|27 Jun 2012||#1|
| || |
Random BSOD error x101
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
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
|My System Specs|
|28 Jun 2012||#2|
| || |
Hello and welcome to Sevenforums.
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
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.
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
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 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
A few suggestions!
|My System Specs|
|Similar help and support threads for2: Random BSOD error x101|
|Random BSOD stop error 0x0000001E, hardware error?||BSOD Help and Support|
|BSOD at random. Last BSOD while using Firefox. Error 0x0000000a||BSOD Help and Support|
|BSOD Stop x101 and x009c||BSOD Help and Support|
|Random BSOD's random error codes||BSOD Help and Support|
|Random BSOD during Random times, error 0x8000000000000002||BSOD Help and Support|
|Random BSOD's with random error messages after a new setup||BSOD Help and Support|