<X64> Help! Random BSOD issue

[bmacster]

First of all, great place! I wish I found this sooner

I recently completed a home built machine back in May of 2009 and has been running flawlessly up until the last month or so. At first I thought it was poor cooling but after checking with a infrared temp gauge everything was running cool, except for the memory. From June until now, I have been having extremely random BSOD. Yesterday had 7 BSOD (while the system was idle) and today was 6 (while browsing the internet) and they normally happen when the computer is sitting idle. The other times when it happens is when I am photo editing or in Firefox. I never had this issue when playing any games (Command and Conquer, Crysis, Fear, etc) Removing Photoshop and Firefox does not resolve the issue.

I am not the greatest when it comes to reading mini-dump files but the files themselves vary so much which is why I have came on here for help. The jest of it almost seems like it is a memory issue but then there are several NT and SYS dumps as well.

Attached is the mini dumps for this month.

I have not installed anything or downloaded anything except for the Windows updates. I am the only user of this system.

Sys Specs;

Antec P180
Gigabyte GA-EP45-UD3R (not overclocked...did not update BIOS)
WD 500GB green drives - RAID 0
Intel E5200 with boxed cooler
Crucial Ballistix 8GB DDR2 @ 4-4-4-12
EVGA GeForce 9800GTX+

Thanks for your advice and input on this issue!

 

[SquonkSC]

First of all, great place! I wish I found this sooner

I recently completed a home built machine back in May of 2009 and has been running flawlessly up until the last month or so. At first I thought it was poor cooling but after checking with a infrared temp gauge everything was running cool, except for the memory. From June until now, I have been having extremely random BSOD. Yesterday had 7 BSOD (while the system was idle) and today was 6 (while browsing the internet) and they normally happen when the computer is sitting idle. The other times when it happens is when I am photo editing or in Firefox. I never had this issue when playing any games (Command and Conquer, Crysis, Fear, etc) Removing Photoshop and Firefox does not resolve the issue.

I am not the greatest when it comes to reading mini-dump files but the files themselves vary so much which is why I have came on here for help. The jest of it almost seems like it is a memory issue but then there are several NT and SYS dumps as well.

Attached is the mini dumps for this month.

I have not installed anything or downloaded anything except for the Windows updates. I am the only user of this system.

Sys Specs;

Antec P180
Gigabyte GA-EP45-UD3R (not overclocked...did not update BIOS)
WD 500GB green drives - RAID 0
Intel E5200 with boxed cooler
Crucial Ballistix 8GB DDR2 @ 4-4-4-12
EVGA GeForce 9800GTX+

Thanks for your advice and input on this issue!

Hi and welcome bmacster,

We have to start somewhere, and the first thing to do is this:

Take out all RAM except 2gb.
See if that helps.
Exchange that strip with the next 2gb and so on.

if they are all good, put them in 2 strips at a time. So make different combinations of 4gb, and check again.

If a Ram strip is bad, you should get to the culprit soon enough.

If you keep getting BSOD's with all of the single Ram strips, we can safely rule that out and go from there.

Good luck

 

[bmacster]

Thanks for the welcome squonksc!

I will go ahead and try that now, though as of right now, it is running completely stable and hasn't crashed for almost an hour now.

This is the entire random part. The next time it decides to dump could be as I am typing this to a few weeks from now.
http://www.sevenforums.com/member.php?u=16846

 

[zigzag3143]

First of all, great place! I wish I found this sooner

I recently completed a home built machine back in May of 2009 and has been running flawlessly up until the last month or so. At first I thought it was poor cooling but after checking with a infrared temp gauge everything was running cool, except for the memory. From June until now, I have been having extremely random BSOD. Yesterday had 7 BSOD (while the system was idle) and today was 6 (while browsing the internet) and they normally happen when the computer is sitting idle. The other times when it happens is when I am photo editing or in Firefox. I never had this issue when playing any games (Command and Conquer, Crysis, Fear, etc) Removing Photoshop and Firefox does not resolve the issue.

I am not the greatest when it comes to reading mini-dump files but the files themselves vary so much which is why I have came on here for help. The jest of it almost seems like it is a memory issue but then there are several NT and SYS dumps as well.

Attached is the mini dumps for this month.

I have not installed anything or downloaded anything except for the Windows updates. I am the only user of this system.

Sys Specs;

Antec P180
Gigabyte GA-EP45-UD3R (not overclocked...did not update BIOS)
WD 500GB green drives - RAID 0
Intel E5200 with boxed cooler
Crucial Ballistix 8GB DDR2 @ 4-4-4-12
EVGA GeForce 9800GTX+

Thanks for your advice and input on this issue!

While waiting for someone with a true debugger I took a quick look at 5 of the BSODS, and it seems like 2 things repeat themselves. Partmgr.sys, and ntorkrnl. I would bet the RAID 0 controller is not working correctly and that is making ntoskrnl choke and die. I would get updated drivers for the raid controller, and bios. See if that cures it. Our Dump guru will probably jump in when he comes online later.

Hope this helps

Ken

 

[SquonkSC]

