Tech Support banner

Status
Not open for further replies.
1 - 20 of 77 Posts

·
Registered
Joined
·
91 Posts
Discussion Starter #1
Hello people, i just registered in hope for some fixes. This problem appared to me 2 weeks ago. Where my BSOD's were quite often no matter what i did.

However these other days in the week, they've been happening every 2 - 3 days. But that has also dissapeared. Now i BSOD really often, when ever the computer feels like it.

This started happening as i said 2 weeks ago when i changed my Motherboard and Processor. Because my old one was a AMD 5200+ Dualcore on a M2N-E Asus AM2

They both died at the same time. So i got myself a ASRock N68-S UCC.

But do note that the first four to five days this didnt happen. Everything was fine after changing my hardware. So .. Ive read my minidumps with "whocrashed" and it indicates it is most likely a driver/software problem and NOT hardware.

Yes indeed this is a wall of text, but as a gamer i cannot proceed to enjoy my hobby with a BSOD constantly popping up. Ill post my specs below and all that


CPU: AMD Athlon 64 X2 Dual Core 6000+ 3.1 Ghz
GPU/Video Card: Nvidia 9600 GT
RAM: 4 Gigabyte
Motherboard: ASRock N68-S UCC

My usual temperatures for the CPU are about 35C at idle and 40C - 50C Ingame. Same goes with GPU and just about everything else.

I am running on the latest drivers for all of my components, ive tried rolling back to see if the BSOD's dissapear but nope .. So im guessing it's not those

I zipped the Minidump. Thank you for your help, if you need more info please do ask. I want to fix this asap.
 

Attachments

·
Registered
Joined
·
91 Posts
Discussion Starter #2
Here is more info on my computer, i didnt read the "read before posting" sticky until now. My fault!


>What was Original OS installed on your system?
Answer: Windows Vista 64bit Ultimate

>Age of System (Hardware)
Answer: My only old hardware is my 9600, which is from 2007. But i take care of it ..

>Age of OS installation - Have you reinstalled the OS?
Answer: When i changed my hardware i installed Windows 7, pretty much a clean install.

>Power supply - Brand and Wattage
Answer: Could not identify brand, however im running a 600W PSU
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

NOTE: Please provide the following information for a more detailed response: http://www.techsupportforum.com/forums/f299/blue-screen-of-death-bsod-posting-instructions-windows-7-and-vista-452654.html

The lone dump file that you uploaded doesn't provide any significant info for us to work with. Please provide the info requested above AFTER following the procedure that I list below:
Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\103111-30218-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Oct 31 16:19:53.109 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:42.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 

·
Registered
Joined
·
91 Posts
Discussion Starter #4 (Edited)
I've followed those instructions and they are pretty confusing. Atleast some of them ..

I cant install Service Pack for my Windows 7, i actually don't know why myself. Ive tried installing it via Auto-Update but when it's supposed to restart and configure the update. It doesn't.

It just says " Configuration failed " or whatever.

I've attached a new RAR file. With one more dump of a couple of days before.
A health report

And finaly i copied info about the BSOD from "whocrashed" quite a good program actually ..

If this doesnt help please tell me and ill try to give more info. There isnt much info i can give though. This is almost all of it.
 

Attachments

·
Registered
Joined
·
91 Posts
Discussion Starter #6
Quick update on the problem.

I haven't had a BSOD since i posted in the thread, Which is kinda weird

I ran Driver Verifier and followed the instructions. It ran 5 hours and 43 Minutes to be exact.

No problems where found, so i disabled it and rebooted. I even played video games while doing it but nope. It didnt find anything
 

·
Registered
Joined
·
91 Posts
Discussion Starter #7
Guys do i have to underclock my processor to fix this? By going around a hundreed and hundreed places on Google. It all indicates that its mostly because of overclocking.

I havent overclocked my processor but do i need to underclock it? Would it fix the problem?
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
Run Driver Verifier for 36 hours of normal use.

If you wish to underclock your processor, it won't hurt. But I'm not convinced that that will fix it either.

IMO, the inability to install Service Pack 1 is the biggest problem right now. There are 2 primary reasons that a Service Pack won't install - incompatible drivers and/or malware.

So, visit the manufacturer's website and update ALL of your drivers. Your chipset drivers date from 2008 - for starters And your storage drivers (which date from 2009) may also be implicated in the crashes.

