Sign in with
Sign up | Sign in
Your question

Blue Screen 0x101 need help!

Tags:
  • Blue Screen
  • Games
  • Processors
  • Computers
  • CPUs
Last response: in CPUs
Share
August 20, 2014 3:48:39 PM

Hi whenever I play the game "Marvel Heroes 2015" after 2 hours or so my computer blue screens and the error is 0x101 and I asked support they said: 0x101: CLOCK_WATCHDOG_TIMEOUT
Cause: The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked. Which I clearly have no idea what this means. If y'all need more information let me know. I have no idea on how to up the voltage either was reading up on it tried to research but lack of time. Thanks ahead of time!

More about : blue screen 0x101

a b à CPUs
September 12, 2014 11:14:00 AM

it means one program is accessing hardware from one core of your cpu and blocking a program running on another core of your CPU from getting access. After a certain timeout the system bugchecks because it thinks your processor is hung.

most often it turns out to be a USB driver. Either the USB chipset driver for your motherboard or very often a bug in a USB network driver.

So, without looking I would guess: update your CPU chipset drivers
directly from the vendor or intel if you have a intel CPU. google "intel chipset driver"
and you can get the update.

if you have a USB thumb network device update the driver for it if you can get it.
very common to have bugs in the default driver.

beyond that for a 0x101 error you have to run verifer.exe and set debug flags and
turn on kernel mode memory dump (not mini dump) then look at the memory .dmp file with a windows debugger to figure out the problem.

Also, USB support depends on a the BIOS so it is often good to update the BIOS if you have not done so.

you might also run usbview.exe from the windows standalone debugging tools to see if you have a reported error with your USB devices.

sometimes you can have a failed install of a USB network driver that causes the system to hang waiting for the driver to install (never does) and causes this bugcheck.
(driver bug)


m
0
l
!