BSOD

Over the last 6 months I've had increasing BSOD incidents. I can't directly reproduce the issue, it likes to be randomized. I have seen it immediately on initial bootup, and in all manner of applications, sometimes after hours of uptime. Need some help to point me in the right direction.

primary error reported in event viewer is X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC

system info
Win7 64 bit (x86)
4 Gig Ram
(4) 500 Gig HDD
system is homebrew, no major changes in last 12 months. OS installation is about 11 months old at this point.

Thanks for the help.

James

palantyri said:

Over the last 6 months I've had increasing BSOD incidents. I can't directly reproduce the issue, it likes to be randomized. I have seen it immediately on initial bootup, and in all manner of applications, sometimes after hours of uptime. Need some help to point me in the right direction.

primary error reported in event viewer is X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC

system info
Win7 64 bit (x86)
4 Gig Ram
(4) 500 Gig HDD
system is homebrew, no major changes in last 12 months. OS installation is about 11 months old at this point.

Thanks for the help.

James

James Hi and welcome

The most recent one was caused by BS_I2CIO.SYS is related to BIOSTAR I2C I/O driver. Manufcturer: BIOSTAR Group BIOSTAR

Your version is over 2 years old and needs to be updated as well as re-installed.

Code:

The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This  indicates that an expected clock interrupt on a secondary processor, in a  multi-processor system, was not received within the allocated interval.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Ken J

Ken,

Thanks for the tip. I went ahead and reviewed the drivers I had already downloaded & installed, and they match the set available from biostar's website at this point. I reinstalled the drivers, just for the sake of trying it, and lo and behold, it did decide to update the northbridge driver. Which could be it. The rest of the sub drivers all showed current, so I don't know how that didn't work the first time. The BS_I2CIO.SYS driver you mentioned above didn't actually change (ver info, file size and file dates remained the same) with the reinstall, but perhaps it was mildly corrupted. Tough to tell.

Since then, i've been stable for about 48 hours, so we'll see how the bake in goes. Thanks for your time.

James

Just to close the loop. I started having issues again with this error. I eventually just re-installed Win7 over the top of itself, and my issues have cleared.

James