Not sure why it is doing it, but I followed the BSoD posting instructions.
System Specs:
Compal NBLB2
Intel Core i7 740 QM
8 GB 1333 MHz DDR3
Mobility Radeon HD 5650 1 GB GDDR3
Windows 7 Professional x64 SP1 (OEM install)
I compressed the ZIP using 7-ZIP on ultra using 8 threads to minimize the file size. Went from ~30 MB to ~2MB
BSoD Dump, etc:
Attachment 170411
No I do not. Those are the only dumps I have and I'm still getting the same BSoD error code. To be more specific, it seems to be happening when the system is under load. I'm starting to suspect a CPU issue (which if this is the case, I'll just upgrade to an 840 QM or something if possible...)
Newest crash dated 8/15/2011 was blamed on :
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.
Best advice that I've seen about this error (from here: https://www.sevenforums.com/crashes-d...tml#post356791 )
What you're looking for will be in one of the following categories:
So, check the driversa) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests
Then try replacing parts.Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Then look up the versions of your BIOS to see what changes were done.
You don't seem to have connected scsi disks... but you do have a problem with a scsiadapter:
This should show up in your Devices screen with an exclamation mark. If you really don't use scsi, maybe disable as a test would be easiest.Not Available ROOT\SCSIADAPTER\0000 The drivers for this device are not installed.
How long have you been running VM stuff? A longer time and stable?
Quote