Win7 ei käynnisty

Discussion in 'Windows -ongelmat' started by jorpen, Jun 9, 2015.

  1. jorpen

    jorpen Member

    Joined:
    Dec 11, 2014
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    11
    Eilen päivitin windows updaten ehdottomat tiedostot ja sen jälkeen win7 ei käynnisty. Tulee blue screeen IRQ L_NOT_LESS_EQUAL.
    Windowsin yritykset käynnistää edellisellä toimivalla versiolla ei tuota tulosta. SafeModeen pääsee, ilman verkkoa.
    Miten pakotan edelliseen toimivaan versioon? Backupia tai imagea ei ole.
     
    jorpen, Jun 9, 2015
    #1
  2. 1pertti

    1pertti Senior member

    Joined:
    Sep 10, 2008
    Messages:
    9,179
    Likes Received:
    1,225
    Trophy Points:
    243
    Käynnistä kone vikasietotilassa (Safe Mode) ja tee järjestelmän palautus edelliseen palautuspisteeseen. Widows Update tallentaa palautuspisteen ennen päivitystä, joten tuore palautuspiste pitäisi olla käytettävissä. Vikasietotilassa tehtyä järjestelmän palautusta ei voi kumota, mutta sillä tuskin on väliä, kun Windows ei nykytilassa edes käynnisty.
     
    1pertti, Jun 9, 2015
    #2
  3. jorpen

    jorpen Member

    Joined:
    Dec 11, 2014
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    11
    Ei pelitä. Saa kyllä edellisen palautuspisteen valittua, mutta jossain vaiheessa tulee buutti eikä auta tämäkään.
     
    jorpen, Jun 9, 2015
    #3
  4. *Trinity*

    *Trinity* Senior member

    Joined:
    Dec 15, 2014
    Messages:
    6,906
    Likes Received:
    1,256
    Trophy Points:
    223
    Hei
    mene seueaaviin polkuihin

    C:\Windows\Minidump\...
    C:\Windows\LiveKernelReports\WATCHDOG\...

    Ota vaikka usb:lle siellä olevat dmp.tiedostot
    ja pistä jollekin palvelimelle ja latauslinkki tänne.
     
    *Trinity*, Jun 9, 2015
    #4
  5. *Trinity*

    *Trinity* Senior member

    Joined:
    Dec 15, 2014
    Messages:
    6,906
    Likes Received:
    1,256
    Trophy Points:
    223
    Mahdollinen bsodin aiheuttaja on langattoman verkkokortin ajuri (atheros)

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\\Desktop\Uusi kansio (2)\060815-78250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18839.x86fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0x82a15000 PsLoadedModuleList = 0x82b60e30
Debug session time: Mon Jun  8 22:25:54.578 2015 (UTC + 3:00)
System Uptime: 0 days 0:02:10.234
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1c, 2, 1, 82e3171e}

