BSOD playing Dirt 3

[tracingspirals]

I was playing Dirt 3 online multiplayer when suddenly the system froze with this looping noise after which I got the BSOD. I didn't get to take a picture of the screen but I tried to follow the steps on posting BSOD and I've attached the folder.

If you guys need to know, I built my system last summer. Its:
Windows 7 Home 64bit retail
Asus Maximus IV Gene-Z
Intel i7 2600K
Nvidia 570GTX
G-Skill 2x4gb DDR3 1600mhz

Haven't overclocked it or anything. Its all running pretty stock.

This seems to be the error report of the crash:

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 2 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000000000000002 
 
  - TimeCreated 

   [ SystemTime]  2012-07-07T17:34:46.315613700Z 
 
   EventRecordID 80694 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer Afaque-PC 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  BugcheckCode 257 
  BugcheckParameter1 0x19 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0xfffff88003d17180 
  BugcheckParameter4 0x6 
  SleepInProgress false 
  PowerButtonTimestamp 0

If you guys could check it out and let me know what I need to do to prevent this from taking place in the future.

Thanks!

 

[b666]

you need to download a blue screen viewer you can download hirens that has one in it and a lot of other good little programs in it then you can post the full blue screen

and the viewer will give you the code from the blue screen and then you can Google it as well

 

[writhziden]

BlueScreenView is not as reliable as a thorough analysis with WinDbg. The most useful information it often gives is that Windows is not working right. Hmmm... I think the user would not be here if Windows was working right.

That is not to say that it always misses finding the problem, but in my experience, it finds the actual problem maybe 15-20% of the time. Not exactly the best odds.


It also is not useful when the user is not getting a blue screen crash as in the case of the OP.

Device Concerns:

ArcSec	ROOT\LEGACY_ARCSEC\0000	This device is not present, is not working properly, or does not have all its drivers installed.

The above is your ArcSoft TotalMedia Theatre 5 software. Re-install the software.​

Software Concerns:

You have both Microsoft Security Essentials and Kaspersky Internet Security installed. Please choose between the two; having both can cause conflicts since they access the same resources simultaneously while protecting your system from viruses.

Removal tool for Kaspersky Lab products

http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627​

Recommend removing your ASUS utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.​

Analysis:

The Event ID error you received typically means a hardware problem. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[tracingspirals]

Thanks very much for the response!!

Device Concerns:
The Arcsoft TotalMedia software was just a demo I downloaded. Never really used it. I guess I'll just uninstall it.

Software Concerns:
Which one would you recommend me deleting? I got the Kaspersky free with the motherboard. I guess I'll probably remove that one.

Analysis:
My system is running completely stock. Apart from the factory overclock on the GPU but I guess that can be considered stock too.
Don't have SSDs, I'll run the tests for the HDDs.

My system has quite good cooling. I've run Prime 95 for a couple of hours and other benchmark tests such as 3D Mark 11 on it a few times and never had any problems. The max CPU temperature I'ld get is around 51C. GPU doesn't go above 65C either as its got a pretty large heatsink and cooler. But I'll run those tests you mentioned and see how well the system does.



I built the PC myself so I have warranty on the individual components but not on the PC as a whole.

Thanks for the reply. I'll do those tests you mentioned and get back to you with the results or if I get any errors.

 

[tracingspirals]

Ran FurMark today for 30mins first at 720p max temp 65C.

Then did a 15min 1080p benchmark.
Scores are: BURN-IN SCORE: 2819 points, 27802 frames, 30 FPS, 66°C,
Resolution: 1920x1080 (FS) - AA:0 samples, FPS: min:31, max:32, avg:30 - OPTIONS: DynBkg,

Didn't see any artefacts or anything as such. I guess its safe to assume my GPU is pretty stable...

I'll run Prime 95 later tonight and probably leave it running overnight and see what results I'll get.

 

[writhziden]

Software Concerns:
Which one would you recommend me deleting? I got the Kaspersky free with the motherboard. I guess I'll probably remove that one.

Analysis:
My system has quite good cooling. I've run Prime 95 for a couple of hours and other benchmark tests such as 3D Mark 11 on it a few times and never had any problems. The max CPU temperature I'ld get is around 51C. GPU doesn't go above 65C either as its got a pretty large heatsink and cooler. But I'll run those tests you mentioned and see how well the system does.

