Windows 7: BSOD when system is going to sleep mode

MortenB · 23 Feb 2012

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: MORTENS-DELL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6433136640 total
VM: 2147352576, free: 1943576576

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 22.02.2012 22:18:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022312-22308-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006275060, 0xFFFFF800033F4518, 0xFFFFFA8006589400)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 22.02.2012 22:18:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006275060, 0xFFFFF800033F4518, 0xFFFFFA8006589400)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 22.02.2012 19:23:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-14586-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006270060, 0xFFFFF800033F4518, 0xFFFFFA8008249E10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 22.02.2012 04:03:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-14352-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006277060, 0xFFFFF80000B9A518, 0xFFFFFA80096B58E0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

writhziden · 24 Feb 2012

Possible out of date drivers:

Code:

GEARAspiWDM	fffff880`03dc9000	fffff880`03dd6000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
RTKVHD64	fffff880`0463c000	fffff880`047e8900	Fri May 22 12:04:20 2009 (4a16e924)	001b57b6		RTKVHD64.sys
k57nd60a	fffff880`0303e000	fffff880`0308f000	Sat Jun 20 05:34:49 2009 (4a3cc959)	0005682d		k57nd60a.sys
nvBridge	fffff880`03bd8000	fffff880`03bd9180	Fri Jun 26 15:22:03 2009 (4a453bfb)	00010f0d		nvBridge.kmd
nvlddmkm	fffff880`030de000	fffff880`03bd7d80	Fri Jun 26 16:15:53 2009 (4a454899)	00b06499		nvlddmkm.sys

GEARAspiWDM.sys
RTKVHD64.sys
k57nd60a.sys
nvBridge.kmd
nvlddmkm.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\MortenB\Windows_NT6_BSOD_jcgriff2\022312-22308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`033f4500?
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0200f000 PsLoadedModuleList = 0xfffff800`02254670
Debug session time: Wed Feb 22 15:18:24.174 2012 (UTC - 7:00)
System Uptime: 0 days 2:41:54.251
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006275060, fffff800033f4518, fffffa8006589400}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006275060, Physical Device Object of the stack
Arg3: fffff800033f4518, Functional Device Object of the stack
Arg4: fffffa8006589400, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f83000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`033f44c8 fffff800`020f9cd2 : 00000000`0000009f 00000000`00000003 fffffa80`06275060 fffff800`033f4518 : nt!KeBugCheckEx
fffff800`033f44d0 fffff800`020975fc : fffff800`033f4600 fffff800`033f4600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`033f4570 fffff800`02097496 : fffff800`02236f00 00000000`00098070 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`033f45e0 fffff800`0209737e : 00000016`9e252532 fffff800`033f4c58 00000000`00098070 fffff800`02205088 : nt!KiProcessExpiredTimerList+0xc6
fffff800`033f4c30 fffff800`02097167 : 00000005`e022a7c1 00000005`00098070 00000005`e022a7c8 00000000`00000070 : nt!KiTimerExpiration+0x1be
fffff800`033f4cd0 fffff800`0208396a : fffff800`02201e80 fffff800`0220fcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`033f4d80 00000000`00000000 : fffff800`033f5000 fffff800`033ef000 fffff800`033f4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_k57nd60a_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_k57nd60a_IMAGE_pci.sys

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

This crash is due to the system sending a device driver the signal to turn itself off or turn itself on during a power cycle such as during sleep, hibernate, shut down, or startup. The device or device driver failed to respond to the signal and so the system crashed to force the power state. The most common components to cause this are network adapters or display card adapters. Could be caused by either the devices themselves or their drivers.

Update the following drivers:
RTKVHD64.sys
k57nd60a.sys
nvBridge.kmd
nvlddmkm.sys

Two of the drivers are network related, and they may very well be causing the power state failure crashes. The others are your audio and display card drivers, and the display card could also be causing the crashes you are experiencing. The audio driver is just a good idea to keep updated since it is an important system component.

MortenB · 04 Mar 2012

Hi,

Now I have updated these drivers:
GEARAspiWDM.sys
RTKVHD64.sys
k57nd60a.sys
nvBridge.kmd
nvlddmkm.sys

but still I get BSOD

Here's what WhoCrashed reports:

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: MORTENS-DELL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6433136640 total
VM: 2147352576, free: 1943351296

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 02.03.2012 20:29:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030312-14742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006251A10, 0xFFFFF800037F4518, 0xFFFFFA80065787D0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 02.03.2012 20:29:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006251A10, 0xFFFFF800037F4518, 0xFFFFFA80065787D0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 02.03.2012 01:06:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-14196-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800626FA10, 0xFFFFF800037F9518, 0xFFFFFA800899C940)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Thu 01.03.2012 17:16:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030112-13884-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006251A10, 0xFFFFF80000B9A518, 0xFFFFFA80058D9A50)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 27.02.2012 22:27:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022912-13759-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006275060, 0xFFFFF800033EC518, 0xFFFFFA80063F8930)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 25.02.2012 23:48:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022712-14242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800626FA10, 0xFFFFF80000B9A518, 0xFFFFFA80077667B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 22.02.2012 22:18:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022312-22308-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006275060, 0xFFFFF800033F4518, 0xFFFFFA8006589400)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

writhziden · 04 Mar 2012

We do not rely on WhoCrashed for this reason. It is telling you that Windows is causing Windows to crash. While this is possible, it is not highly likely. However, for peace of mind, we should check if there is any file corruption to Windows files.

Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

I still note one out of date driver:

Code:

nvBridge	fffff880`03b9c000	fffff880`03b9d180	Fri Jun 26 15:22:03 2009 (4a453bfb)	00010f0d		nvBridge.kmd

Make sure your nForce chipset drivers are updated.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\MortenB\Windows_NT6_BSOD_jcgriff2\030312-14742-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`037f4500?
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02261000 PsLoadedModuleList = 0xfffff800`024a6670
Debug session time: Fri Mar  2 13:29:07.333 2012 (UTC - 7:00)
System Uptime: 0 days 0:27:37.410
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006251a10, fffff800037f4518, fffffa80065787d0}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006251a10, Physical Device Object of the stack
Arg3: fffff800037f4518, Functional Device Object of the stack
Arg4: fffffa80065787d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`037f44c8 fffff800`0234bcd2 : 00000000`0000009f 00000000`00000003 fffffa80`06251a10 fffff800`037f4518 : nt!KeBugCheckEx
fffff800`037f44d0 fffff800`022e95fc : fffff800`037f4618 fffff800`037f4618 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`037f4570 fffff800`022e9496 : fffffa80`05967870 00000000`00019f03 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`037f45e0 fffff800`022e937e : 00000003`dbe4cb2b fffff800`037f4c58 00000000`00019f03 fffff800`024562e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`037f4c30 fffff800`022e9167 : 00000001`00ab95c3 00000001`00019f03 00000001`00ab9524 00000000`00000003 : nt!KiTimerExpiration+0x1be
fffff800`037f4cd0 fffff800`022d596a : fffff800`02453e80 fffff800`02461cc0 00000000`00000002 fffffa80`00000000 : nt!KiRetireDpcList+0x277
fffff800`037f4d80 00000000`00000000 : fffff800`037f5000 fffff800`037ef000 fffff800`037f4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_k57nd60a_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_k57nd60a_IMAGE_pci.sys

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

