BSOD - što, zašto i kako

 Nije verojatno vec je od Acronisa definitivno :)

Uradi update Acronisa TI 2010 ili vrati se unatrag jednu verziju (za sada) dok ovi iz Acronisa ne uklone problem. Eventualno zaustavi sve servise od Acronisa (RUN-services.msc) i disejblaj driver u Device Manager (disable,nemoj uninstall)

Kao rezultat ovoga ces izgubiti mogucnost backupa dok je Windows aktivan ali zato upotrebi Emergency CD da bi radio imaging sistemske particije (primitvno ali i ucinkovitije i brze je)

imam problem...kad otvorim dump file pise:

   Your debugger is not using the correct symbols          

   In order for this command to work properly, your symbol path   

   must point to .pdb files that have full type information.    

   Certain .pdb files (such as the public OS symbols) do not   

   contain the required information.  Contact the group that   

   provided you with these symbols if you need this command to   

   work.                             

   Type referenced: nt!_KPRCB              

Probably caused by : ntoskrnl.exe ( nt+248dcf )

Followup: MachineOwner

zna li tko?

moze li mi neko reci kako da se rjesim ovih problema

STACK_COMMAND:  kb

FOLLOWUP_IP: 

nt!ViReleaseDmaAdapter+12b

805446dc 8913       mov    dword ptr [ebx],edx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ViReleaseDmaAdapter+12b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a784394

FAILURE_BUCKET_ID:  0xC5_2_nt!ViReleaseDmaAdapter+12b

BUCKET_ID:  0xC5_2_nt!ViReleaseDmaAdapter+12b

Followup: MachineOwner

STACK_COMMAND:  kb

FOLLOWUP_IP: 

RtkHDAud+7d849

