Solved BSOD only in sleep mode, BCCode: 1000007e, BCP1: FFFFFFFFC0000005

[tkay11]

I installed a new motherboard, memory and CPU 3 weeks ago and get BSODs irregularly whilst the computer is in sleep mode.

I did not re-install Windows, as it worked just with automatic reinstallation of new drivers.

I have re-installed drivers (especially the video drivers) and restored back to the install date without improving the problem.

I have also run the extended MemTest on the 8GB Kingston memory, which reports no issues.

The graphics are being run by the onboard graphics set together with an Intel Pentium 3020.

The following is the latest statement from Windows recovery:

BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88000E1E977
BCP3: FFFFF8800372A7C8
BCP4: FFFFF8800372A020
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

I attach the debug file obtained after using the DM log collector.

I would be grateful for any suggestions as to the cause.

Thanks

Tony

 

[koolkat77]

Wrong analysis will get back with the correct ones..

 

[koolkat77]

Hi.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

hcw99bda.sys Thu Mar 22 01:32:58 2007 (4601886A)
Hauppauge Nova-DT (99xxx) driver
Driver Reference Table - hcw99bda.sys

hcw99rc.sys Thu Mar 22 01:33:13 2007 (46018879)
Hauppauge Nova-DT (99xxx)
Driver Reference Table - hcw99rc.sys

RimSerial_AMD64.sys Mon Nov 24 23:01:01 2008 (492ADDCD)
Virtual Serial Port driver for Blackberry
Driver Reference Table - RimSerial_AMD64.sys

gdrv.sys Fri Mar 13 09:22:29 2009 (49B9D175)
Gigabyte Easy Saver - mobo power utility driver
Driver Reference Table - gdrv.sys

HECIx64.sys Tue Dec 18 01:32:21 2012 (50CF7345)
Intel Management Engine Interface
Driver Reference Table - HECIx64.sys

AppleCharger.sys Tue Feb 19 10:17:09 2013 (5122FCC5)
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - (uninstall to test)
Driver Reference Table - AppleCharger.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Test your Hardware for Stability and Heat Problems with Prime95. Be sure to keep an eye on your temperatures when running these tests, especially the Large FFTs:

• Stress Test With Prime95

How to Stress Test a Video Card with Furmark:

• Video Card - Stress Test with Furmark

Test your CPU Stability with IntelBurnTest:

• CPU - Stress Test Using IntelBurnTest

BSOD DUMP OUTPUT

[FONT="Lucida Console"]Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Mar 14 22:25:29.541 2014 (UTC + 6:00)
System Uptime: 0 days 8:03:32.493
BugCheck 1000007E, {ffffffffc0000005, fffff88000e1e977, fffff8800372a7c8, fffff8800372a020}
Probably caused by : ACPI.sys ( ACPI!GetNameSpaceObject+11b )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sat Mar  1 23:33:09.578 2014 (UTC + 6:00)
System Uptime: 0 days 5:53:23.530
BugCheck 3B, {c0000005, fffff88001cb9d62, fffff8800821dd70, 0}
Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+2fd3a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

 

[tkay11]

Thanks a lot, Koolkat77, for such an incredibly rapid and detailed response. I'll get working on it today and will post back results.

Tony

 

[tkay11]

OK, I've been through all the rituals. Kept on getting BSODs in sleep mode. Then, after doing an all-night check with MemTest which again showed no problems with memory, I booted into Windows 7 Safe Mode because Windows was starting without one of its essential services. I didn't do a thing except re-boot from Safe Mode. Since then, the computer has been working without a problem.

I did investigate the drivers for a wide range of programmes, and deleted some of the start up programmes using msconfig, but that hadn't done anything. I also investigated the drivers causing the crashes using BlueScreenView.exe, but this just revealed that while ntoskrnl.exe showed up most of the time, there were a variety of others being reported as problematic at different times (hal.dll, acpi.sys, tcpip.sys, ndis.sys) so there didn't seem to be any particular single driver that had caused the problems.

I am leaving this thread open for a couple more days in case any one wants to comment on this, but otherwise I just have to close the thread as solved, albeit in a mysterious way that seemed to have nothing to do with what I did.

Thanks for all the help, though!

Tony

 

[tkay11]

OK, I'm closing this now. I have a feeling it's a Windows 7 power saving issue related to USB function during sleep, since there seems to be no problem when no usb drives are attached. I'll try changing the settings in the Power Management part of the device settings. I've heard that works, as well as turning off the 'Link State Power Management' in the Power Management part of Control Panel.

Thanks very much to Koolkat 77 for guiding me throught the vagaries of BSODs -- I sure have learned a lot from this experience!

Tony