BSOD on resume from standby, but only sometimes

[naughtymonkeybo]

Hello, and thank you in advance for any help you may offer.

I put this computer together April 2008 and installed Windows XP on a 640G drive. In April 2011 I installed a second hard drive, a 300Gig Velociraptor, and installed an OEM version of Windows 7 Home Premium x64; XP is still on the first hard disk, and I do not dual-boot. On November 12, 2011, I upgraded from 2Gigs Corsair RAM to 4Gigs Crucial RAM.

I've been getting BSOD after resuming form sleep mode for a week or so. If I go into sleep mode and then resume right away, there is no problem; otherwise, the computer may reboot when I resume from standby. I may get to the logon screen and enter my password before BSOD reboots the system.

My wife, who has her own logon, told me that "the computer has been acting weird lately." She told me this morning that she couldn't launch a browser to send an email.

The problems may have started after I used CCleaner, but I'm not sure.

I have one unknown device in device manager that has had no driver since the W7 install, but it hasn't been a problem. After using Uniblue's driver scanner to update drivers, I have an additional 3 items that cannot start (two Microsoft ISATAP Adapters and a Teredo Tuneling Pseudo-Interface.)

I believe that the Windows_NT6_BSOD_jcgriff2 is zipped with the system health report; I've not zipped files before this.

Again, thank you for any help you may offer.

P.S. I've tried system restore, but the problem remained.

 

[zigzag3143]

Hello, and thank you in advance for any help you may offer.

I put this computer together April 2008 and installed Windows XP on a 640G drive. In April 2011 I installed a second hard drive, a 300Gig Velociraptor, and installed an OEM version of Windows 7 Home Premium x64; XP is still on the first hard disk, and I do not dual-boot. On November 12, 2011, I upgraded from 2Gigs Corsair RAM to 4Gigs Crucial RAM.

I've been getting BSOD after resuming form sleep mode for a week or so. If I go into sleep mode and then resume right away, there is no problem; otherwise, the computer may reboot when I resume from standby. I may get to the logon screen and enter my password before BSOD reboots the system.

My wife, who has her own logon, told me that "the computer has been acting weird lately." She told me this morning that she couldn't launch a browser to send an email.

The problems may have started after I used CCleaner, but I'm not sure.

I have one unknown device in device manager that has had no driver since the W7 install, but it hasn't been a problem. After using Uniblue's driver scanner to update drivers, I have an additional 3 items that cannot start (two Microsoft ISATAP Adapters and a Teredo Tuneling Pseudo-Interface.)

I believe that the Windows_NT6_BSOD_jcgriff2 is zipped with the system health report; I've not zipped files before this.

Again, thank you for any help you may offer.

P.S. I've tried system restore, but the problem remained.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[naughtymonkeybo]

I ran Memtest86 for 34 passes in 30 hours with no errors. Does that mean that the memory and slots are 100%?

Driver verifier does look iffy.

 

[zigzag3143]

I ran Memtest86 for 34 passes in 30 hours with no errors. Does that mean that the memory and slots are 100%?

Driver verifier does look iffy.

I would say the ram is OK. Next step verifier.

 

[naughtymonkeybo]

I just came back from travel away from home; my wife says that the computer blue screened many times while I was gone; the computer was no longer booting up. I pulled out the new RAM and put the old back in: sometimes it boots, but not always.

The POST code (C1) gets stuck on "Detect Memory - Auto-detection of DRAM size, type, and EEC - Auto-detection of L2 cache (socket 7 or below)"

I doesn't happen with every reboot; it does happen with either stick in different slots. The RAM is rated to run at 2.2V. If I set the Bios to run RAM at auto-detect voltages (1.8V), I can't get past C1.

I'm wondering if my board is going bad, or if it's the RAM.

 

[mgorman87]

Please upload a new report if you can

 

[naughtymonkeybo]

Thank you; here are the new reports.View attachment 195195

 

[mgorman87]

Are you still having problems booting?

Please remove the over clock on your CPU

Update your BIOS - Universal abit > Motherboard, Digital Speakers, iDome, AirPace, Multimedia

Find your motherboard from the list and download the most recent revision

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 03:25:57.889 2012 (UTC - 5:00)
System Uptime: 0 days 11:25:36.249
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 15:59:44.296 2012 (UTC - 5:00)
System Uptime: 0 days 13:35:27.672
*** WARNING: Unable to verify timestamp for tdrpm273.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm273.sys
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : tdrpm273.sys ( tdrpm273+4d88d )
BUGCHECK_STR:  0x34
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x34_tdrpm273+4d88d
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 02:23:32.996 2012 (UTC - 5:00)
System Uptime: 8 days 0:29:35.371
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 21:50:27.736 2012 (UTC - 5:00)
System Uptime: 0 days 9:58:20.048
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 11:51:11.425 2012 (UTC - 5:00)
System Uptime: 0 days 13:46:37.800
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 17:52:13.235 2012 (UTC - 5:00)
System Uptime: 0 days 1:54:55.610
Probably caused by : ntkrnlmp.exe ( nt!ObfReferenceObjectWithTag+1c )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ObfReferenceObjectWithTag+1c
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 15:56:47.660 2012 (UTC - 5:00)
System Uptime: 0 days 1:36:10.035
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 14:20:08.770 2012 (UTC - 5:00)
System Uptime: 0 days 0:47:30.129
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  1 19:34:11.500 2012 (UTC - 5:00)
System Uptime: 1 days 20:21:42.796
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::ResetBackingStore+11e )
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_SEGMENT::ResetBackingStore+11e
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec 30 23:09:39.000 2011 (UTC - 5:00)
System Uptime: 3 days 6:31:57.375
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsCleanupIrpContext+58b )
PROCESS_NAME:  svchost.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCleanupIrpContext+58b
BiosReleaseDate = 09/06/2007
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 3006
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[naughtymonkeybo]

I have previously attempted to update my BIOS; the update was slightly larger than what would fit on a floppy.

 

[mgorman87]

I have previously attempted to update my BIOS; the update was slightly larger than what would fit on a floppy.

A floppy? BIOS updates are usually done through Windows. I didn't even think people had floppy drives any more

EDIT: I guess this one doesn't have one. You can put it on a USB thumb drive or even a CD
http://www.abit.com.tw/page/en/download/guide.php

 

[zigzag3143]

Some other possible causes include your AVG, and Daemon tools.

I would remove both at least to test.

AVG can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows



Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files