Random BSOD's

usasma · 20 Feb 2012

We don't know what causes it - if we did, we'd be doing it over and over in order to get results that we can work with. Stressful usage is definitely one way to increase the frequency - but so is Driver Verifier (and it's more informative).

Most BSOD's are caused by 3rd party software/driver problems
The next most common cause is hardware
Then comes Windows problems

3rd party stuff:
We rule out 3rd party software/drivers by removing it. We manually scan for programs with known problems and ask you to remove them. If the software is needed, we rule it out by removing the current version from the computer and installing a fresh copy that's known to be compatible with the OS. FYI - malware falls into this category also - so anti-malware scans are a part of the diagnostics (but we let others fix malware problems - it's too specialized for us to do here).

Hardware:
We rule out some hardware issues by running diagnostics.
We rule out others by removing hardware or substituting known good hardware for the hardware that's questionable.
That leaves us with only a few pieces that aren't easy to remove/replace and/or are too expensive

Windows:
Windows problems are relatively easy - update Windows and run SFC.EXE /SCANNOW
If that's not enough, a clean install will put the system in a state where Windows most likely isn't the problem (so if the errors continue, Windows is ruled out).

Jamy981 · 20 Feb 2012

After some 12 hours of testing, my system decides to crash a mere hour into me actually using it for what I want to do.
BSOD was MEMORY_MANAGEMENT
Have turned Driver Verifier off for the time being
Mini Dumps included....

Any suggestions?

What is the probability of this problem recurring if I were to upgrade my Motherboard, Processor and RAM?

Might go and buy a cheap keyboard tomorrow and re-install windows.....

usasma · 20 Feb 2012

If you replace everything - the original problem will go away.
But you'll have a new problem - much less money!

Driver Verifier is supposed to cause BSOD's. If it doesn't cause a Driver Verifier BSOD in 36 hours of use, we presume that it's not a 3rd party driver problem (because that's what we set it to test for).

In this case, the last memory dump was a Driver Verifier enabled memory dump - and it blamed a Windows driver (dxgmms1 - a DirectX driver). Since we tested for 3rd party drivers, this is either a hardware problem or a Windows problem (since Driver Verifier didn't point out a 3rd party driver when it caused the crash).

Also, the last 3 memory dumps were all different - which usually suggests a hardware issue. BUT, the line blurs a bit here - as these hardware issues also include:
- compatibility issues
- low-level driver problems
- malware

We've checked for the most common of the above issues. I see no sign of compatibility, low-level driver problems, or anything suggestive of malware. So, again, we must suspect hardware.

So, have you run all of the hardware tests that I suggested? I can't recall you posting the results of a CPU stress test. How about the other video tests (other than Furmark and the MemtestG80 and MemtestCL test thingy)

If so, then we've gotta start looking at other things (the cheap keyboard is a good idea for now).
Then try this procedure to start ruling things out: Hardware Troubleshooting Via System Stripdown
Remember from earlier - if it's video related, and we rule out the video stuff, then we've gotta suspect the motherboard.

Good luck!

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


vmbus.sys         Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys         Sat Nov 20 04:20:02 2010 (4CE792C2)
nvstor.sys        Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys      Fri Apr 09 05:22:41 2010 (4BBEF1E1)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dump_nvstor64.sys Fri Apr 09 05:22:41 2010 (4BBEF1E1)
MpFilter.sys      Wed Apr 06 16:07:29 2011 (4D9CC801)
atikmpag.sys      Mon Dec 05 21:12:14 2011 (4EDD79FE)
nvmf6264.sys      Thu Mar 04 20:04:39 2010 (4B9058A7)
atikmdag.sys      Mon Dec 05 21:52:23 2011 (4EDD8367)
AtihdW76.sys      Tue Oct 18 03:09:49 2011 (4E9D263D)
MpNWMon.sys       Wed Apr 06 16:07:23 2011 (4D9CC7FB)
NisDrvWFP.sys     Wed Apr 06 16:08:53 2011 (4D9CC855)
mbam.sys          Wed Nov 02 09:07:48 2011 (4EB140A4)
ALSysIO64.sys     Sat Jul 09 20:27:45 2011 (4E18F201)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022012-19125-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 20 17:13:52.232 2012 (UTC - 5:00)
System Uptime: 0 days 2:12:40.011
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
BUGCHECK_STR:  0x1a_411
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`5006c100 aea00000`a7c47882 f0000000`f0000001
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4500  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022012-16926-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 20 05:07:20.822 2012 (UTC - 5:00)
System Uptime: 0 days 0:40:11.476
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::DdiOpenAllocation+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  JagexLauncher.
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGADAPTER::DdiOpenAllocation+4d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0551ccc1 fffff880`0494ca00 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4500  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021912-15397-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 19 14:58:43.347 2012 (UTC - 5:00)
System Uptime: 0 days 0:20:14.321
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+447c6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+447c6
Bugcheck code 00000050
Arguments fffff7ff`f2dc73c4 00000000`00000008 fffff7ff`f2dc73c4 00000000`00000002
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4500  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Jamy981 · 20 Feb 2012

My bad, completely missed the CPU Stress test off the list, just figured I had tested the CPU with Prime95.
Will run the CPU stress test in a minute.

Also your link http://nvworld.ru/utilities/vmt/ is reported by malwarebytes to be unsafe.....

I didn't know what the Artifact Locator was and didn't want to try the last one that you said "USE AT YOUR OWN RISK," I'd rather not make my system worse if possible

The game I am playing that seems to crash alot on has 3 video options: DirectX, OpenGL, or Software, it is set to DirectX, perhaps using one of the other for the time being see if BSOD's decrease/increase?

And as a side note, I have suspected my Motherboard for a while now, which is a pain, not cheap to replace, but I just don't understand why the system was stable with my 8800GT card but not the Radeon HD5850.

Jamy981 · 20 Feb 2012

CPU test seemed to pass,results included.
Will have a look at the hardware troubleshooting.

Possibility of being able to borrow another 775 motherboard next weekend to test with, which would be pretty usefull

fingers crossed.

Random BSOD's

Eurghhhh

passed