Thanks Ken.

Bad sectors on the disk could also kill those.

Try and download some free diagnostic tools for both disk and ram.

greetz.

 

[bmacster]

I am back with an update;

I ran memtest86 and one stick had a error. The one stick that did have the error, later passed 8 additional tests without an error...

I did defrag and test the HD's just in case it was an issue and no bad sectors or any other problems came up during the tests.

I am downloading the MB BIOS and trying to find the RAID BIOS (Are they actually separated or the same?)...

I found the drivers for the RAID controller that are newer than what I have (RAID n00b here..) but like I said before, it was working perfect the first month, harsh loads, gaming, heavily stressing it on purpose.

I am heading out to Frys Electronics to buy a RAM cooling fan since it is running so hot (175F currently)

 

[usasma]

80º C us awfully hot for the memory. Until the memory is cooled down, I'd suspect that you will experience BSOD's.

This is especially true if there's an error in one of the sticks - even if it's only one error. There's 2 schools of thought on memory errors:
- one believes that a couple of errors are acceptable, and the error correcting mechanisms of the system will take care of it.
- the other side is that any errors are unacceptable - I belong to this group. My example is that an error of 1 in your checkbook doesn't mean much if it's in the cents column, but it does mean a lot in the $1000 column! IMO it's just not worth the chance!

Could the heat have caused the RAM to break down - or did the heat cause the failure of the already defective RAM? I dunno. I'd leave that stick out until you've finished testing the rest of the system tho' - just in case it is the problem. I also wonder why the memory is running so hot - is this "normal" for your system? Are you running any apps that require the memory to do a lot of number crunching?

The memory dump files are pretty random (7 different error messages for the 13 memory dumps) - implying that it's either a hardware problem, or that the offending party has exited before the crash occurs. The involvement is primarily memory systems - but there is a significant number related to the storage systems too.

There's about a 10 day gap between the older dump files, and the newest one's. Can you recall anything about the system that may have occurred in that period?

In short, I'd suspect that this was due to the heat of your memory - with additional issue that could be caused by your storage drivers. But I wonder how close the storage controller is to your memory - maybe it's overheating also?

As a test, you may want to point a house fan into the case (with the side off), turn it on high and see if that improves things. If it does, then you're in the market for a better cooling solution.

Here's a summary of the last 13 memory dumps (27 & 28 Aug):

Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 22:21:19.243 2009 (GMT-4)
System Uptime: 0 days 0:01:08.977
BugCheck 50, {fffff8a0ff51f554, 0, fffff880012295b0, 5}
Probably caused by : Ntfs.sys ( Ntfs!memcmp+30 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 22:18:39.547 2009 (GMT-4)
System Uptime: 0 days 0:55:32.282
BugCheck 50, {fffffa8051310af4, 1, fffff8800104e48b, 5}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+190 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgdumpa.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 22:23:12.671 2009 (GMT-4)
System Uptime: 0 days 0:00:21.406
BugCheck 1000007E, {ffffffffc0000005, fffff800029a8033, fffff880009b0638, fffff880009afe90}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 21:21:37.828 2009 (GMT-4)
System Uptime: 0 days 0:00:27.562
BugCheck 50, {fffff8000088dc90, 8, fffff8000088dc90, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3f7b3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 15:23:18.272 2009 (GMT-4)
System Uptime: 0 days 0:01:41.991
BugCheck D1, {fffff80004d0ba8a, 2, 1, fffff80003d0ba93}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+12c540 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Aug 27 15:20:00.521 2009 (GMT-4)
System Uptime: 2 days 13:15:21.255
BugCheck 24, {1904fb, fffff88009fae918, fffff88009fae170, fffff880014ca09b}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  avgcsrva.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:15:31.485 2009 (GMT-4)
System Uptime: 0 days 0:56:58.219
BugCheck 4E, {99, 1efa1, 0, f0f0f000f0f0f0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:20:19.166 2009 (GMT-4)
System Uptime: 0 days 0:00:35.900
BugCheck 3B, {c0000005, fffff88001021633, fffff88008624990, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltGetEcpListFromCallbackData+3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  taskhost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:23:29.875 2009 (GMT-4)
System Uptime: 0 days 0:02:02.406
BugCheck 19, {3, fffffa80069934d0, 0, 80}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a54 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:25:36.529 2009 (GMT-4)
System Uptime: 0 days 0:01:03.263
BugCheck A, {48, 2, 1, fffff8000292586f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:17:03.249 2009 (GMT-4)
System Uptime: 0 days 0:00:26.983
BugCheck 3B, {c0000005, fffff800028a3509, fffff88006b76ee0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PsChargeProcessNonPagedPoolQuota+9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgrsa.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Fri Aug 28 11:18:39.266 2009 (GMT-4)
System Uptime: 0 days 0:00:27.000
BugCheck 1000007E, {ffffffffc0000005, 0, fffff8800334f348, fffff8800334eba0}
*** WARNING: Unable to verify timestamp for iaStorV.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
Probably caused by : partmgr.sys ( partmgr!PmReadWrite+123 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System