Reluctantly Posting

[Sinrider]

Hi guys,

I have been struggling with a new computer for a few months. Every time I think I have the upper hand, the issues creep back, like a persistent ex.

So, I'm swallowing my pride and trying with you. I built this computer in March and since then, I've had very sporadic BSoDs. They will pop up when I'm doing nothing at all or when I'm in the middle of nuking the crap out of a boss in World of Warcraft.

My fear and suspicion is that I have a bad piece of RAM or something like that. However, I have run RAM diagnostics without any sign of bad sticks. Help?

Lynn

 

[Jonathan_King]

Welcome!

No shame in posting, it says nothing about your computer skills. I have seen people on other forums try to diagnose a BSOD without looking at the dmps, and their advice is vague, inconvenient, expensive, and often takes dozens of posts to solve, if they ever do.

The dmps suggest hardware. In particular, I suspect RAM and video card. I know you ran some memory diagnostics already, but frankly, I don't trust anything other than Memtestx86.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Let us know the results if the tests. We can also do a CPU and driver test if need be.

[font=lucida console]
BugCheck 1A, {41284, 5c26001, 178d, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {28, 2, 0, fffff80002cb3410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff880041cdcee, fffff88001f2e6a8, fffff88001f2df10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 34, {50830, fffff88002f8c738, fffff88002f8bfa0, fffff80002c72651}
Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+5e2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {403, fffff68000053930, 89900000af6a9867, fffff6fc80618a9a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff80002d0ffa2, fffff88002ffc848, fffff88002ffc0b0}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {5003, fffff70001080000, 2094, 209600000128}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f97 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {403, fffff68000006650, 9c50000036fc3847, fffff68000043530}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {28, 2, 0, fffff80002cff410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {ffffb80002c94752, 2, 8, ffffb80002c94752}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 19, {3, fffff80002e4f520, fffff80002a4f520, fffff80002e4f520}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Sinrider]

I'll give the tests a go and let you know what I find. Thanks!

 

[Sinrider]

For the GPU stress test, how long should I let it go for? I left it going for a few minutes and it hit about 84 degrees and hovered right around there.

 

[jameslkerr]

I have used Furmark in the recent past, I left it running for about 4 hours and my temp didn't go over 80 degrees during that entire time. But, I have also spent time in the recent past using Furmark to properly set my fan speeds (100% on my card sounds like a jet engine inside my case ... insanely loud).

Since your specs show that you are using a Radeon, I will recommend opening the Catalyst Control Center, then go to the top left corner, click on Graphics, then ATI Overdrive (last item in the drop down). Once here, you may have to click the Padlock in order to Unlock the settings. Once you have unlocked the settings, you need to check the Enable ATI Overdrive (I would not mess with the GPU or Memory settings, but you need this box checked in order to control the fan). Now, checkmark the Enable Manual Fan Control box. This screen will show you both the current temperature and the fan speeds.

I like to leave this open, then start FurMark and adjust the fan speed to a sound level I am comfortable with, while continuing to keep the temperature in a safe range.

I personally think that ATI's fan control is a little too dangerous ... I have left it alone before, and it just seems to run way to hot for my liking. That is my I keep it under control myself.

 

[Sinrider]

This screen will show you both the current temperature and the fan speeds.

What temperature should I look for on the graphics card? 80s seemed to be edging into the warmer zone. What would be considered average running temp? I've run World of Warcraft on full tilt graphics for hours on end without it missing a beat.

Download a copy of
Memtest86

Done. It went through about 6 passes (4 hours) before I turned it off. Looks like there were 8 errors (occurring in pairs). Is there a log file I can pull? Or did I miss that? >.<

 

[Jonathan_King]

Try testing the sticks individually. If you find a good one, test it in all slots.