Ran FurMark today for 30mins first at 720p max temp 65C.

Then did a 15min 1080p benchmark.
Scores are: BURN-IN SCORE: 2819 points, 27802 frames, 30 FPS, 66°C,
Resolution: 1920x1080 (FS) - AA:0 samples, FPS: min:31, max:32, avg:30 - OPTIONS: DynBkg,

Didn't see any artefacts or anything as such. I guess its safe to assume my GPU is pretty stable...

I'll run Prime 95 later tonight and probably leave it running overnight and see what results I'll get.

Microsoft Security Essentials (MSE) was designed by Microsoft and therefore has the least problems with Microsoft Windows. It also has the smaller footprint (uses less resources) compared with Kaspersky. I would recommend MSE to guarantee you have the fewest problems/conflicts. Make sure to use the Kaspersky removal tool to remove Kaspersky.

Temperatures all look good. FurMark sounds like it went off without a hitch. Nice work so far. Any problems to report to this point?

 

[tracingspirals]

Thanks for the replies. I removed Kaspersky from my PC.

I ran Prime 95 for around 9hrs and 22mins last night with 0 errors and warnings. CPU temp went max to 60C and stayed around 50-55C for most of the time.

But the motherboard SYSTIN and CPUTIN went upto 123C and 127C and are still around there. Also got a warning saying motherboard temperature is too high and I stopped Prime 95. I used CPUIDs HWmonitor to check the motherboard temperatures. I don't know if this is normal... My case has really good airflow. The side panel is an open mesh so air can freely get in, the CPU is water cooled, there are two 120mm fans on the top and one 80mm fan at the rear exhausting the hot air.

I've attached a screenshot of the hardware monitor after I stopped Prime 95.


Also here's a pic of what my system looks like to give you an idea of the airflow:

Thanks.

 

[writhziden]

It may be a bad sensor reading. Does the motherboard actually feel that hot to the touch?

Make sure when you touch the motherboard to avoid static damage to the PC. Also make sure not to burn yourself by touching it very quickly or using something as an insulator. You do not want to burn yourself in the process.

 

[tracingspirals]

Thanks for the prompt replies.

I touched the bits of the motherboard I could (which weren't behind the graphics card and other components) and it was all fairly cool. I don't know if there's a certain point which is particularly hot on the motherboard.

Although after restarting the computer, the motherboard temperatures have gone down to normal level. So I don't know if its a faulty sensor or the temperatures are genuinely getting that hot.

 

[tracingspirals]

Ok I ran the Seatools for HDD scan and both my HDDs passed all the tests (except the advanced ones which I didn't test).

Also I ran the "WhoCrashed" software and this is what it came up with:

On Sat 07/07/2012 17:33:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003D17180, 0x6)
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

Conclusion

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 it can be of any help to you in figuring out what might have caused the crash?

Thanks!

 

[writhziden]

For the 0x101 crash, one of our experts compiled: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Can you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the reports?

 

[tracingspirals]

Hi, yeah, I followed the BSOD posting instructions and attached the reports in my first post in this thread.

I read the 0x101 crash. What I got is it could be something wrong with the BIOS or a driver or could be something like high temperature. I updated the BIOS to the latest one. I can't say much about the driver but I updated the intel ethernet driver and did a clean reinstall for the graphics driver. I don't think I can do much about temperature but I'm planning on fitting another fan to my case which should improve the airflow and cooling. Still what I read in other forums is its very rare to get a 0x101 crash for a stock system which hasn't been overclocked.


Anyway, I played Dirt 3 again yesterday for about 2hrs. This time I pulled back the graphics a bit. Before I was running it at max graphics when the crash happened. This time I was able to play it with no crashes or any issues. I was monitoring the temperature with HWmonitor too and any of the temps didn't go upto any dangerous levels either. So I don't know if everything is fine now...

 

[writhziden]

BSOD Posting Instructions:

You did attach the reports in your first post, but you have had new crashes since then. We need the up to date reports.​

Temperature Monitoring:

Use the following programs to monitor the temperatures.​

• Real Temp is a good CPU temperature monitor.
• Speccy - System Information - Free Download will monitor all hardware temperatures.
• HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

 

[tracingspirals]

Hi, no I haven't had any new crashes since then. That was the only crash I had.

 

[writhziden]

Alright, it may have been a one time occurrence. Report back if you have any more crashes.