Get the Crash Cart!

I just finished my first Windows 7 system a few weeks ago. A curious issue occurred about two weeks ago.

Whenever I shut down my computer for a few hours, then start it back up, about 5 minutes after the start up is complete, my PC has a memory management error. What makes this curious, though, is the fact that once the PC is up and running, I receive no further BSOD. Similarly, if I just restart the computer, all is well. Or, when I just go into sleep mode and restart normally, there is no issue. In addition, running in safe mode doesn't replicate the problem, either.

Here's my system information:

Windows 7, x64
- OEM

Age of the hardware is relatively new, as well as the installation date.

I cannot seem to generate a System Health Report. I'm getting the apparently common message (page not found).

Thanks for the read.

The Howling Wolves said:

I may have given you the wrong restore tutorial so try this one.
System Restore

Thank you, but unfortunately a system restore at this point isn't possible. As I said, this problem occurred weeks ago. I originally assumed it was a fluke, albeit, a reoccurring one (since again, when I restart, or come out of sleep mode, the problem didn't exist anymore).

At this point, the earliest restore point on my PC is last week.

The problem is progressively getting worse. It seems the "grace period" I had is starting to diminish. I managed to grab a system report, however. Including in this .zip is a system report and the BSOD Dump & System File Collection.

Jonathan_King said:

I suspect bad RAM; however, let's try software too.

Remove AVG with this tool: http://download.avg.com/filedir/util...removerx64.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

Are you overclocking your video card at all? If so, reset to defaults.

Now, test RAM. Follow Part 1 of this tutorial: RAM - Test with Memtest86+

Leave the CD or USB drive attached, and then shut down for the night. In the morning, immediately boot to the CD/USB and start testing first thing.


...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 19:18:53.079 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:07.561
BugCheck 1A, {5002, fffff70001080000, 3e8e, 1003e8ffffffffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f42 )
BUGCHECK_STR:  0x1a_5002
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 19:12:14.999 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:09.482
BugCheck 1A, {41790, fffffa80031472d0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 19:05:49.639 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:55.122
BugCheck 24, {1904fb, fffff88008ea1a98, fffff88008ea1300, fffff800030e4980}
Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+24d )
PROCESS_NAME:  WerFault.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 18:57:12.209 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:58.692
BugCheck 24, {c08a2, 0, 0, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 18:49:26.265 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:10.765
BugCheck 1000007E, {ffffffffc0000005, fffff880011a69c7, fffff8800271dab8, fffff8800271d320}
Probably caused by : volsnap.sys ( volsnap!VspLaunchAdjustBitmapContext+87 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 18:33:36.500 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:52.983
BugCheck 1A, {41284, 23c5001, 476, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  AOLacsd.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 18:13:22.049 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:23.157
BugCheck 1A, {5002, fffff70001080000, 76e, fefffffffffffffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2971c )
BUGCHECK_STR:  0x1a_5002
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

No, I'm not overclocking.

I suspected ram as well. When I was done with the assembly of the PC, I noticed the system only recognized 4 GIGs and not 6. So I moved the ram to another slot and the 6 GIGs appeared. This BSOD developed around the same time as the switch, but it wasn't an obvious problem because of all the new software that was put into the system around that time.


The reason why I'm saying all of this is because I needed something like this ram test to put my mind at ease about the ram. After 7 passes, there were no errors found. This is a big thing for me. As I said, I was concern it was hardware.


Now, after some trouble shooting, I noticed my laptop had flash the same BSOD. The only thing in common with the desktop and laptop is a program called Automatic Wallpaper Changer (AWC). I uninstalled it on my desktop last night, which made the BSOD disaapear. But, I won't know for sure if this software was the villain behind this, as this could be another fluke. I won't know until I shutdown my PC and restart, which I'll do momentarily.

My next concern is finding an alternative wallpaper changer!

Also, I uninstalled AVG for MSE. I actually had no idea Microsoft had such a software. I read the reviews about it, so despite paying money for AVG, I'm going to switch over to MSE, anyway.

It appears the problem is back. I shutdown the PC over night, and upon reboot, the same BSOD popped up. Any suggestions? I actually went as far as to fiddle with the ram and everything started up fine (put 4 gigs instead of 6). I went back and added the third stick of ram and lo and behold, the PC started up fine. Did my .DMP files say anything?