Solved BSOD and freezes while playing game, error 0x00000101

[snafu22]

Hello,

I had random BSOD's all with 0x00000101 error code everytime I'm playing a game (usually after 5-30 mins of play) (I mostly play Alliance of Valiant Arms, FPS game, unreal engine, directx), which is not a memory hungry game and successfully played it for almost 1 year on my other system (Alienware m15x laptop) without any issue.

System Spec (no overclocking done whatsoever):

Intel Core i5-2500k 3.3Ghz
Asus P8P67-M Pro
MSI NGTX 560 Ti - Hawk 1024Mb (factory overclocked)
Patriot Viper Extreme 2x4Gb
WDC Caviar Blue 500Gb
Seasonic 620w
Windows 7 Ultimate x64

My friend had an EXACT same system and he however did not have this issue. I had this issue after I installed the latest WHQL nvidia driver (which is 301.10). I tried to roll back to previous driver version (270.61, 275.33, 280.26, 290.53) but all of them had BSOD's. I noticed that the 290.53 driver is the most compatible because all of other drivers gave me TDR's while browsing and even while idling but the 290.53 still gave me BSOD while gaming and have the same bugcode just like the other versions.

I will consider to reformat but only if there's no real solution available.

Hope I'll find the solution here, any response to this matter will be much appreciated.

Thanks before.

 

[snafu22]

Sorry for the double post, I forgot to add the attachment.

EDIT: Had another BSOD half an hour ago. Same BugCode. Report from bluescreenview attached (report.rar)

 

[snafu22]

bump?

 

[snafu22]

lol. i see other threads being replied. why you guys wont reply to mine?????

 

[snafu22]

BUMP

Just rolled back to 260.67 driver from the CD that came with the card.
Had TDR just now. No sign of BSOD yet.

 

[snafu22]

LOL. still no response?

 

[writhziden]

Take a look at http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html and let us know if you still need help.

Also, I recommend: http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html since you continue to violate 2)

The more you respond to your own thread, the less likely you are to get help. It will either deter those who would normally have helped, or the number of replies will make it appear that someone has already responded to your thread making it seem unlikely that you need help.


Problematic software:

RTCore64	fffff880`07e00000	fffff880`07e06000	Wed May 25 00:39:12 2005 (42941d90)	00004158		RTCore64.sys

RTCore64.sys: RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7)

 

[snafu22]

Take a look at http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html and let us know if you still need help.

Also, I recommend: http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html since you continue to violate 2)

The more you respond to your own thread, the less likely you are to get help. It will either deter those who would normally have helped, or the number of replies will make it appear that someone has already responded to your thread making it seem unlikely that you need help.


Problematic software:

RTCore64    fffff880`07e00000    fffff880`07e06000    Wed May 25 00:39:12 2005 (42941d90)    00004158        RTCore64.sys

RTCore64.sys: RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7)

Sry about the multipost because i was really frustrated.
Done a clean windows 7 home premium x64 just today, installed drivers from mobo DVD, etc etc. Still had BSOD while gaming. Attached another file because had different BSOD (according to bluescreenview: caused by raspptp.sys ndproxy.sys, wmiacpi.sys, 2x ntoskrnl.exe) so a total of 5 BSOD since OS reinstall, but still with bugcode stop 0x101.

I have MSI afterburner, but the error occured even before I installed it. I will uninstall later.

Haven't done any of the tests mentioned, but will do later on because I have work to do.

Things I have done:
- Os reinstall
- Cleaned hardware from dust etc
- Moved RAM to different slots
- Rolled back and update display drivers

Thank you for your response.
Again, sorry for the multipost.

 

[writhziden]

Problem Devices:

High Definition Audio Controller	PCI\VEN_10DE&DEV_0E0C&SUBSYS_26011462&REV_A1\4&80E7924&0&0108	This device is disabled.

This was probably intentional and is not likely to cause problems.


Security Software: ??? Recommend either of these two options:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

Run a full scan with your new security software as soon as it has been updated.


You are correct that these were 0X101 crashes, but none of the drivers you indicated were blamed. BlueScreenVieiw often blames Windows system files for crashes, which is why we use WinDbg to analyze crashes instead of BlueScreenView. Do some hardware tests.

• If you are overclocking any hardware, please stop.
  
  
• 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 a 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).
  
  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.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[snafu22]

Problem Devices:

High Definition Audio Controller    PCI\VEN_10DE&DEV_0E0C&SUBSYS_26011462&REV_A1\4&80E7924&0&0108    This device is disabled.

This was probably intentional and is not likely to cause problems.


Security Software: ??? Recommend either of these two options:

• Microsoft Security Essentials - Free Antivirus for Windows
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

Run a full scan with your new security software as soon as it has been updated.


You are correct that these were 0X101 crashes, but none of the drivers you indicated were blamed. BlueScreenVieiw often blames Windows system files for crashes, which is why we use WinDbg to analyze crashes instead of BlueScreenView. Do some hardware tests.

• If you are overclocking any hardware, please stop.
• 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 a 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).
  
  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.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Hey, thanks again for the response.

My pc is only 4 days old and i'm quite sure there's no virus or malware lurking around, because i transferred my data using a brand new USB and external HD, and of course i reformatted this morning so i'm pretty sure there's no virus but I will install MSE.

I will do the tests now, and i'll update you with the results ASAP.

Thanks

EDIT: just installed speccy, and whoa it shows around 80-90c for the motherboard temp... is that normal?

 

[writhziden]

That appears to be a sensor malfunction. I would be very surprised if that were the actual temperature with your CPU being as low as it is. You could open the system up and see if the board feels that hot to you. It could be a bad NB fan or the NB heat is not being properly dissipated. If you have an NB fan, check that it is working properly and installed properly. Make sure you Avoid Static Damage to Your PC while checking the temperatures by hand and/or checking the NB fan, and be careful not to burn yourself or shock yourself. You should try to check temperatures when the system is off, unplugged, and has had the power drained by closing the circuit for 30 seconds through holding down the power button with all power sources removed (AC adapter, batteries, etc.).

 

[snafu22]

That appears to be a sensor malfunction. I would be very surprised if that were the actual temperature with your CPU being as low as it is. You could open the system up and see if the board feels that hot to you. It could be a bad NB fan or the NB heat is not being properly dissipated. If you have an NB fan, check that it is working properly and installed properly. Make sure you Avoid Static Damage to Your PC while checking the temperatures by hand and/or checking the NB fan, and be careful not to burn yourself or shock yourself. You should try to check temperatures when the system is off, unplugged, and has had the power drained by closing the circuit for 30 seconds through holding down the power button with all power sources removed (AC adapter, batteries, etc.).

The temps of that screenshot was before I start the stress test, but I haven't reach any of the hardware max temp while running the tests.

- Ran FurMark for 15 minutes, GPU temp stable between 73-76c
- Ran VMT, no errors after 12 passes
- Ran MemTest for 6 hours straight, 5 passes, no error

Also, I can't boot into normal windows because startup repair showed up after memtest (IDK what happened or what's the error because I was AFK), but after I removed the memtest boot USB somehow i can log into windows. Wonder what was the cause...]

Had another BSOD just now after playing 15 minutes of AvA game. Still with stop 0x101.

Running Prime95 atm, will update the result ASAP

 

[writhziden]

Did you check the NB temperature and fan?

 

[snafu22]

Did you check the NB temperature and fan?

Yes, it's warm but it didn't feel like anything close to 90c. Speccy and HWinfo now saying that my motherboard temp is 30c... weird...

EDIT: Ran Prime95 for 1 hour (because i have work to do involving the pc) - no errors
Done a clean (formatted all of my partitions) REINSTALL again of the OS, STILL had BSOD. So it is hardware problem? I'll contact my vendor ASAP to have replacements... And we'll see how things goes after that

 

[writhziden]

It is most likely hardware. Let us know how the replacements go. Best of luck!

 

[snafu22]

Hey guys, been out of town last 2 days.
Got the replacements from my vendor, turns out my motherboard was defect.
Switched to P8Z68-V, no BSOD or TDR whatsoever.
Had a hunch from the start that it was the motherboard that is acting up.

Thank you so much for your support writhziden, I really appreciate it.

 

[writhziden]

You're very welcome. Glad the new motherboard solved it.