Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Blue screen is killing me, help

05 Dec 2011   #1
debgram1

Windows 7 Home Premium 64-bit
 
 
Blue screen is killing me, help

My Ram is fine, I got a new hard drive and I'm still getting blue screen. The date is wrong on the dump file below and it really doesn't tell me what driver it is. I thought it was my graphics driver since that was the only new thing I installed so I removed it and installed the older one and still no help.

Here's what the dump file said............. On Tue 12/6/2011 2:38:43 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\120511-22807-01.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EA180, 0x1) Error: CLOCK_WATCHDOG_TIMEOUT Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown

CLOCK_WATCHDOG_TIMEOUT onclusion 1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: unknown If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


My System SpecsSystem Spec
05 Dec 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by debgram1 View Post
My Ram is fine, I got a new hard drive and I'm still getting blue screen. The date is wrong on the dump file below and it really doesn't tell me what driver it is. I thought it was my graphics driver since that was the only new thing I installed so I removed it and installed the older one and still no help.

Here's what the dump file said............. On Tue 12/6/2011 2:38:43 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\120511-22807-01.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EA180, 0x1) Error: CLOCK_WATCHDOG_TIMEOUT Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown

CLOCK_WATCHDOG_TIMEOUT onclusion 1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: unknown If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
Quote:
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
05 Dec 2011   #3
debgram1

Windows 7 Home Premium 64-bit
 
 

okay here's the dump file



Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by debgram1 View Post
My Ram is fine, I got a new hard drive and I'm still getting blue screen. The date is wrong on the dump file below and it really doesn't tell me what driver it is. I thought it was my graphics driver since that was the only new thing I installed so I removed it and installed the older one and still no help.

Here's what the dump file said............. On Tue 12/6/2011 2:38:43 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\120511-22807-01.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EA180, 0x1) Error: CLOCK_WATCHDOG_TIMEOUT Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown

CLOCK_WATCHDOG_TIMEOUT onclusion 1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: unknown If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
Quote:
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
06 Dec 2011   #4
zigzag3143

Win 8 Release candidate 8400
 
 

Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post356791 )
Quote:
What you're looking for will be in one of the following categories:

a) 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...)
Check the drivers
Check the inside of the case (temperature, voltage, dust, etc).
Run Furmark, and Prime95 below.


Quote:
Quote:
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.



I notice your avast which is often at least a contributing cause of BSOD'S of this type. Please remove and replace your Avast with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows
My System SpecsSystem Spec
Reply

 Blue screen is killing me, help




Thread Tools





Similar help and support threads
Thread Forum
Blue Screen crash I play LOL but everytime I see blue screen
I add dump files please help me I format my pc and I install everything new but still my pc give me restart and blue screen
Drivers
Blue Screen Error but no actual blue screen pops up
While using my laptop, usually when trying to open some "windows" application such as task manager, wireless networks, documents, media player, windows updater etc. my laptop freezes or doesn't allow me to click on anything except the minus button on all my windows and the start button. I'll try to...
BSOD Help and Support
Blue Screen out of the Blue, Was working fine for 9+ hours then c...
Well i had my computer on all day since i woke up @ 8 in the morning gaming and what not. It had finally crashed on me while i was playing dirt 2 a couple of mins ago. I had fixed all my previouse blue screen problems by not using any AMD OverDrive Settings for my Radeon HD 4850. My specs...
BSOD Help and Support
Help with blue screen auto reboot, Stop: 0x0000007B error screen
Hello, I have an HP Pavilion g series laptop (running win7) that is in a continuous restarting loop. This happened after the computer auto updated (windows update). I do not know what was updated, but now every time the laptop starts up it seems to be in a continuous rebooting loop after the...
BSOD Help and Support
Screen glitching is killing me!
I have a Dell Studio laptop that was running Vista. I recently upgraded to 7 ultimate but found a problem. My screen is glitching sometimes. Here are some pictures of what's happening.... http://www.flickr.com/photos/10098664@N00/4423023457/ I have looked online for weeks and have not been able...
Graphic Cards
Please Please Help me .. Blue Screen it's Killing me
Hi .. Happy new Year :) I've problem with blue screen .. it's Hard to Fix it i'm Trying .. But I can't Fix .. :( And What Mean : Probably caused by : hardware ( nt!MiReleaseModifiedWriter+1 )
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App