Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD HELP!


  • Please log in to reply
37 replies to this topic

#1 cram03

cram03

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 25 January 2014 - 06:11 PM

HI, I am new here and I have constantly been having problems since December of 2013. I went to countless forums and would love to try my luck in here.

So here's my situation. I built my computer last year and I have been having problems with BSOD since i made a few upgrades. I am trying hard to pinpoint the problem but I cannot find it. My current and former computer specs would be as follow:

Former:
Windows 7 home premium edition
intel i5 2500k 3.00ghz @ 4 cores
ASUS P8Z77-V LX LGA 1155 Intel Z77
ASUS 1gb gtx 650ti
4x2 generic ram 1300mhz
Corsair Enthusiast Series 850w 80 plus bronze

Current:
Windows 7 home premium edition
Intel i5 3570k 3.4ghz @ 4 cores
ASUS P8Z77-V LX LGA 1155 Intel Z77
Gigabyte geforce gtx 760 2gb with windforce
Corsair Vengeance (2x4gb) DDR3 1600mhz
Corsair Enthusiast Series 850w 80 plus bronze

I did a fresh install and updated all my bios and software. Problems started when I installed my new graphic card. Even with the latest drivers, BSOD happens almost every 2 hours. I tried replacing my GPU with a new but same card and BSOD still happens. I tried putting back my generic memory card but did not fix the problem. From the last BSOD report, it stated that there might be some software problems. Can anybody assist me on this? I spent a lot of money to build my PC but I am a newbie as well. Thank you! I also replaced my new CPU but did not solved the problem.

 

Here is my speccy: http://speccy.piriform.com/results/EHYgRuNWiBqHIu1aJjYINQ8

 

and here are some of my mini-dump via whocrashed:

 

On Sat 1/25/2014 7:52:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012514-7597-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009ED180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 1/25/2014 7:52:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009ED180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 

As I said, I have tried doing a fresh install but have not tried wiping clean my whole HDD. I have a new HDD coming in in two days to possibly back up my files before I try using DBAN. I just want to avoid this because my hybrid drive is new as well and I have a lot of important files. any suggestions on what to do? do you think this might have been caused by a hardware problem? If so, I am willing to replace my PSU and motherboard as well. My PSU is not even 6 months old.



BC AdBot (Login to Remove)

 


#2 technonymous

technonymous

  • Members
  • 2,520 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:01 PM

Posted 26 January 2014 - 07:45 PM

