Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
So I have this ancient HP Pavilion hanging around and I figured I could use it for something, so I upgraded it to Windows 2000 Pro so it would at least be NTFS and work with modern network setups (and not have the bugs of 98). After installation, it worked fine the first time I started it up, and it even worked over multiple restarts. But when I shut it down and later turned it on again, it gives me a BSOD right after the fullscreen loading graphic is finished. The STOP error codes read as follows:
0x000000C2 (0x00000007, 0x00000B8A, 0xF381B6F8, F381B700) BAD_POOL_CALLER
Booting in Safe Mode works fine, of course, but that disables just about every hardware device and forces me to 640x480 at 16 colors. If I go to the Device Manager, Windows says all the devices are working fine.
Everything I've been able to find on the internet about this error seems to assume that it occurs sometime while Windows is already running, rather than at startup. I did find a Microsoft KB article on debugging it, but it was so incredibly technical and confusing that it nearly bowled me over. Any other information I can provide about the computer I'd be glad to give you.

My friend encountered bugcheck code 0x000000c2 when he shutdown W2K. After he re-install W2k, the problem disappear. It is obviously one of the device driver is in error. When he re-install W2K, he did not install the the faulty device driver. He could not recall which device driver was the culprit as he installed too many software at his windows.
Try re-install W2K. Don't install all the software in a row. Install the software one by one. Test W2k for two to three hours. Install another software and test until the same problem occurs.
The last installed software is the culprit.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |