Windows 7: Random BSOD error x101

guitarmanjared · 27 Jun 2012

I am currently running windows home premium x64. I have gotten the BSOD occasionally inthe past but today it has happened numerous times. I recently updated my graphics card driver, however, i had the problem before that. my specs are

AMD FX 4100 quad core 3.60 Ghz
Nvidia gtx 560
8gb Ram
asus m5a97 motherboard

Any help would be great, i also am a noob and when i try to zip up the dump files it tells me i cant

FredeGail · 28 Jun 2012

Hello and welcome to Sevenforums.

BSOD Analyse

I see a few timestamp issues related to your Nvidia Driver. Do the procedure below for a reinstallation and in order to avoid leftover files.

i) Make your way to Nvidia Drivers - Download NVIDIA Drivers
ii) Uninstall the one you currently have and all its extensions
iii) Download Driver Sweeper
iv) Get to safe mode (without network) and search for Driver Sweeper in your

v) Select all the Nvidia components and analyse them
vi) Clean them, head into Windows without internet and download the driver

SFC /scannow

Windows components were blamed. It's the most common command used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

BSOD Summary

Code:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

I do see a few issues with the processor. Do you have the cooling installed correctly? Make sure it won't get overheated. Monitor your temperatures while you're using your computer.

A few suggestions!

Best Regards,
Frederik.

Windows 7: Random BSOD error x101

Random BSOD error x101 problems?