Go into bios and to the monitoring section and write down the voltages 12v+ 5v+ 3v+ and battery bios voltage (if it's there) and post your findings. Also check that you're not ovclocking the bus as speccy says your memory is...8.00GB Single-Channel DDR3 @ 816MHz (9-9-9-24) Not sure if speccy is reporting that correctly or not. It's possible that slight Overclock of 16x2mhz is causing issues. Then if you are also OCing the video card too, that combination could be pushing it to much and system hangs. Check that the memory modules are in the right color coded slots, could be a bad slot. Check QVL list of the motherboard some memory module brands just will not work well no matter what.

 

Swaping components out is only way to pinpoint the problem. Like you said PSU or Motherboard is going out. Even though Corsair is a good brand doesn't mean it couldn't be going out. Without properly testing it under load there really is no way to tell. Maybe you can find a friend that you can swap it out for a while to see what happens? I have come across this issue more than once like what you're having. In many cases it was the motherboard that was a lemon. No telling what is wrong on them as they are slammed together with robots that solder the components on the board so it could be anything on the board causing it. The only solution is to buy a new one and rebuild the system after you exhausted all other possibilities and what you can do. Good luck



#3 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 26 January 2014 - 11:05 PM

Hi

 

BSOD 101 CLOCK_WATCHDOG_TIMEOUT is always a CPU related BSOD. According to "Speccy" , your CPU seems to be overclocked.

 

Core 0
Core Speed: 4181.6 MHz
Multiplier: x 41.0
Bus Speed: 102.0 MHz
Temperature: 32 °C
Thread 1
APIC ID: 0
 
Core 1
Core Speed: 4181.6 MHz
Multiplier: x 41.0
Bus Speed: 102.0 MHz
Temperature: 31 °C
Thread 1
APIC ID: 2
 
Core 2
Core Speed: 4181.6 MHz
Multiplier: x 41.0
Bus Speed: 102.0 MHz
Temperature: 40 °C
Thread 1
APIC ID: 4
 
Core 3
Core Speed: 4181.6 MHz
Multiplier: x 41.0
Bus Speed: 102.0 MHz
Temperature: 25 °C
Thread 1
APIC ID: 6
 
Uninstall any overclocking related software from the system first. Then reset system BIOS and load "Optimal default Values". Make sure not to modify neither CPU nor RAM voltage or frequency values and let the BIOS to choose what is best for the system. Probably your issue will be solved.


#4 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 27 January 2014 - 03:22 PM

Thanks for the quick reply guys. For now, I have took out my overclock which I doubt is the problem since it was just a mild OC and it was the second i5-3570k that got delivered to me. The first one works great on my first computer. I just did a fresh install an hour ago and formatted my hard drive then used windows verifier. I cannot pinpoint exactly what it was but whocrashed said it was a driver error which was very unlikely because there are no drivers installed in the first place. I want to know if I purchased the same motherboard, would I still have to repurchase a new windows 7 license key. I am now leaning to a faulty motherboard as I have tried three different CPU's altogether and ended up having the same problem. I am about to try technonymous's advice and will keep you posted. 



#5 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 05 February 2014 - 08:46 PM

It seems that it may eventually be my PSU or MOBO as the problem. I still keep having problems eventhough I replaced my CPU. My question still stands, if I change my mobo to the same one i have, will i need to purchase a new windows?



#6 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 05 February 2014 - 10:51 PM

 

My question still stands, if I change my mobo to the same one i have, will i need to purchase a new windows?

 

 

Usually Windows will remain activated if you swapped the MoBo with another same make and model. If the model changes, you may need to reactivate Windows.



#7 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 06 February 2014 - 12:07 AM

Thank you Anshad. Mobo problems do start blue screen right? I have replaced every single part of my computer except for the motherboard and PSU. it is just frustrating. Any suggestions on my predicament? My minidump has actually changed a bit. 

 

On Thu 2/6/2014 3:54:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-10186-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2/6/2014 3:54:02 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 2/6/2014 1:33:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-9547-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009ED180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  

 

do you think  buying a new motherboard and psu will solve the problem? i have spent more than enough money on my rig.. :(



#8 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 06 February 2014 - 12:23 AM

Hi

 

Before RMAing the MoBO, please try the below steps.

 

1. Make sure to run CPU on default settings. You can overclock after the system became stable and working.

 

2. Update system BIOS.

 

    There is a recent BIOS update available which improves system stability. Download it from http://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8Z77-V_LX/P8Z77-V-LX-ASUS-2303.zip. You can use EZFlash utility to safely update BIOS. Please refer user manual for more info.

 

3. Manually set the timing and voltage of RAM according to manufacturer's specs ( if already not done so). 

 

4. If nothing helps, clean install Widows and test the systems. Install drivers one by one and observe if the BSOD returns after installing a specific driver. This step will clarify whether there is a driver issue in your system.



#9 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 06 February 2014 - 12:56 AM

Thanks Anshad. Unfortunately I have done every step except for number 3, can you please guide me step by step into it? Regarding my overclock, it seems that everytime I reboot, it goes back to the previous overclock values. I have tried everything, even re-setting the CMOS but failed. My last resort would be to go to a technician which I would end up spending another hundred or more. I built a PC under the impression that it would be far cheaper than consoles in the long run but in the past few years alone, have spent a little below $2000. The friend who overclocked my PC is now in seattle and could not help me at all. 



#10 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 06 February 2014 - 02:42 AM

 

 

Regarding my overclock, it seems that everytime I reboot, it goes back to the previous overclock values.

 

It means there is some software is installed in your system which auto overclock your CPU. Please download and run Minitoolbox from the below link.

 

http://www.bleepingcomputer.com/download/minitoolbox/

 

Run the tool and select only "List Installed Programs". Then press the Go button and post the output here.



#11 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 06 February 2014 - 03:01 AM

MiniToolBox by Farbar  Version: 23-01-2014
Ran by Marc (administrator) on 06-02-2014 at 00:00:39
Running from "C:\Users\Marc\Downloads"
Microsoft Windows 7 Home Premium  Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************
 
=========================== Installed Programs ============================
 
Adobe Flash Player 11 Plugin (Version: 11.1.102.55)
AI Suite II (Version: 2.01.01)
Battle Realms WOTW Expansion (Version: 0.20.000)
Battle.net
BitTorrent (Version: 7.8.2.30489)
Borderlands 2
Command & Conquer Generals (Version: 0.50.0000)
Diablo III
Dota 2
GeForce Experience NvStream Client Components (Version: 1.6.28)
Google Chrome (Version: 32.0.1700.107)
Google Update Helper (Version: 1.3.22.3)
Hi-Rez Studios Authenticate and Update Service (Version: 3.0.0.0)
Intel® Management Engine Components (Version: 8.1.0.1252)
Intel® USB 3.0 eXtensible Host Controller Driver (Version: 1.0.5.235)
Intel® Trusted Connect Service Client (Version: 1.24.388.1)
Java 7 Update 51 (Version: 7.0.510)
Java Auto Updater (Version: 2.1.9.8)
League of Legends (Version: 3.0.0)
McAfee Online Backup (Version: 1.16.4.0)
McAfee Total Protection (Version: 12.8.908)
Microsoft .NET Framework 4.5.1 (Version: 4.5.50938)
Microsoft Visual C++ 2005 Redistributable (Version: 8.0.56336)
Microsoft Visual C++ 2005 Redistributable (Version: 8.0.59193)
Microsoft Visual C++ 2005 Redistributable (Version: 8.0.61001)
Microsoft Visual C++ 2005 Redistributable (x64) (Version: 8.0.59192)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 (Version: 10.0.40219)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 (Version: 10.0.40219)
MPC-HC 1.7.2 (64-bit) (Version: 1.7.2)
NVIDIA 3D Vision Controller Driver 332.21 (Version: 332.21)
NVIDIA 3D Vision Driver 332.21 (Version: 332.21)
NVIDIA Control Panel 332.21 (Version: 332.21)
NVIDIA GeForce Experience 1.8.2 (Version: 1.8.2)
NVIDIA Graphics Driver 332.21 (Version: 332.21)
NVIDIA HD Audio Driver 1.3.30.1 (Version: 1.3.30.1)
NVIDIA Install Application (Version: 2.1002.142.992)
NVIDIA LED Visualizer 1.0 (Version: 1.0)
NVIDIA Network Service (Version: 1.0)
NVIDIA PhysX (Version: 9.13.0725)
NVIDIA PhysX System Software 9.13.0725 (Version: 9.13.0725)
NVIDIA ShadowPlay 11.10.11 (Version: 11.10.11)
NVIDIA Stereoscopic 3D Driver (Version: 7.17.13.3221)
NVIDIA Update 11.10.11 (Version: 11.10.11)
NVIDIA Update Core (Version: 11.10.11)
NVIDIA Virtual Audio 1.2.20 (Version: 1.2.20)
Pando Media Booster (Version: 2.6.0.7)
Realtek Ethernet Controller Driver (Version: 7.65.1025.2012)
Realtek Ethernet Diagnostic Utility (Version: 2.0.2.6)
Realtek High Definition Audio Driver (Version: 6.0.1.6767)
Rome - Total War - Gold Edition (Version: 1.6)
RTKXI (Version: 1.00.0000)
SHIELD Streaming (Version: 1.7.306)
Skype™ 6.13 (Version: 6.13.104)
Smite (Version: 0.1.1930.0)
Speccy (Version: 1.24)
StarCraft II
Steam
Total War: SHOGUN 2
WhoCrashed 5.00
WinRAR 4.00 (64-bit) (Version: 4.00.0)
 
**** End of log ****
 
This is what I got, as far as I am concerned, i don't think i have any software that overclocks it outside the bios. It was overclocked last december if I remember correctly.


#12 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 06 February 2014 - 05:32 AM

Hi

 

Please uninstall AI Suite II (Version: 2.01.01) completely from the system. After rebooting, enter BIOS setup and load "Optimized defaults". When you boot in to the desktop, please rerun "Speccy" and post a new snapshot to verify the CPU is running on stock settings. 



#13 cram03

cram03
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 06 February 2014 - 06:00 AM

Here you go. http://speccy.piriform.com/results/aUb2k8Y01NK8l6T1BmS1lfS

 

I am deeply ashamed of the way I handled things with building a computer. It might have been a lot better to have purchased something already built and have it covered with warranty. Although I wouldn't have the same specs, I at least wouldn't have to bother a lot of people to help me with my predicament. :(



#14 technonymous

technonymous

  • Members
  • 2,520 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:01 PM

Posted 06 February 2014 - 07:43 AM

The specs of the cpu is normal 3400Mhz and 3800Mhz Turbo. In the bios settings you need to go to cpu and manually change the bus to 100mhz and multiplier 34x for a 3400Mhz. Could be that the software is turbo clocking it? Before it was set at 102x41=4182Mhz, thats almost 400 over it's spec. A slight cpu voltage bump might stable it at that speed and stop BSOD.
 
Bus Speed: 
103.0 MHz
Stock Core Speed: 
3400 MHz
Stock Bus Speed: 
100 MHz

Edited by technonymous, 06 February 2014 - 07:47 AM.


#15 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:31 AM

Posted 06 February 2014 - 07:53 AM

Hi

 

New Speccy looks fine. You can try changing multiplier, voltage etc later after making sure the system works stable. Until then leave the CPU settings to BIOS defaults. System will automatically manage the CPU frequency in accordance with the load ( When under full load, it will boost up to 3.8 Ghz ).

 

Now play some games and report whether you still gets BSOD. 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users