*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : athr.sys ( athr+94c40 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e3171e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b8184c
Unable to read MiSystemVaType memory at 82b60780
0000001c

CURRENT_IRQL:  2

FAULTING_IP:
hal!KeAcquireSpinLockRaiseToSynch+e
82e3171e f00fba2900      lock bts dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFFFFF8078B000

TRAP_FRAME:  8078adc4 -- (.trap 0xffffffff8078adc4)
ErrCode = 00000002
eax=00000002 ebx=86779510 ecx=0000001c edx=8078ae84 esi=85e700e0 edi=00000000
eip=82e3171e esp=8078ae38 ebp=8078ae5c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
hal!KeAcquireSpinLockRaiseToSynch+0xe:
82e3171e f00fba2900      lock bts dword ptr [ecx],0   ds:0023:0000001c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e3171e to 82a55d1f

STACK_TEXT:
8078adc4 82e3171e badb0d00 8078ae84 84a7b500 nt!KiTrap0E+0x1b3
8078ae34 8ec9fc40 04745078 00000000 00000000 hal!KeAcquireSpinLockRaiseToSynch+0xe
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ae5c 8ed46726 86598020 8078ae84 8078ae9c athr+0x94c40
8078ae70 8ed77838 86598020 8078ae84 8078ae9c athr+0x13b726
8078aea0 8ed5bcb7 863ee020 82e33cca 86779510 athr+0x16c838
8078aec8 8ec45d6d 863ee020 8078aee4 8ec0c830 athr+0x150cb7
8078aed4 8ec0c830 86598020 863e8020 8078af20 athr+0x3ad6d
8078aee4 8908589a 863e8020 00000000 8078af10 athr+0x1830
8078af20 89030a1f 86779524 00779510 00000000 ndis!ndisMiniportDpc+0xe2
8078af48 82a8cff5 86779524 86779510 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 82a8ce58 82b41e20 84adb4c0 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82a8c61c 807d29f4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 807d29f4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82a8c61c 00000000 0000001a 00d6850f bb830000 0x807d29f4


STACK_COMMAND:  kb

FOLLOWUP_IP:
athr+94c40
8ec9fc40 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  athr+94c40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athr

IMAGE_NAME:  athr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5539d395

FAILURE_BUCKET_ID:  0xA_athr+94c40

BUCKET_ID:  0xA_athr+94c40

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa_athr+94c40

FAILURE_ID_HASH:  {63fb11b9-95e3-3436-3b5c-df04ce0e4c59}

Followup: MachineOwner
---------

kd> lmvm athr
start    end        module name
8ec0b000 8ef27000   athr     T (no symbols)       
    Loaded symbol image file: athr.sys
    Image path: \SystemRoot\system32\DRIVERS\athr.sys
    Image name: athr.sys
    Timestamp:        Fri Apr 24 08:24:37 2015 (5539D395)
    CheckSum:         0031BCD7
    ImageSize:        0031C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mene vikasietotilassa
    Ohjauspaneeli - Laitehallinta - Verkkosovittimet - Valitse sieltä Atheros liittyvä ja hiiren oikealla valitse poista käytöstä.
    Koita käynnistyykö kone normaalisti

    Toinen mikä on ainakin jossainvaiheessa aiheuttanut ongelmia on näytönohjain lakkasi vastaamasta ja palautui ongelma.

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\\Desktop\Uusi kansio (2)\WD-20150125-0415.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18700.x86fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0x82a0d000 PsLoadedModuleList = 0x82b565b0
Debug session time: Sun Jan 25 05:15:48.814 2015 (UTC + 3:00)
System Uptime: 1 days 6:37:34.163
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {86824510, 9014438e, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+11238e )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: 86824510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9014438e, The pointer into responsible device driver module (e.g owner tag).
Arg3: 00000000, The secondary driver specific bucketing key.
Arg4: 00000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+11238e
9014438e ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
8ae6dcb4 90b2d163 00000000 9014438e 88feb07e dxgkrnl!TdrUpdateDbgReport+0x68
8ae6dcdc 90b2cd23 00000000 82a43b99 86824510 dxgkrnl!TdrCollectDbgInfoStage2+0x1ab
8ae6dd18 90b2d1be 86824510 8212b788 8ae6dd3c dxgkrnl!DXGADAPTER::Reset+0xb6
8ae6dd28 90b8e343 86824510 8212b788 00000000 dxgkrnl!TdrResetFromTimeout+0x12
8ae6dd3c 90b915bd 8212b788 00000000 82137a48 dxgmms1!VidSchiRecoverFromTDR+0x15
8ae6dd50 82c15fb7 8212b788 ad0a51a6 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8ae6dd90 82abd6f9 90b9153e 8212b788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+11238e
9014438e ??              ???

SYMBOL_NAME:  nvlddmkm+11238e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b44481

FAILURE_BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x117_image_nvlddmkm.sys

FAILURE_ID_HASH:  {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}

Followup: MachineOwner
---------
    Joskin veikkaa ettei se ole syy tuohon bsodiin
     
    Last edited: Jun 9, 2015
    *Trinity*, Jun 9, 2015
    #5
    jorpen likes this.
  6. jorpen

    jorpen Member

    Joined:
    Dec 11, 2014
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    11

    Verkkokortin disablointi auttoi! Jippii!
    Nyt herää kysymys onko ajuri vain rikki/vanhentunut vai onko kortissa vikaa...
     
    jorpen, Jun 9, 2015
    #6
  7. *Trinity*

    *Trinity* Senior member

    Joined:
    Dec 15, 2014
    Messages:
    6,906
    Likes Received:
    1,256
    Trophy Points:
    223
    Voit koittaa ladata emolevyn valmistajan sivulta uudet ajurit ja koittaa onko sillä vaikutusta
    Tai siten anttaa Windowsin ladata ne, jos taas rupeaa tulemaan bsodia niin otat taas pois päältä vain
     
    *Trinity*, Jun 9, 2015
    #7
  8. jorpen

    jorpen Member

    Joined:
    Dec 11, 2014
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    11
    Jos verkkokortin laittaa päälle niin Windows kaatuu. Pitää laittaa parikaapelilla adsl-boksiin, eri kortti nimittäin.
     
    jorpen, Jun 9, 2015
    #8
  9. *Trinity*

    *Trinity* Senior member

    Joined:
    Dec 15, 2014
    Messages:
    6,906
    Likes Received:
    1,256
    Trophy Points:
    223
    Ok saattaa olla että siinä on sitten jotain fyysistä vikaa jolloin se aiheuttaa kaatumisen kun sen yrittää ottaa käyttöön.
    toimiiko kone muuten normaalisti?
     
    *Trinity*, Jun 9, 2015
    #9

Share This Page