Discussion Locked

Help me DEBUG my computer in conflict!

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi. My computer was continuously restarting suddenly (only changes made to computer was installing Microsoft's last 2 critical updates for W2K). I followed advice I saw here in the forum to uncheck the "Automatically Reboot" option in the System Failure tab in Control Panel/System. Now it has shown me a very informative blue screen and this is what it reads:

"***STOP:0x000000C2 <0x00000099,0xFF8F9D88,0x00000000,0x00000000>
BAD_POOL_CALLER

BEGINNING DUMP OF PHYSICAL MEMORY
PHYSICAL MEMORY DUMP COMPLETED-CONTACT YOUR SYSTEM ADMINISTRATOR OR
TECHNICAL SUPPORT GROUP

Can anyone help me debug this???
Thank you!

5 replies

by jdmercha

Are you running an up-to-date virus scanner?
Can you boot into safe mode?
Does the computer still reboot itself from safe mode?
Can you boot to a CD?
Does the computer still reboot itself when it boots from a CD?

by ohreli

From Microsoft bulletins, it appears to be a bad driver of some sort. I can boot into WIndows fine, the crash happens between 15 min and 1 hour after I boot. Everything works fine until the crash. I havent tried safe mode---I guess that would narrow down the problem...Remind me how to enter safe mode in W2K...

by jhoejhit

this will help you clean the bad sectors of your HDD. You can use win98 startup, type scandisk C: at A: prompt/ drive A:, to start you pc to safe mode click "F8" before windows starts, thin follow direction, you need to have administrators password.

by dbucyk

You don't need to debug your computer. What has happened is the codes have been overwritten and with the thousands of lines of code in Windows, that particular update has caused a device to conflict with the windows update. I had this problem before when I installed an internet explorer update and found myself dealing with a blue screen.

My best advice is to boot into safe mode. Check to see what devices are conflicting, either through device manager or through Dr. Watson.

If there are no devices conflicting through device manger, then ad dr. watson into the startup through safe mode if possible. Reboot you're computer and dr. watson should be able to log the problem for you. Go into the log file through safemode and check it out from there.

Then if that doesn't work, use another person's computer and check out technet through Microsoft and they will have possible troubleshooting that can be done to fix the problem.

This discussion is closed to new replies.