I was hoping to get some input from those of you who are more tech-savvy than myself when it comes to checking out BSoD error messages.

System Specs:
AMD Phenom II X4 955 BE @ 3.2GHz
ATI Radeon HD 5870
OCZ ModXStream Pro 500W Modular PSU
GIGABYTE GA-770TA-UD3 Motherboard
8GB DDR3 RAM (2x4GB) - CEON
Seagate 500GB 7200RPM HDD

I've been experiencing very random BSoD's rather frequently (every other day or so), and I can't seem to pinpoint anything that seems to cause it - however, they do seem to occur under idle or simple tasks (web surfing), as I've never crashed with the system under load (gaming, etc).

I've run the Windows Diagnostic Memory Test program for 8 cycles overnight, and the test report came back clean, but I'm planning on running memtest86+ this evening, as it seems to be widely suggested.

Below is the WinDbg reports from the latest crash (Jan 21):

Quote :

" Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Josh\Desktop\Debugging Software\Errors\Jan 21 2012\012112-14773-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Users\Josh\Desktop\Debugging Software\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03250670 Debug session time: Sat Jan 21 20:18:34.878 2012 (UTC - 5:00) System Uptime: 0 days 2:07:23.034 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : partmgr.sys ( partmgr!PmWmiCounterIoComplete+6c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3833373038303538 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002f8c448 -- (.exr 0xfffff88002f8c448) ExceptionAddress: fffff88000fa3a6c (partmgr!PmWmiCounterIoComplete+0x000000000000006c) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002f8c4f0 -- (.trap 0xfffff88002f8c4f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ff7ffa8007a20d80 rbx=0000000000000000 rcx=0000000000000000 rdx=0000165700000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88000fa3a6c rsp=fffff88002f8c680 rbp=fffffa800a79be98 r8=fffffa800a79beb0 r9=0000000000000004 r10=fffffa800782d620 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc partmgr!PmWmiCounterIoComplete+0x6c: fffff880`00fa3a6c 4a8b0cd8 mov rcx,qword ptr [rax+r11*8] ds:ff7ffa80`07a20d90=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000307f5fe to fffff80003087c10 STACK_TEXT: fffff880`02f8b528 fffff800`0307f5fe : 00000000`0000099c 00000000`00000d90 fffff880`02f8bca0 fffff800`030b3830 : nt!KeBugCheck fffff880`02f8b530 fffff800`030b34fd : fffff800`0329171c fffff800`031cec30 fffff800`0300b000 fffff880`02f8c448 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02f8b560 fffff800`030b22d5 : fffff800`031d20fc fffff880`02f8b5d8 fffff880`02f8c448 fffff800`0300b000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02f8b590 fffff800`030c3361 : fffff880`02f8c448 fffff880`02f8bca0 fffff880`00000000 fffffa80`0a79bc60 : nt!RtlDispatchException+0x415 fffff880`02f8bc70 fffff800`030872c2 : fffff880`02f8c448 fffffa80`07a20ce0 fffff880`02f8c4f0 fffffa80`0a79beb0 : nt!KiDispatchException+0x135 fffff880`02f8c310 fffff800`03085bca : 00000000`00000001 00000000`00000000 fffff880`02f8c590 fffff880`02cfa13f : nt!KiExceptionDispatch+0xc2 fffff880`02f8c4f0 fffff880`00fa3a6c : 00000000`002fe577 fffffa80`07a20ce0 00000000`002fe577 fffffa80`07a21ab0 : nt!KiGeneralProtectionFault+0x10a fffff880`02f8c680 fffff880`00fb6c7f : fffffa80`07a26a90 00000000`00000000 fffffa80`07a26940 fffffa80`0a79bc60 : partmgr!PmWmiCounterIoComplete+0x6c fffff880`02f8c6b0 fffff800`0308b021 : fffffa80`0a79be0b fffffa80`07a26940 fffffa80`0a79bc60 fffffa80`0a79bc60 : volmgr! ?? ::FNODOBFM::`string'+0x2cc fffff880`02f8c6f0 fffff880`01617bce : fffffa80`08c4fe60 fffff880`02c09701 fffffa80`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`02f8c7e0 fffff800`0308b021 : 00000000`00000000 fffffa80`08a297a8 fffffa80`08c4fe02 fffffa80`08a29010 : CLASSPNP!TransferPktComplete+0x1ce fffff880`02f8c860 fffff880`0114c41a : 00000000`00000000 00000000`00000001 fffffa80`070ea460 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`02f8c950 fffff880`0114c242 : fffffa80`070ea460 00000000`00000f00 00000000`00000001 26297f41`00000000 : ataport!IdeCompleteScsiIrp+0x62 fffff880`02f8c980 fffff880`01146e32 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`07312350 : ataport!IdeCommonCrbCompletion+0x5a fffff880`02f8c9b0 fffff880`0114f805 : fffffa80`0782c1a0 fffffa80`070ea460 00000000`00000000 00000000`00000005 : ataport!IdeTranslateCompletedRequest+0x236 fffff880`02f8cae0 fffff880`0114f104 : fffffa80`0782c1a0 00000000`00000000 fffffa80`0782c1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5 fffff880`02f8cc10 fffff800`030930ac : fffff880`02f64180 00000005`9609e693 fffffa80`0782c050 fffffa80`0782c118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`02f8ccd0 fffff800`0307f96a : fffff880`02f64180 fffff880`02f6efc0 00000000`00000000 fffff880`0114ef5c : nt!KiRetireDpcList+0x1bc fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: partmgr!PmWmiCounterIoComplete+6c fffff880`00fa3a6c 4a8b0cd8 mov rcx,qword ptr [rax+r11*8] SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: partmgr!PmWmiCounterIoComplete+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: partmgr IMAGE_NAME: partmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792c0 FAILURE_BUCKET_ID: X64_0x1E_0_partmgr!PmWmiCounterIoComplete+6c BUCKET_ID: X64_0x1E_0_partmgr!PmWmiCounterIoComplete+6c Followup: MachineOwner ---------"

