Solved Pink and Blue BSOD! And my first posting, please help.

[Gleepglop]

Ordinarily, I'd get to a problem like this, and I would re install everything, but I thought that I'd give these forums a try. So if someone can help, I would greatly appreciate it.

I have been experiencing regular BSOD, 2 to 5 a day--sometimes more. I can't figure out the cause. I haven't noticed a pattern. Sometimes things go well and my computer will work well gaming or surfing the web, and then other times it will just flash to a Pink Screen of Death. This might happen with only a document open, surfing the web, or anything really.

Attached are the files that the instructions said to attach. Please let me know if I've left anything out. Here is some brief system information:

HP Pavilion Elite m9400f
Windows 7 Ultimate 64 bit (Not Originally Installed)
I have changed the Graphics Card (in January), the power supply (in January), and the hard-drive (about 2 years ago).

 

[Jonathan_King]

Hello,

It looks like hardware is the cause here, most likely RAM. Try running each of the three Prime95 tests, as well as Memtest86.

CPU - Stress Test with Prime95

RAM - Test with Memtest86+

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 11:39:05.867 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.820
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpInterlockedPopEntrySListFault16+0
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 23 19:46:39.607 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:22.558
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+446055 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_atikmdag+446055
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 23 19:43:15.463 2011 (UTC - 4:00)
System Uptime: 0 days 11:52:45.413
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DMA_POOL::FlushPendingCPUAccess+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_dxgmms1!VIDMM_DMA_POOL::FlushPendingCPUAccess+2
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff8a0`0c5f7b00
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff8a0`0c5f7b00
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 21 11:28:19.860 2011 (UTC - 4:00)
System Uptime: 0 days 2:27:38.810
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff8a0`0c5f7b00
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff8a0`0c5f7b00
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 21 08:42:47.653 2011 (UTC - 4:00)
System Uptime: 0 days 12:44:07.229
Probably caused by : win32k.sys ( win32k+27999 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+27999
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul 20 08:39:32.773 2011 (UTC - 4:00)
System Uptime: 0 days 12:47:54.723
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xc4_91
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_91_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jul 19 19:49:55.379 2011 (UTC - 4:00)
System Uptime: 0 days 2:29:43.330
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiUpdateContextStatus+de
BiosReleaseDate = 06/20/2008
SystemProductName = FK790AA-ABA m9400f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for Unknown_Module_00330063`007b0074
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00330063`007b0074
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 18 10:53:28.770 2011 (UTC - 4:00)
System Uptime: 4 days 7:33:24.326
*** WARNING: Unable to verify timestamp for Unknown_Module_00330063`007b0074
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00330063`007b0074
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Gleepglop]

Thanks Jonathan, I'm running the Prime95 tests now. Will post tomorrow with any results, and I'll try the Memtest too.

 

[Gleepglop]

Ok, 11 hours of Prime95 Stress Testing with nothing to report, no errors and no warnings. I'll run the Memtest in a few hours.

Would bad RAM show up on a Prime95 test?

 

[Jonathan_King]

Bad RAM should be flagged by Prime95, but might slip by depending on the nature of the problem. Sometimes, bad RAM passes all software diagnostics but still turns out to be the cause of the problem.

 

[Gleepglop]

Hi Jonathan, (thanks for your helps so far)

Ok, I've run all those tests. Nothing is coming up as a problem. I ran Memtest for about 5 hours without any errors.

Interestingly enough, since I've been running these tests, the computer hasn't been experiencing any problems. Yesterday afternoon I had many crashes, and it was hard to get it started long enough to run Prime95, but once I did... no problems.

Thoughts? More tests?

 

[Gleepglop]

I just ran the middle test in Prime95... I think it said something about lots of heat... Anyway, about 6 minutes into that, the computer crashed.

Is there a way to determine whether this is a heat issue, Ram issue, or both?

 

[Gleepglop]

Ok, after the most recent crash (listed above), I shut off my machine for about an hour and a half. Then I booted the machine up and ran the middle Prime95 test again (the one that caused the previous crash) and it ran and ran with no problems for an hour. Core temperature got up to about 60C and Motherboard temp hovered around 58C.

 

[Jonathan_King]

Try opening the side of the case and blowing a fan inside. Also clean out all dust while you're in there. Run Prime95 again, and see what the temps are like.

 

[Gleepglop]

I removed the dust from the case about two days ago... just before writing to the forum. Should I run the Prime95 test while I have an additional fan blowing inside the case?

 

[Jonathan_King]

Yes, go ahead.

 

[Dave76]

Can you fill in your system specs?

Lower left corner of any of your posts,'My System Specs'.
This will help anyone reading your thread.

 

[Gleepglop]

Turns out it was the RAM after all.

I wanted to close this thread, and say thanks for your help. A couple weeks ago, I took out 2 of my RAM modules (4GB) and everything has been running smoothly since.

I will put them back in, one at a time, to see which one is the problem, but in the meantime, I'm counting this as closed and solved!

Thanks again for your help!

 

[Dave76]

Glad to hear you found the cause.

Best way to find out if one of the RAM cards are bad it to run memtest86+ with only one of the suspected bad RAM cards installed at a time.
Run memtest86+ for a full 7 passes, this will take several hours, best to run overnight. You can stop the test if you get any errors.

If all the cards pass memtest86+, you might just need to adjust some of the settings.

It's very common requirement to bump the memory controller and/or RAM voltage if you have more than 4GB RAM or 4 RAM cards installed.

Let us know how the testing goes.


With a little information we might be able to suggest something.
Download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums