Need help with a few system issues. Please take a look.

SSERAB

Member
Jul 7, 2001
110
0
0
This past weekend I took apart my entire PC, leaving the ram, and heatsink/fan attached to the mobo. I cleaned the dust out, added a blowhole fan in the top and an intake fan in the front. I re-assembled the PC adding in a slave Maxtor 160gb hard drive (see the rest of the system specs in my sig). Upon booting the first time I got an error that I had a non-working CPU or improper bios settings. I hit F1 to continue and the machine booted fine but no longer was overclocked. Basically I lost my ability to overclock, no matter what I do, the machine defaults to stock processor speeds. This is strange as I've had the 2.4ghz processor overclocked to 3.0 for a pretty long time now with no problems.

2nd issue is that after a little while of using the PC it all of a sudden dropped it's resolution and rebooted itself. I've seen lots of these random reboot problems on here but no solutions at this time. I've had this issue a few times in the last few weeks, even before I stripped the PC down. I will check for a virus tonight, and I'm hoping that's all it is.

3rd issue is that the 160gb maxtor is seen by the bios correctly but does not appear in my windows explorer. It's even in my hardware profile in windows but I just don't have an icon for it?

Anyone have any answers to these issues??? Thanks in advance.
 

HKSturboKID

Golden Member
Oct 20, 2000
1,816
0
0
For #3. Did you try to use disk management in the administrative tools to see if it pickup the drive.
 

egale

Senior member
Jun 5, 2002
848
0
0
I don't think a new drive will show up in Windows explorer until it is formatted. Once that is done, it should show up.
 

SSERAB

Member
Jul 7, 2001
110
0
0
HKSturboKID was exactly right. I did what he said formatted the drive and now it shows up in explorer. Thanks. Number 3 is solved. Next will be #2. I will check for the blaster worm files shortly.
 

SSERAB

Member
Jul 7, 2001
110
0
0
Fixed problem number one, got it to overclock to 3.0 again, was just a settings issue. Also updated the bios to rev 1.7 from 1.3.

I tried to update my video driver but each time I uninstall it, windows re-installs it. Last random re-boot was before the bios update. I patched windows with the auto update from microsoft, don't think it's the blaster worm. I'm crossing my fingers that the bios update will help with the reboots but this was the message I got just after the last reboot (had shut off auto restart, got the blue screen message which basically said to either update the bios, or check video drivers):

Stop: 0x0000007e (0xc0000005, 0x805idcc6, 0xf7c7d780, 0xf7c7d480)

I have no idea what that stop message means, can't find anything on microsoft's website about it?
 

DOSfan

Senior member
Sep 19, 2003
522
0
0
SSERAB, I did a search on Microsofts Knowledge base for your stop error, this is what I found.

I hope this helps.... I did not know where to begin with the articles.

And if you need the Knowledge base (or any other support based problems) in the future, go here.
 

SSERAB

Member
Jul 7, 2001
110
0
0
Thanks DOSfan, I did go to microsoft's site and could not find a specific match to my stop error. What I did was updated the bios of my motherboard last night and I was able to completely burn a DVD which I usually would not be able to do due to the reboot bug. The stop message I got did mention a bios update so maybe this has fixed the problem. I did manage to fix my overclocking also. I'm back at 3.0ghz and my 160 gb Maxtor is up and running now. I also did a total security update from microsoft's website. Hopefully this will fix it but only time will tell.
 

SSERAB

Member
Jul 7, 2001
110
0
0
Got another stop error last night. The PC seems more stable now but when I booted yesterday it said it had recovered from a serious error, then it was fine, when I went to restart it a little later I got:

Bad_Pool_Caller

Stop: 0x000000c2 (0x00000007, 0x00000cd4, 0x00000000, 0x85c332f0)

Haven't had a chance to look it up on microsoft's site yet, probably later today. It's funny, it will run fine for a long time, burn discs, play games and then every once in a while it goes a little wacky.