Scan for malware to see if you're infected (If so, post over in the Security Center for assitance in cleaning it up). IF both of those fail, then contact Microsoft Support - they offer free technical support for Windows Update issues.


OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:
Code:
[font=lucida console]
nvstor.sys      Fri Mar 19 16:45:11 2010 (4BA3E257)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)
RzSynapse.sys   Wed Dec 15 05:32:19 2010 (4D089933)
dump_nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor.sys      Wed May 20 02:45:37 2009 (4A13A711)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
dump_nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
nvlddmkm.sys    Thu May 14 16:48:07 2009 (4A0C8387)
[/font]





http://www.carrona.org/dvrref.html#nvstor.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#nvm62x64.sys
http://www.carrona.org/dvrref.html#RzSynapse.sys
http://www.carrona.org/dvrref.html#dump_nvstor.sys
http://www.carrona.org/dvrref.html#nvstor.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#dump_nvstor.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys

BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\110111-21578-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Nov  1 02:03:37.093 2011 (UTC - 4:00)
System Uptime: 0 days 1:00:36.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\110111-32140-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Nov  1 01:02:12.109 2011 (UTC - 4:00)
System Uptime: 0 days 8:41:12.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\103111-30218-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Oct 31 16:19:53.109 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:42.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\103111-26750-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Oct 31 04:49:17.251 2011 (UTC - 4:00)
System Uptime: 0 days 9:38:06.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\103111-24359-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Oct 30 19:10:20.108 2011 (UTC - 4:00)
System Uptime: 0 days 5:08:48.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102811-24328-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Oct 28 06:31:18.109 2011 (UTC - 4:00)
System Uptime: 0 days 1:33:36.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102411-23015-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Oct 24 05:57:47.376 2011 (UTC - 4:00)
System Uptime: 0 days 6:43:42.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102311-26968-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Oct 22 18:28:31.109 2011 (UTC - 4:00)
System Uptime: 0 days 8:40:24.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\102011-28562-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Oct 20 15:39:28.093 2011 (UTC - 4:00)
System Uptime: 0 days 9:23:30.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000060 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101311-34515-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 13 15:43:20.723 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:42.676
BugCheck D1, {a, 2, 0, fffff8800103efa5}
Probably caused by : storport.sys ( storport! ?? ::FNODOBFM::`string'+b55 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_storport!_??_::FNODOBFM::_string_+b55
Bugcheck code 000000D1
Arguments 00000000`0000000a 00000000`00000002 00000000`00000000 fffff880`0103efa5
BiosVersion = P1.50
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 

·
Registered
Joined
·
91 Posts
Discussion Starter #9 (Edited)
I know that i do not have malware, im always sure about that. I've never been a idiot enough to actualy get any kind of infection for my computer.

And speaking about malware, i scanned my computer with Avast and it did not detect anything. I took this thread up on another forum. Or better known as the Windows Seven Forum. The guy thinks its a hardware problem.

But i don't think its the hardware.

"Your chipset drivers date from 2008 - for starters And your storage drivers (which date from 2009) may also be implicated in the crashes."

You list that? Im almost ashamed to say it but, i really do not know how to do that. As much as i know how to update my GPU, CPU drivers and all that. I dont know how to update my chipster drivers nor do i even KNOW PROPERLY what the storage drivers are.

I am wondering where you got the info for the old drivers, as this motherboard isnt from 2008. Its 2 and a half weeks old. Thats as far as i know, and it already comes with almost the latest updates for both the BIOS and the chipset.

Now about the old drivers. I dont even know what each one of them is for at all.

RzSynapse.sys is the only one i recognize, and its the LATEST driver for the Razer Naga. So why did you list it there? Other then that.

If i knew what the drivers were for specificly id actualy update/remove them. But the info on the site you linked is very VERY limited.

This entire process is starting to confuse me. But i try my best.

Besides, driver verifier. I will turn it on once i take a nap.

I almost forgot to say. Thanks for the help ofcourse! Atleast we're advancing.
 

·
Registered
Joined
·
91 Posts
Discussion Starter #11
I am just quiclky going to say this as i think its the most easy way to solve the problem.

I am guessing there is a bad core or a defective CPU problem, now i usualy wouldnt belive its a hardware problem.

But after running so many tests with drivers, stressing and all that. None indicate software nor thermal issues.

Instead of buying that Playstation 3 i was gonna get i might aswell get a CPU.

So do you guys, Jonathan/Usama have any ideas for a nice AM2+/AM3/AM2 CPU that has good performance for a fair price?
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
When you buy a motherboard, it's usually been sitting on the shelf in a warehouse for a long time before it gets shipped out to you. As such, the CD/DVD that comes with it is already outdated. So, it's advisable to download and install drivers from the mobo manufacturer's website rather than using the CD/DVD that came with the system.

As for checking the drivers, I use the Windows Debugging Tools to give me the date/time stamps on the drivers. But you can easily double check most of them by lookin at the date/timestamps in the C:\Windows\System32\drivers folder.

While a hardware problem (either the mobo or the CPU) is a possibility - without having updated drivers and all Windows Updates (to include Service Pack 1) - you just can't tell what the problem is. There are many, many fixes published by Microsoft. You can view the most current BSOD fixes at my website here: BSOD Index

And, just to confuse things further - missing Windows Updates, outdated low-level drivers, incompatible drivers, and malware can all mimic hardware problems.

My son's have the Asus M4 series of boards and they seem to work well for them. It's inexpensive, but they're able to play most games without issues.

Your system, your wallet, your call on what to replace.
Good Luck!
 

·
Registered
Joined
·
2,210 Posts
If you wish to resort to swapping hardware, you're entitled to do so and we can't stop ya. However if it is in fact a driver related problem, then in most cases it would not resolve the issue.

The crashdumps all report a CLOCK_WATCHDOG_TIMEOUT during a C1 Halt on your CPU, which shouldn't typically occur during normal CPU activity. I'm not sure why C1 halt is triggering or what's tripping over it, but that seems to be the case. Note that as a workaround, you can disable C1/C1E state in your BIOS, as it's designed only as a power saving option. Note that with this disabled your PC probably isn't gonna like you trying to put it to sleep, hibernate, or any other power state other than off or on.

Unfortunately for these kind of crashdumps a kernel dump is required. Minidumps only save info on the state of a currently running thread and the processor/core that it's running on, nothing else. Normally what happens with these scenarios is that one core is unaware of what the other one is doing, and ends up doing something the thread running on the other core doesn't like, and things go haywire. Without information on what was taking place on all processor cores at the time, we have no way of discerning what could cause this.

If you are interested, you should have the latest kernel dump present as MEMORY.DMP in your Windows directory. Be advised that even compressed it's gonna be a couple 100 MBs so you'll need to use a filesharing site to upload it too. Also, you may wanna verify that the dump file is in fact intact and is not corrupted or incomplete. I'm not sure the WhoCrashed or BlueScreenView may be able to give you an idea if it's corrupt or not, only way I know personally to be sure is to use Dumpchk.exe and have it validate the crash dump. If you are willing to go this way, I can provide you a link to how to get it.

UPDATE:

I decided to dabble into the minidumps further, and would like to ask a couple questions:

1. Do you use any virtual devices?

2. Are you using any VM (virtual machine) software?
 

·
Registered
Joined
·
91 Posts
Discussion Starter #14
If you wish to resort to swapping hardware, you're entitled to do so and we can't stop ya. However if it is in fact a driver related problem, then in most cases it would not resolve the issue.

The crashdumps all report a CLOCK_WATCHDOG_TIMEOUT during a C1 Halt on your CPU, which shouldn't typically occur during normal CPU activity. I'm not sure why C1 halt is triggering or what's tripping over it, but that seems to be the case. Note that as a workaround, you can disable C1/C1E state in your BIOS, as it's designed only as a power saving option. Note that with this disabled your PC probably isn't gonna like you trying to put it to sleep, hibernate, or any other power state other than off or on.

Unfortunately for these kind of crashdumps a kernel dump is required. Minidumps only save info on the state of a currently running thread and the processor/core that it's running on, nothing else. Normally what happens with these scenarios is that one core is unaware of what the other one is doing, and ends up doing something the thread running on the other core doesn't like, and things go haywire. Without information on what was taking place on all processor cores at the time, we have no way of discerning what could cause this.

If you are interested, you should have the latest kernel dump present as MEMORY.DMP in your Windows directory. Be advised that even compressed it's gonna be a couple 100 MBs so you'll need to use a filesharing site to upload it too. Also, you may wanna verify that the dump file is in fact intact and is not corrupted or incomplete. I'm not sure the WhoCrashed or BlueScreenView may be able to give you an idea if it's corrupt or not, only way I know personally to be sure is to use Dumpchk.exe and have it validate the crash dump. If you are willing to go this way, I can provide you a link to how to get it.

UPDATE:

I decided to dabble into the minidumps further, and would like to ask a couple questions:

1. Do you use any virtual devices?

2. Are you using any VM (virtual machine) software?
Oh nice, quite some info in your post. Much appriciated.

You've encouraged me to try and fix the problem before lastly replacing my hardware. Thanks for that i guess.

Now to answer your questions.

I do not use a VM/Virtual machine, nor any kind of devices. Never have really.


"Note that as a workaround, you can disable C1/C1E state in your BIOS, as it's designed only as a power saving option. Note that with this disabled your PC probably isn't gonna like you trying to put it to sleep, hibernate, or any other power state other than off or on."

Does that mean that, if disabling/enabling that thing in the BIOS would mean that my Computer will have to be on or off. Never in sleep mode or such cause otherwise it wont like it?

If so i have no problems with that.

I almost forgot .. I compressed & uploaded the file on megaupload. Had to compress because the file was almost 400MB.

Anyways here is the link: MEGAUPLOAD - The leading online storage and file delivery service

Thanks for the help!
 

·
Registered
Joined
·
2,210 Posts
That's interesting. To my knowledge when perusing the crashdumps the Hyper-V (Hypervisor) debugger was called before the problem was sent to KeBugCheck, which is the function designed to start the crashing process. Hypervisor is for virtual machine stuff, like the Windows XP mode for Win7 Pro/Ultimate. I guess because you're using Pro/Ultimate it's just automatically present. I figured it's worth asking about.

I'll peruse some more regarding this. Thanks for the kernel dump. I probably won't be able to get to it today, but I should as soon as possible. Kernel dumps seldom come here at TSF, and when they do I drool at the opportunity to break em open and see what's inside. Let's just hope it didn't end up being corrupt.

And yes, hibernate, sleep, etc. are all probably no-nos. C states for the CPU are different than the S states that govern the types of sleep the system may be in, but the S states may rely on the C states (not sure). As a result, Windows might simply disable the options or Windows would crash when attempting to do such. But the C states are designed simply for power-saving options for the CPU and are therefore optional.
 

·
Registered
Joined
·
91 Posts
Discussion Starter #16
That's interesting. To my knowledge when perusing the crashdumps the Hyper-V (Hypervisor) debugger was called before the problem was sent to KeBugCheck, which is the function designed to start the crashing process. Hypervisor is for virtual machine stuff, like the Windows XP mode for Win7 Pro/Ultimate. I guess because you're using Pro/Ultimate it's just automatically present. I figured it's worth asking about.

I'll peruse some more regarding this. Thanks for the kernel dump. I probably won't be able to get to it today, but I should as soon as possible. Kernel dumps seldom come here at TSF, and when they do I drool at the opportunity to break em open and see what's inside. Let's just hope it didn't end up being corrupt.

And yes, hibernate, sleep, etc. are all probably no-nos. C states for the CPU are different than the S states that govern the types of sleep the system may be in, but the S states may rely on the C states (not sure). As a result, Windows might simply disable the options or Windows would crash when attempting to do such. But the C states are designed simply for power-saving options for the CPU and are therefore optional.
Thanks for more info again.

Well, take your time. Im here, so no need to hurry. Im guessing you guys are busy after all as im not really the only user asking for help on the forum or such.

Either way, im not gonna disable the C state nor touch it for now. I'll wait for further answers from you. About the Kernel dump that is.

I doubt it corrupt though, Whenever i BSOD the counter reaches 100% in the lower left corner. And im guessing that's the progress of the dump, so if it quits before 100% its corrupt.

Either way. I'll be patient for further help, hopefully i wont have to buy new hardware. Although that wont be such a problem anyways.

Thanks for the help, this progress is quite interesting. Might learn something in the future.
 

·
Registered
Joined
·
91 Posts
Discussion Starter #20
When you changed the motherboard and CPU did you reinstall Windows?
When i replaced my hardware, yes i installed a clean copy of Windows 7. Before that i ran on a 64 Bit Vista Ultimate.

I'm mainly waiting for these guys (above) to look through my kernel dump. I know they're busy though.

I haven't had as frequent BSOD's though, which im happy about. Usualy it'd get them during gameplay. But i dont anymore.
 
1 - 20 of 77 Posts
Status
Not open for further replies.
Top