I've had something like 11 crashes through January thus far, and none of which seem to be throwing the same error, so I'm pretty lost at this point. Any help would be greatly appreciated!

[Edited on January 21, 2012 at 11:15 PM. Reason : ]

1/21/2012 11:14:05 PM

I'm pretty lazy when it comes to BSOD's.

Install new hdd, install windows, go from there.

1/21/2012 11:22:03 PM

your hardware seems more than sufficient so unless you have bad hard drive sectors (try a chkdsk /f) i doubt its hardware related

i'd take a look in the registry \run and startup folder and make sure there isnt anything suspicious in there

also cant hurt to make sure you have the latest Windows Update patches, though Win7 is pretty stable

[Edited on January 21, 2012 at 11:31 PM. Reason : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]

1/21/2012 11:28:22 PM

Thanks for the input so far. I'm going to run a chkdsk in a bit and will report back with any results. chkdsk came back clean. As for inspecting the registry - I'm really only familiar with PC's to the degree that I can BS my way through most stuff, and with that said, I'm not sure what I should be looking for within the registry that would be considered suspicious etc.

The only programs I have set to go on startup at the moment are Explorer, a USB program that I believe relates to the mobo (USB 3.0 Monitor by Renesas Electronics Corp.), Trend Micro, and AMD's Catalyst software.

Windows Update shows no new updates other than IE9, which I don't use

Thanks again!

[Edited on January 22, 2012 at 12:56 AM. Reason : Chkdsk was clean]

1/22/2012 12:30:46 AM

make sure your memory is actually running at it's spec'd voltage.

double check the actual voltages/multipliers/clock rates for you mem, video, cpu and northbridge. make sure what the bios reports is actually what is showing up in cpuz/etc.

1/22/2012 12:47:47 AM

^^You should still upgrade to IE9, because some other programs with Web interfaces use the IE engine internally.

1/22/2012 12:56:31 AM