aa39d849 0f2822      movaps  xmm4,xmmword ptr [edx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RtkHDAud+7d849

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME:  RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  437c351f

FAILURE_BUCKET_ID:  0xD1_RtkHDAud+7d849

BUCKET_ID:  0xD1_RtkHDAud+7d849

Followup: MachineOwner

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  NDIS!ndisMRundownRequests+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NDIS

IMAGE_NAME:  NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025d03

STACK_COMMAND:  .cxr 0xffffffffa8e259bc ; kb

FAILURE_BUCKET_ID:  0x7E_NDIS!ndisMRundownRequests+e

BUCKET_ID:  0x7E_NDIS!ndisMRundownRequests+e

Followup: MachineOwner

---------

STACK_COMMAND:  kb

FOLLOWUP_IP: 

win32k!DrvProbeAndCaptureDevmode+64b

bf8aa0c1 ??        ???

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  win32k!DrvProbeAndCaptureDevmode+64b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8564c7

FAILURE_BUCKET_ID:  0x50_win32k!DrvProbeAndCaptureDevmode+64b

BUCKET_ID:  0x50_win32k!DrvProbeAndCaptureDevmode+64b

Followup: MachineOwner

---------

STACK_COMMAND:  kb

FOLLOWUP_IP: 

Npfs!NpDecodeFileObject+4c

f7948dd4 ??        ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Npfs!NpDecodeFileObject+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  480251c6

FAILURE_BUCKET_ID:  0x25_Npfs!NpDecodeFileObject+4c

BUCKET_ID:  0x25_Npfs!NpDecodeFileObject+4c

Followup: MachineOwner

---------

---------

@mikiseki2

do BSOD-a ti dolazi zbog različitih grešaka s driverima, te sa sistemskim datotekama (BSOD su ti napravili driver od Realtek audio kartice -  RtkHDAud.sys, sistemska datoteka vezana uz mrežu - ndis.sys , image kernela OS-a - ntoskrnl.exe). Mogu ti dati par savjeta, čisto usmjeriti gdje bi problem mogao ležati:

1. Provjeri računalo na malware s nekoliko alata - Malwarebytes, primjera. Napravi Full scan računala.

2. Nađi novije drivere za mrežnu karticu, te alternativno, mrežnu karticu makni iz računala (ili ako je integrirana, isključi ju u BIOS-u). Vidi kako ti se računalo ponaša bez mrežne kartice

3. Nađi novije drivere za Realtekovu audio karticu. Kao i u slučaju mrežne, testiraj računalo tako da makneš karticu (ili isključiš u BIOS-u ako je integrirana - a vjerojatno je).

Radi korake jedan po jedan, ne sve odjednom, kako bi utvrdio što ti radi probleme. Nekako mi se čini da je problem u mrežnoj kartici, no nije 100%. Nema ti druge nego ispitati ovih par koraka, pa se javi s dodatnim informacijama (problemima), ili nadam se rješenjem.

@BlackM

Nisam u potpunosti siguran što bi mogao biti problem. Načelno, jedina situacija kada do BSOD-a ne dolazi je ako je Pagefile podešen na drugoj particiji od one sa OS-om. Sad debelo nagađam, al isprobajte da na računalu nije problem s napajanjem. Dodatno, čini mi se da problem nije vezan uz BSOD, nego neku neispravnu komponentu na računalu. Isprobajte ako možete drugu grafičku, napajanje, procesor, pa i memoriju.

Skroz si fulao temu, ali to su ti poruke od msn-a udi u msn igore desno klikni na 54+mails otvorit će ti na netu prijavi se i počisti...

kako da se rijesim ovog problema:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini042910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Apr 29 18:13:35.375 2010 (GMT-7)
System Uptime: 0 days 3:02:36.931
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image ati2cqag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {eb1f9594, 0, bf08fac6, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : ati2cqag.dll ( ati2cqag+29ac6 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: eb1f9594, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf08fac6, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000001, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************

ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  49bea870

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 eb1f9594

FAULTING_IP:
ati2cqag+29ac6
bf08fac6 394a54          cmp     dword ptr [edx+54h],ecx

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from bf09ba34 to bf08fac6

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ab25e594 bf09ba34 e1e59420 e1e56aa0 ab25e658 ati2cqag+0x29ac6
ab25e598 e1e59420 e1e56aa0 ab25e658 e1c00940 ati2cqag+0x35a34
ab25e59c e1e56aa0 ab25e658 e1c00940 e1e3c2e0 0xe1e59420
ab25e5a0 ab25e658 e1c00940 e1e3c2e0 e1c00940 0xe1e56aa0
ab25e5a4 e1c00940 e1e3c2e0 e1c00940 e1e59420 0xab25e658
ab25e658 00000000 00000028 000024e3 00000000 0xe1c00940


STACK_COMMAND:  kb

FOLLOWUP_IP:
ati2cqag+29ac6
bf08fac6 394a54          cmp     dword ptr [edx+54h],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ati2cqag+29ac6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME:  ati2cqag.dll

BUCKET_ID:  WRONG_SYMBOLS

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

ovaj put sam sve napravio i deinstaliro drivere i instaliro nove i opet isto:

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ab25e594 bf09ba34 e1e59420 e1e56aa0 ab25e658 ati2cqag+0x29ac6
ab25e598 e1e59420 e1e56aa0 ab25e658 e1c00940 ati2cqag+0x35a34
ab25e59c e1e56aa0 ab25e658 e1c00940 e1e3c2e0 0xe1e59420
ab25e5a0 ab25e658 e1c00940 e1e3c2e0 e1c00940 0xe1e56aa0
ab25e5a4 e1c00940 e1e3c2e0 e1c00940 e1e59420 0xab25e658
ab25e658 00000000 00000028 000024e3 00000000 0xe1c00940


STACK_COMMAND:  kb

FOLLOWUP_IP:
ati2cqag+29ac6
bf08fac6 394a54          cmp     dword ptr [edx+54h],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ati2cqag+29ac6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME:  ati2cqag.dll

BUCKET_ID:  WRONG_SYMBOLS

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

Imam sljedeći problem: sustav mi se ruši samo kada pokrenem 3DMark 06. Sve ostale benchmarke mogu pokretati po x puta i ništa, a kada njega pokrenem nekada prođe a neka ne. Testirao sam memoriju sa Memtestom +( zadnja verzija 4.1) i nije našao nikakvu pogrešku ( test je trajao satima) Memorija je OCZ, nije klokana niti ništa slično, samo lagano dignut napon na 1.85. Procesor isto tako nije klokan ( AMD 810 Quad 2.6 GHz) Stavio sam i novo napajanje od 500 W jer sam sumnjao da staro ne valja. No moram napomenuti da se problem javio kada sam stavio GTX 260 ( pa me i dalje muči da 500W Chieftec napajanje) ipak nije preslabo za nju i procesor dok test traje.

Dump

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050610-17343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`0368ce50
Debug session time: Thu May  6 22:32:18.179 2010 (UTC + 2:00)
System Uptime: 0 days 0:17:21.710
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800034cdcbf, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+24f )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800034cdcbf, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!KiSecondaryClockInterrupt+24f
fffff800`034cdcbf 0f285510        movaps  xmm2,xmmword ptr [rbp+10h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036f70e0
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  3DMark06.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003500a17 to fffff800034c0f00

STACK_TEXT: 
fffff880`0829d208 fffff800`03500a17 : 00000000`0000001e ffffffff`c0000005 fffff800`034cdcbf 00000000`00000000 : nt!KeBugCheckEx
fffff880`0829d210 fffff800`034c0542 : fffff880`0829d9e8 00000000`00000000 fffff880`0829da90 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`0829d8b0 fffff800`034bee4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0829da90 fffff800`034cdcbf : 00000000`00000000 fffff880`0829dca0 00000000`00000000 00000000`0fa14180 : nt!KiGeneralProtectionFault+0x10a
fffff880`0829dc20 00000000`71bb7b11 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x24f
00000000`05b8feb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x71bb7b11


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiSecondaryClockInterrupt+24f
fffff800`034cdcbf 0f285510        movaps  xmm2,xmmword ptr [rbp+10h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiSecondaryClockInterrupt+24f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiSecondaryClockInterrupt+24f

BUCKET_ID:  X64_0x1E_c0000005_nt!KiSecondaryClockInterrupt+24f

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

Kako vidim da je greška u ntkrnlmp.exe a to je vrlo "uvriježena greška" i kako vidim da se spominu neki clock interupti zanima me mišljenje koje znalca. Pokušao sam mijenjati drivere za grafičku, spuštati ili dizati napon na mem modulima, grafičku underclockati ( nije clockana, nego joj još više spustiti clock od tvorničkog) Ostalo je zapravo samo reinstalacija 7 x64.

Bilo kakav savjet?

_______________________________________

UPDATE

Možda će svima biti čudno , ali na prijedlog svog prijatelja resetirao sam BIOS: ali tako što sam odštekao sve konektore sa matične i još maknuo bateriju od BIOSa iz ležišta na deetak minuta. Nakon što sam sve uredno namjestio u BIOS-u nikakvih problam sa 3dMarkom 06 više nemam, vrtio sam ga u loopu par sati bez ikakvog problema. Pa ako netko ima sličan problem kao i ja neka pokuša ovo vrlo jednostavno rješenje.

BSOD ti radi windrvNT.sys datoteka koja je dio Folder Lock programa.

Prvo što trebaš pokušati je maknuti folder lock sa računala pa pokušati instalirati Photoshop.

To (deinstalacija) će vjerojatno riješiti problem. Ako ne, postaj slijedeći dump...

Mada sam u prijašnjoj poruci izvjestio da problema nema, izgleda da se vratio: redovito svaki dan imam barem jedan BSOD i to uvijek sa drugačijom pogreškom, a sve se počelo javljati odkada sam na svoj komp stavio GTX 260. Kako međutim GTX na drugom računalu radi besprijekorono, a radi i na ovom, te je prošlo niz testova bez pogreške iskreno sam bez ideje. Pokušat ću sa čistom instalacijom OS-a pa ćemo vidjeti rezultat. Zadnji BSOD je bio X64_IP_MISALIGNED a izgleda ovako

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


Could not read faulting driver name

WRITE_ADDRESS:  fffff8004b7be07d

FAULTING_IP:
nt!IopProcessWorkItem+5
fffff800`037ba809 208379380048    and     byte ptr [rbx+48003879h],al

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031b6b10 -- (.trap 0xfffff880031b6b10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa80048d4940
rdx=0000257a00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800037ba809 rsp=fffff880031b6ca0 rbp=fffff880031b6ca0
 r8=0000000000000000  r9=000000000029d83d r10=000000000002159a
r11=fffffa80048d4940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!IopProcessWorkItem+0x5:
fffff800`037ba809 208379380048    and     byte ptr [rbx+48003879h],al ds:6680:00000000`48003879=??
Resetting default scope

MISALIGNED_IP:
nt!IopProcessWorkItem+5
fffff800`037ba809 208379380048    and     byte ptr [rbx+48003879h],al

LAST_CONTROL_TRANSFER:  from fffff8000353c801 to fffff800034bd600

STACK_TEXT: 


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+5
fffff800`037ba809 208379380048    and     byte ptr [rbx+48003879h],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!IopProcessWorkItem+5

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner

Hvala na odgovoru: mada sada me je malo sram jer ni sam ne znam kako da napišem sljedeće: kada sam probao testov ( inače koristi OCCT 3.1.0 koji broji grafičke errore) nisam probao na duže staze.  I danas mi vrag ne da mira i opalim sat vremena testa. I on ispali 23 errora. Onda sam lagano spuštao takt i nađem da je kartica i nakon sata vremena stabilna na 585 MHz. Kako je to tvorniki OC kartica na 625 HMz vjerujem da u njoj nešto nije moglo izgurati takvu frekvenciju, a kako sam je ja već kupio polovnu: onda i ne znam koliko je dugo radila. Uglavnom sada sam je flashao na 585 , prolazi sve testove OK, nigdje se ne ruši, neću likovati preuranjeno i šutim :)

Random BSOD i to totalni, ali skoro uvijek nakon povratka iz standby-a ( volim ostaviti tv na monitoru, pa TV tuner kartica ode u stand by nakon sat vremena) No ni tada nije pravilo: dakle baš random. Random je što se tiče opterećanja isto tako: dakle neka se ne ruši kada igraš igricu satima, a nekada kada pokreneš firefox.  Dakle opterećenje ili ne:nema veze.

Što se tiče napajanja sumnjam da je u njemu stvar: jer i sa karticom koja je u full loadu, sa 4 core koje su na 2.8 GHz makinja troši 260 W a ono je novo 500W.

Dakle zasada, čekam sljedeći BSOD pa ćemo vidjeti dalje.

Pozdrav

Upravo se sistem srušio usred surfanja netom: po dumpu u pitanju je tcpip.sys

_________________________________________________________________

Update dva: frekvencija grafičke spuštena na default za ovaj tip kartice: 18 sati bez problema. Stavljeno drugo napajanje od 500 W

_________________________________________________________________________________________________________

Kad god me netko nazove il ja nekog nazovem preko skype-a izbaci mi BSoD. Evo analize 2 crash dumpa.

DRIVER_CORRUPTED_EXPOOL (c5)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is

caused by drivers that have corrupted the system pool.  Run the driver

verifier against any new (or suspect) drivers, and if that doesn't turn up

the culprit, then use gflags to enable special pool.

Arguments:

Arg1: 00000004, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: 805515a1, address which referenced memory

Debugging Details:

------------------

BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 

nt!MmProtectToPteMask+39

805515a1 894804      mov    dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  uTorrent.exe

LAST_CONTROL_TRANSFER:  from 80570a00 to 805515a1

STACK_TEXT:  

a8b1d9d0 80570a00 00000000 00000001 74696157 nt!MmProtectToPteMask+0x39

a8b1dd48 804dd99f 00000040 017a2c60 00000001 nt!CmQueryKey+0x62

a8b1dd60 0156ff3c 7c90e4f4 badb0d00 0156fea8 nt!ZwSetSystemPowerState+0xf

WARNING: Frame IP not in any known module. Following frames may be wrong.

a8b1dd64 7c90e4f4 badb0d00 0156fea8 00000000 0x156ff3c

a8b1dd68 badb0d00 0156fea8 00000000 00000000 0x7c90e4f4

a8b1dd6c 0156fea8 00000000 00000000 00000000 0xbadb0d00

a8b1dd70 00000000 00000000 00000000 00000000 0x156fea8

STACK_COMMAND:  kb

FOLLOWUP_IP: 

nt!MmProtectToPteMask+39

805515a1 894804      mov    dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmProtectToPteMask+39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  48a40b55

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xC5_2_nt!MmProtectToPteMask+39

BUCKET_ID:  0xC5_2_nt!MmProtectToPteMask+39

Followup: MachineOwner

---------

pozdrav ljudi imam problem...imam vistu home basic i išo sam na tune up i stisnuo onog doktora...on mi ga je sam restartirao i počeo pregledavat(ima 5 koraka) odjednom mi se ekran zašarenio i počeo titrati oko 3 minute...ja ugasim na gumb pričekam i ponovno upalim...sad mi neće uopće pokrenut windowse...prvo me tražio da ubacim instalacijski dvd/cd, da izaberem jezik i repariram sistem ja to napravio i sad mi uđe tojest počne mi učitavat pa mi izbaci taj plavi ekran nakratko i sam se restartira...ne znam šta da radim, da instaliram ponovno vistu ili? hvala svima unaprijed