A few of these point towards
ntkrnlmp.exe which is highly unlikely as a cause because it's a system file. It's usually disguised as the cause because it gets sent in after processing the possible bad data that causes the BSOD but is not really the initial cause that created the crash.
One of the crash dumps was intriguing to me, since some of them are different. I believe this is the cause for your BSOD:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wmpnetwk.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0aa0c158 fffff800`02ed78c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff880`0aa0c160 fffff800`02e8a497 : fffff8a0`00000000 fffff800`00000002 00000000`00026160 fffffa80`04ea3000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0aa0c1f0 fffff800`033f6895 : fffff800`0341c3c0 fffff880`0aa0c3a0 fffff800`0341c3c0 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0aa0c2f0 fffff800`02e7c173 : fffff8a0`0a388940 00000000`00000040 fffff880`0aa0c3a8 00000000`000007ff : hal!HalpHpetClockInterrupt+0x8d
fffff880`0aa0c320 fffff800`02e82a09 : fffff880`0aa0c680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0aa0c4b0 fffff800`02e824da : fffff880`0aa0c848 fffff880`0aa0ca50 fffff8a0`020230e0 fffff880`0aa0c960 : nt!SwapContext_PatchXRstor+0x127
fffff880`0aa0c4f0 fffff800`02e41f20 : fffffa80`06ac9700 fffffa80`06ac9700 00000000`0000020e 00000000`000007ff : nt!KiSwapContext+0x7a
fffff880`0aa0c630 fffff800`02e82592 : 00000000`00000008 fffff800`02ff5e80 fffff880`0aa0c730 fffff880`0aa0c730 : nt!KiQuantumEnd+0x1b4
fffff880`0aa0c670 fffff800`02ecb993 : fffff800`02e7c1a0 fffff800`02e7c20c 00000000`000000dc fffff8a0`052182e0 : nt!KiDispatchInterruptContinue+0x16
fffff880`0aa0c6a0 fffff800`02e7c20c : 00000000`000000dc fffff8a0`052182e0 fffff880`624e4d43 fffff880`0aa0c848 : nt!KiDpcInterruptBypass+0x13
fffff880`0aa0c6b0 fffff800`02faefe4 : 00000000`00000001 fffff8a0`0a388910 fffff8a0`022445c0 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
fffff880`0aa0c840 fffff800`03228026 : fffff8a0`022445c0 fffff800`03131b00 00000000`69634d43 00000000`000004ef : nt!ExFreePoolWithTag+0x254
fffff880`0aa0c8f0 fffff800`031b425a : fffff880`00000010 fffff880`0aa0c9f0 00000000`00000000 fffff8a0`00000010 : nt!CmpCallCallBacks+0x4f6
fffff880`0aa0c9c0 fffff800`031321bb : 00000000`00000000 fffff880`0aa0cc60 00000000`00000004 fffff8a0`052182e0 : nt! ?? ::NNGAKEGL::`string'+0x1232b
fffff880`0aa0ca40 fffff800`02e7eed3 : 00000000`00000558 00000000`00000001 fffffa80`00000000 fffff800`00000004 : nt!NtSetValueKey+0x36e
fffff880`0aa0cb70 00000000`775b191a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01acdbd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b191a
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Error: 0x101
Cause: This would indicate to me that an expected clock interrupt on a secondary processor, was not received within the allocated interval, causing a timeout stop error. You have multiple processors which is good, but one of your secondary processors is giving you grief. This secondary processor is not processing interrupts, which typically occurs when the processor is nonresponsive or is deadlocked.
I know this can happen with applications that don't handle their threads in each process properly, which is a huge concern for multi-threading any application. From my programming experience I know that it's pretty difficult to debug a cause once the application has been run for debugging.
I would suggest running Memtestx86 and Driver Verifier, to test a few things out before myself or another BSOD analyzer makes any further suggestions for you.
It's good to do a checkup anyway in case something is corrupt on your system.
Memtestx86 is available here:
http://www.memtest86.com/
Run it on boot, booting it from a CD from the boot menu when you start up your computer. Let it pass for at least 6 tests. As usual, if any of the tests don't pass it means something is corrupted in your memory.
Driver Verifier: :Note make sure you backup your data first
If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.
A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start > All Programs > Maintenance > "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu
Follow these steps:
- Go to Start and type in "verifier.exe" and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the BSOD. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 48 hours (recommended) of continuous operation to make sure.
If you can't get into Windows because it crashes too soon, try it in Safe Mode (recommended) or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.