^^ Memory is confirmed at 1.5V according to CPU-Z, as well as correct frequency. Everything else is currently untouched/stock/auto within the bios, and looks correct to my knowledge (CPU/GPU/etc) as I've never really tinkered within the BIOS. I'll be running memtest86+ this evening to doublecheck the RAM, as it's generic nature concerns me, but I didn't have any issues with the regular Windows Diagnostic memory test, so I'm not sure what this will yield.

^Thanks for the advice - just installed the update.

1/22/2012 1:19:48 AM

Also, you should ditch Trend Micro and install Microsoft Security Essentials instead. It is a much better piece of software and doesn't take nearly as many system resources as other antivirus programs.

Don't worry, the NCSU OIT people won't come after you

1/22/2012 6:54:24 AM

Kind of curious more than anything, I see something about Windows 7 OS but an error description saying Vista driver fault?

Some things I would do:
Bad RAM (run memtest several more times or just run without one stick at a time)
Corrupt file (reload time)
Antivirus definitions (get rid of anything except MSE for the timebeing until you figure it out)

1/22/2012 11:31:50 AM

^^ Dumped Trend Micro and installed MSE - thanks for that note.

^ Just finished 10 hours of Memtest86+ overnight, with just short of 6 passes completed and no errors. As for any corrupt files, a friend suggested a registry cleaner, but I've heard mixed reviews on using a registry cleaner, as you can apparently do much more harm in one mistake than good a clean run.

I noticed the Vista Driver Fault line appearing in several of the crash reports - would it help in troubleshooting if I put up some more of the recent dump files? Or even specific lines of them? The latest major hardware change in my computer was a new video card on the 14th, and I was having crashes before then as well as after, with six total BSoD's (including the above one) since then.

1/22/2012 1:05:14 PM

Do you have a spare hard drive?

1/22/2012 2:00:08 PM

^Sort of. I use a 500GB internal drive as my external backup drive through a USB dock, but beyond that, I don't have anything else on hand. What would you suggest doing with a spare hard drive, and could it be done with my backup drive to some extent?

1/22/2012 2:18:39 PM

Quote :

"I don't have anything else on hand. What would you suggest doing with a spare hard drive"

Like I mentioned above, I'd just do a fresh install on a new hdd, then pull your data off the old drive. I'd put $ on the BSOD's going away, given the hardware troubleshooting you've already done...plus you get the added benefit of starting with a clean install.

1/22/2012 5:45:45 PM

A registry cleaner won't fix corrupt files, although it *may* get rid of cruft from the Registry left behind by incompletely-uninstalled programs; I personally don't like anything more aggressive than CCleaner, because indeed a mistaken Registry cleaning will fuck up your system and force you to reinstall Windows.

However, you should try to run a disk-check, possibly by right-clicking the C: drive in My Computer and going to Properties; you should find an option to "Scan Disk..." or something similar, and the scan will run when you reboot.
If that doesn't fix your problem, try to look for corrupt system files by opening Command Prompt as Administrator and typing in the command "sfc /scannow"; you'll need to reboot again after the scan finishes (and I think you should try that after the disk-check, because it helps to square away any bad sectors first).
Now if you do find any bad sectors on the disk with that disk-check, you should seriously consider moving to a new hard drive, and you might be able to do that without needing to re-install Windows; just use a USB-SATA/IDE connector to hook up the new drive externally: http://www.xxclone.com/

1/23/2012 3:26:10 AM

^ It's buried in above posts, but I did run the disk check and it came back totally clean. I'll go ahead and do the scannow command next. Fortunately, I haven't seen any crashes today, so hopefully I'm moving in the right direction.

Speaking of backups: What's the best way to back up a hard drive? i.e. The W7 backup utility that stores a system image vs a copy/paste of C: vs a clone through a program like you linked? I've always backed my stuff up, but when it comes to ever needing to restore it, I'm not sure what backup type would be easiest, while also not being vulnerable to whatever virus/corruption that would be the cause of needing a backup.

1/23/2012 12:44:36 PM