BSOD
I have recently been getting BSOD's each time with different stop codes ie: 0x0000008e, 0x000000d1, 0x0000000a. 0x0000000050 (win32k.sys) .Even in safe mode: 0x00000101 " a clock interupt was not recieved on a secondary processor within the allocated
time interval" What can I do each time i try to scan or remove files i get the BSOD. Please help.
June 21st, 2011 10:56am
Bug Check Code 0x101: http://msdn.microsoft.com/en-us/library/ff557211(VS.85).aspx
Cause
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.
There is a problem with your processor. Please contact your manufacturer Technical Support for more information.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows 7, Configuring
Microsoft Certified
IT Professional: Enterprise Administrator
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 11:02am
You may boot in Clean Boot Mode.
Perform a clean startup to determine whether background programs are interfering with your game or program
If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files,
rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver
is the root cause.
Another way is enable muni-dump and use Windbg. Please refer:
How to read the small memory dump files that Windows creates for debugging
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 23rd, 2011 10:09am