Help - Pc Keeps Rebooting

mikeh420 · #1 8th Aug 03, 07:57 PM

Help?

Ever since I removed my CPU to test in another M/board, after replacing it in this PC, it's rebooted eight times yesterday, and once today. could I have partially fried the CPU by moving it freom one m/b to another? I'm running XP Pro w/a Celeron 900, 512 MB ram, 60GB HDD, haven't changed or added anything, tried a system restore yesterday, but that obviously didn't work. I'm getting files in a Windows/Minidump folder, but they don't really explain much. One says it has a problem with WIN32K.sys and another has a msg: DRIVER_IRQ_NOT_LESS_OR_EQUAL

Thanx in advance...

Mike

adams · #2 8th Aug 03, 08:33 PM

is that ram one stick or multiple sticks? if it is multiple check and make sure one of the sticks didn't go bad.

Sephiroth · #3 8th Aug 03, 08:35 PM

make sure the heatsink and fan are mounted on firmly on there, the cpu might be overheating since that's what you moved

BlackMantis · #4 8th Aug 03, 08:37 PM

Yea.. what you could also do is just make sure all your chips and cards are properly seated.. if an expansion card or memory isnt seated properly you could get a world of reboots.. maybe you must have hit one while operating on the PC. sounds like a simple problem tho, nothing you should worry too much about. good luck m8

mikeh420 · #5 8th Aug 03, 10:39 PM

Thanks all...

would any of that cause a blue screen and a dump? When I had a problem with my last m/b rebooting, it wouldn't give a blue screen or a dump. I'm going to try and get a new CPU, the Cel 1300 is around $45. The heat sink looks like it's seated OK and the fan is running. I was also running Motherboard Monitor 5 and it was at 89 F the last time it BSOD'd. Everything was perfect until I pulled out the CPU, that'll teach me to mess about!

mike

BlackMantis · #6 8th Aug 03, 10:51 PM

the way i see it is you gotta do isht to learn.. i pulled out a lot of isht outta my pc and sometimes i couldnt even boot up.. but a little reseating here and there did the trick. not saying this is the case with you but patience is a virtue. (sometimes)

mikeh420 · #7 8th Aug 03, 11:02 PM

Just reseated everyting andeven took out a memory stick. Yep, process of elimination, that's all. I also noticed it starts 'bouncing' 3 hours after a cold-start, which might make it heat-related, so I double checked the heat sink. The metal part of the CPU that touches the heat sink is a bit blue, like a chrome motorcycle tailpipe. I'll just keep it running and see.

Stringent · #8 8th Aug 03, 11:05 PM

Might be worth getting some heat sink compound on there if you haven't already.

mikeh420 · #9 8th Aug 03, 11:11 PM

There is just enough compound to be a little tacky, but I suppose a bit more couldn't hurt. I used to use that goop years ago doing electronic assembly, some of those fat power transistors could cook an egg!. Thanks for the idea.

mikeh420 · #10 8th Aug 03, 11:21 PM

Right after I finished my last post, I got a dialog box which read:

"Instruction at (big long hex addr) referenced memory address (another big hex#). This memory address could not be read. "

Adams73533, you might have just won the $64 question! At least RAM is cheaper than another CPU.

Crossing my fingers it's the RAM,

mike