All crashes still point to pci.sys. Since they do not give the true driver causing the crashes, they are not very informative. We will have to try to fish out the underlying driver problem.

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.

The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

MortenB · 25 Mar 2012

Hi,

Thanks for all help so far!

Now I have tried to update the nvBridge.kmd driver again, but still I get BSOD. I have run the DriverVerifier and attached the BSOD info.

Best regards
Morten

writhziden · 25 Mar 2012

Security Software:

Code:

sdwinsec.exe	c:\program files (x86)\spybot - search & destroy\sdwinsec.exe	2748	8	200	1380	25.03.2012 11:27	1.0.0.12	1,10 MB (1*153*368 byte)	05.07.2010 09:20
teatimer.exe	c:\program files (x86)\spybot - search & destroy\teatimer.exe	4908	4	200	1380	25.03.2012 11:27	1.6.4.26	2,04 MB (2*144*088 byte)	05.07.2010 09:20

Do you have antivirus/malware removal software???? Recommend either of these two:

Update the security software and run a full scan of your system.

Code:

SmartDefragDriver	fffff880`018ed000	fffff880`018f4000	Fri Nov 26 02:29:40 2010 (4cef7e04)	0000be1a		SmartDefragDriver.sys

3rd party defragmenting tools can cause crashes on Windows 7.

Code:

nvBridge	fffff880`03d36000	fffff880`03d37180	Fri Jun 26 15:22:03 2009 (4a453bfb)	00010f0d		nvBridge.kmd

The driver is still out of date, unfortunately. Try to find an updated driver through nVidia. Welcome to NVIDIA - World Leader in Visual Computing Technologies

None of your recent crashes are driver verified, and all point to pci.sys due to a driver power state failure. Make sure Verifier is set up properly; there are now new steps for this...

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. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
  Attachment 204297
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
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.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

MortenB · 29 Mar 2012

Hi,

I have done the following actions:
-updated the security sw (Norman Security Suite) and done a full scan, no virus found
-scanned for spyware using Spybot, some findings, destoyed the findings
-uninstalled SmartDefragmenter tool
-activated DriverVerifier so I hope my crashes now are driver verified

But, after installing the latest drivers form NVidia, I still see that the nvBridge.kmd is not updated. I really don't know how to get an updated version installed.

I still get BSOD.

I attach the BSOD info file.

Best regards, Morten

writhziden · 29 Mar 2012

Your crashes are pointing to your Gigabit ethernet driver. You may disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and press Enter:

verifier /reset

-> Restart your computer.

Re-install Broadcom.com - Ethernet NIC NetLink Driver Downloads using the following steps:

First, download the latest driver (for Windows 7 x64). Then do the next steps.
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand network adapters
Right click the Broadcom Ethernet device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer only if Windows asks you to.
Install the latest driver for the device.

Alternatively:

Login as an adminstrative user.
First, download the latest driver (for Windows 7 x64). Then do the next steps.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand network adapters
Right click the Broadcom Ethernet device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer only if Windows asks you to.
Install the latest driver for the device.

MortenB · 31 Mar 2012

Hi,

I did the actions specified, downloaded driver, verifier /reset, uninstalled driver and installed the driver, but I still get BSOD. I haven't posted any BSOD info file since the driver verifier is turned off.

BR Morten

MortenB · 31 Mar 2012

BTW: Both the Uninstall and the Install of the driver timed out, may that cause the trouble?

BR Morten

Windows 7: BSOD when system is going to sleep mode

BSOD when system is going to sleep mode problems?