BSOD 4 times last month - Different error codes

andis59 · 24 Jan 2012

I'm have some instability in my system. During last month I had about 4 BSOD with different codes.

2011-12-13 08:20:24 DRIVER_POWER_STATE_FAILURE 0x0000009f
2011-12-15 19:59:09 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x0000008e
2011-12-18 20:10:13 IRQL_NOT_LESS_OR_EQUAL 0x0000000a
2012-01-08 12:12:17 DRIVER_POWER_STATE_FAILURE 0x0000009f

What is happening?
How do I fix it?

// Anders

writhziden · 24 Jan 2012

Code:


Loading Dump File [F:\BSODDmpFiles\andis59\010812-21106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e40000 PsLoadedModuleList = 0x82f894d0
Debug session time: Sun Jan  8 04:05:29.638 2012 (GMT-7)
System Uptime: 0 days 0:27:20.277
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 894c6928, 82f67b24}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 00000258, Timeout in seconds.
Arg3: 894c6928, The thread currently holding on to the Pnp lock.
Arg4: 82f67b24

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  894c6928

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82ebe65d to 82eb7766

STACK_TEXT:  
92950410 82ebe65d 894c6928 00000000 82f6ad20 nt!KiSwapContext+0x26
92950448 82ebd4b7 894c69e8 894c6928 8602358c nt!KiSwapThread+0x266
92950470 82eb70cf 894c6928 894c69e8 00000000 nt!KiCommitThreadWait+0x1df
929504ec 82fd9ba7 8602358c 00000000 8001c200 nt!KeWaitForSingleObject+0x393
92950564 82ee85ce 860234f0 8619da01 00000000 nt!IopMountVolume+0x4f
9295059c 83085c59 8619da20 929506c8 92950660 nt!IopCheckVpbMounted+0x64
92950680 83065b6e 860234f0 857ce838 85992008 nt!IopParseDevice+0x7c9
929506fc 83075f80 00000000 92950750 00000240 nt!ObpLookupObjectName+0x4fa
9295075c 8306ca5e 92950ae8 857ce838 85b1a300 nt!ObOpenObjectByName+0x165
929507d8 83072be4 92950b10 00120089 92950ae8 nt!IopCreateFile+0x673
92950820 82e7e21a 92950b10 00120089 92950ae8 nt!NtOpenFile+0x2a
92950820 82e7c581 92950b10 00120089 92950ae8 nt!KiFastCallEntry+0x12a
929508b0 8bdc14e5 92950b10 00120089 92950ae8 nt!ZwOpenFile+0x11
92950b14 8bdb4d92 860170d8 82e0e6ee d9aabea8 volsnap!VspIsFileSystemLocked+0xc5
92950b78 82fff80a 01950bfc 92950c00 82fa6da0 volsnap!VolSnapTargetDeviceNotification+0x1b4
92950bb8 82fffa51 92950bfc 92950bec 82e8ac28 nt!PnpNotifyDriverCallback+0x107
92950c18 831011c4 82e8ac28 92950c70 c92c41f8 nt!PnpNotifyTargetDeviceChange+0x19c
92950cc4 82ff12d2 92950cf4 00000000 c92c41d8 nt!PnpProcessQueryRemoveAndEject+0x60d
92950cdc 82fff3d2 00000000 85a2f9c0 894c6928 nt!PnpProcessTargetDeviceEvent+0x38
92950d00 82ebda6b 85a2f9c0 00000000 894c6928 nt!PnpDeviceEventWorker+0x216
92950d50 83048fda 80000001 b820e3cb 00000000 nt!ExpWorkerThread+0x10d
92950d90 82ef11f9 82ebd95e 80000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff894c6928 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    82eb795f - nt!SwapContext_PatchFxb+2
	[ 01:21 ]
    82eb7bad - nt!EnlightenedSwapContext_PatchXSave+2 (+0x24e)
	[ 01:21 ]
2 errors : !nt (82eb795f-82eb7bad)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------

Loading Dump File [F:\BSODDmpFiles\andis59\121811-157139-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e3d000 PsLoadedModuleList = 0x82f864d0
Debug session time: Sun Dec 18 12:00:08.912 2011 (GMT-7)
System Uptime: 0 days 11:15:33.552
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffffa, ff, 1, 82eb9092}

Probably caused by : hardware ( nt!KiLoadBalanceProcessor+bb )

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

0: 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: fffffffa, memory referenced
Arg2: 000000ff, 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: 82eb9092, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82fa6848
Unable to read MiSystemVaType memory at 82f85e20
 fffffffa 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiLoadBalanceProcessor+bb
82eb9092 006afa          add     byte ptr [edx-6],ch

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  82f64c18 -- (.trap 0xffffffff82f64c18)
ErrCode = 00000002
eax=00718d03 ebx=89ae9208 ecx=0001e47e edx=00000000 esi=89ae91e8 edi=82f67d20
eip=82eb9092 esp=82f64c8c ebp=82f64d20 iopl=0         nv up di pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010006
nt!KiLoadBalanceProcessor+0xbb:
82eb9092 006afa          add     byte ptr [edx-6],ch        ds:0023:fffffffa=??
Resetting default scope

MISALIGNED_IP: 
nt!KiLoadBalanceProcessor+bb
82eb9092 006afa          add     byte ptr [edx-6],ch

LAST_CONTROL_TRANSFER:  from 82eb9092 to 82e7e5fb

STACK_TEXT:  
82f64c18 82eb9092 badb0d00 00000000 00cf48da nt!KiTrap0E+0x2cf
82f64d20 82eb4e0d 00000000 0000000e 00000000 nt!KiLoadBalanceProcessor+0xbb
82f64d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiLoadBalanceProcessor+bb
82eb9092 006afa          add     byte ptr [edx-6],ch

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiLoadBalanceProcessor+bb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

Loading Dump File [F:\BSODDmpFiles\andis59\121511-78468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e15000 PsLoadedModuleList = 0x82f5e4d0
Debug session time: Thu Dec 15 11:55:26.165 2011 (GMT-7)
System Uptime: 0 days 17:30:23.803
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 8b8f4ac8, The address that the exception occurred at
Arg3: ba27b498, Trap Frame
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for BHDrvx86.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx86.sys

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
fltmgr!FltpShouldPostWork+0
8b8f4ac8 8bff            mov     edi,edi

TRAP_FRAME:  ba27b498 -- (.trap 0xffffffffba27b498)
ErrCode = 00000000
eax=00000000 ebx=8b8e6f00 ecx=9f4b0274 edx=00000007 esi=c7bf7958 edi=ee9002d8
eip=8b8f4ac8 esp=ba27b50c ebp=ba27b51c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
fltmgr!FltpShouldPostWork:
8b8f4ac8 8bff            mov     edi,edi
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Robocopy.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82eca06c to 82ef3ef4

FAILED_INSTRUCTION_ADDRESS: 
fltmgr!FltpShouldPostWork+0
8b8f4ac8 8bff            mov     edi,edi

STACK_TEXT:  
ba27b004 82eca06c 0000008e c000001d 8b8f4ac8 nt!KeBugCheckEx+0x1e
ba27b428 82e53e06 ba27b444 00000000 ba27b498 nt!KiDispatchException+0x1ac
ba27b490 82e53da2 ba27b51c 8b8f4ac8 badb0d00 nt!CommonDispatchException+0x4a
ba27b4dc 8322cba9 ba27bb50 00000030 ee9002d8 nt!Kei386EoiHelper+0x17a
ba27b51c 8b8f3765 c7bf7958 ee9002d8 c7bf7958 hal!KfLowerIrql+0x61
ba27b534 8b8dd773 c7bf7958 00000000 c7bf7958 fltmgr!FltpCreateFileNameInformation+0x81
ba27b554 8b8dd8c7 9f6dd790 00000000 00000000 fltmgr!HandleStreamListNotSupported+0x125
ba27b584 8b8ddfa3 c00000bb ba27b8a4 00000000 fltmgr!FltpGetFileNameInformation+0xc7
ba27b5ac 9aa69875 009002e0 00000101 ba27b8a4 fltmgr!FltGetFileNameInformation+0x12b
WARNING: Stack unwind information not available. Following frames may be wrong.
ba27b5d0 9aa6a0d9 dbc97024 e98507c4 e98507ac BHDrvx86+0x5c875
ba27b5ec 9aa9f7c5 ba27b600 9aaa219f 0000000b BHDrvx86+0x5d0d9
ba27b5f4 9aaa219f 0000000b ba27b610 9aaa2467 BHDrvx86+0x927c5
ba27b600 9aaa2467 993e04f0 0000000b ba27b64c BHDrvx86+0x9519f
ba27b610 9aaa283c 993e04f0 00000005 0000000b BHDrvx86+0x95467
ba27b64c 9aaa23a7 ba27b7d4 dbc97008 ffffffff BHDrvx86+0x9583c
ba27b674 9aaa2561 ba27b7d4 dbc97008 ffffffff BHDrvx86+0x953a7
ba27b6a4 9aa7f866 00000001 ba27b7d4 e9850000 BHDrvx86+0x95561
ba27b740 9aa7f9a8 00000000 ba27b7d4 9aa7f9a8 BHDrvx86+0x72866
ba27b778 9aa6df1c 00000000 aea32008 ba27b7d4 BHDrvx86+0x729a8
ba27b7a8 9aa1108e ba27b85c aea32008 ba27b7d4 BHDrvx86+0x60f1c
ba27b800 9aa11a98 0027b85c aea32008 00000018 BHDrvx86+0x408e
ba27b81c 9aa6316c aea32008 00000000 82ebf901 BHDrvx86+0x4a98
ba27b834 9aa67fc9 ba27b85c 82ebf94d e269b880 BHDrvx86+0x5616c
ba27b960 9aa63d94 ee9002e0 ba27b9b4 e269b880 BHDrvx86+0x5afc9
ba27b994 8b8d7aeb ee9002e0 ba27b9b4 ba27b9e0 BHDrvx86+0x56d94
ba27ba00 8b8da9f0 ba27ba44 d3158b70 00000000 fltmgr!FltpPerformPreCallbacks+0x34d
ba27ba18 8b8ee1fe ba27ba44 8b8f1f3c 00000000 fltmgr!FltpPassThroughInternal+0x40
ba27ba2c 8b8ee8b7 ba27ba44 d3158b70 9294a208 fltmgr!FltpCreateInternal+0x24
ba27ba70 82e4c58e 9ed898e8 9f6dd3d8 9294a264 fltmgr!FltpCreate+0x2c9
ba27ba88 8305b367 909bd6cf ba27bc30 00000000 nt!IofCallDriver+0x63
ba27bb60 8303ab6e 89bdbe20 857ce838 f094e3d8 nt!IopParseDevice+0xed7
ba27bbdc 8304af80 00000000 ba27bc30 00000040 nt!ObpLookupObjectName+0x4fa
ba27bc38 83041a5e 0084eb44 857ce838 00120001 nt!ObOpenObjectByName+0x165
ba27bcb4 830652d6 0084ecb8 40110081 0084eb44 nt!IopCreateFile+0x673
ba27bd00 82e5321a 0084ecb8 40110081 0084eb44 nt!NtCreateFile+0x34
ba27bd00 775670b4 0084ecb8 40110081 0084eb44 nt!KiFastCallEntry+0x12a
0084f12c 00000000 00000000 00000000 00000000 0x775670b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
BHDrvx86+5c875
9aa69875 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  BHDrvx86+5c875

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BHDrvx86

IMAGE_NAME:  BHDrvx86.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb0c03

FAILURE_BUCKET_ID:  0x8E_BAD_IP_BHDrvx86+5c875

BUCKET_ID:  0x8E_BAD_IP_BHDrvx86+5c875

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

Loading Dump File [F:\BSODDmpFiles\andis59\121311-163660-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82e1a000 PsLoadedModuleList = 0x82f634f0
Debug session time: Mon Dec 12 14:55:23.143 2011 (GMT-7)
System Uptime: 4 days 5:20:58.782
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.................................
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8649a560, Physical Device Object of the stack
Arg3: 8078adb0, Functional Device Object of the stack
Arg4: 85b2aac0, The blocked IRP

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

*** WARNING: Unable to verify timestamp for bcmwl6.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl6.sys

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  85b2aac0

DEVICE_OBJECT: 890a3028

DRIVER_OBJECT: 89097710

IMAGE_NAME:  bcmwl6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cec1238

MODULE_NAME: bcmwl6

FAULTING_MODULE: a3c3f000 bcmwl6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82ee0eef to 82ef8eb4

STACK_TEXT:  
8078ad64 82ee0eef 0000009f 00000003 8649a560 nt!KeBugCheckEx+0x1e
8078add0 82ee0f68 8078ae88 0000fffd 857d6a70 nt!PopCheckIrpWatchdog+0x1f5
8078ae08 82e94019 82f5c6e0 00000000 bf948490 nt!PopCheckForIdleness+0x73
8078ae4c 82e93fbd 82f44d20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
8078af38 82e93e7a 82f44d20 8078af78 00000000 nt!KiProcessExpiredTimerList+0x101
8078afac 82e9200e 0164e049 8db17968 00000000 nt!KiTimerExpiration+0x25c
8078aff4 82e917dc 8db17918 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 8db17918 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82e917dc 00000000 0000001a 00d6850f bb830000 0x8db17918


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_bcmwl6.sys

BUCKET_ID:  0x9F_IMAGE_bcmwl6.sys

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

Possible causes Memory problems... Drivers...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
Caused by Symantec driver. Other possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.
Caused by Broadcom 802.11g Network Adapter driver, which could have been indirectly due to Symantec.

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking anything, please stop.
Since one of your crashes was Norton related, and another may have been, download and run the Norton Removal Tool to uninstall Norton and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

I note that you are working with zigzag3143 in https://www.sevenforums.com/crashes-d...snt-work.html;. You can use the info I provided above to supplement his help. My advice above is really superfluous at this point, so I suggest you continue working with him. :)

andis59 · 25 Jan 2012

Hello,

I have already removed Norton, but the dump was probably from before.

I have run Memtest86+ for 12 passes and 0 errors. Will run extended version of the Windows Memory Diagnostics Tool tonight after Verifier.

I'm running Verifier at the moment but nothing has happened yet. Usually the BSOD happens during the night. Might have something to do with some scheduled tasks that runs during the night... So maybe I get a crash tonight
:)

Thanks for replying!

// Anders

writhziden · 25 Jan 2012

Alright, good to hear you removed Norton earlier. If it happens overnight, it is probably a device that the driver is having difficulty either waking up (turning back on) or putting to sleep (turning back off) during its sleep cycle. The most common driver that causes issues with sleep cycles is a network adapter driver. You may want to update all network adapter drivers.

Also, I am now subscribed to your other thread (https://www.sevenforums.com/crashes-d...ml#post1762959) after speaking with zigzag3143 who offered to let me help with both. The drivers listed were loaded during your recent crash, and he found them outdated using the debugging tool we use. A snapshot is provided as an example.