Blue screen of dread, halp. (not fixed yet)

Aldo

Err, yup, I gots me a bluescreen now~ It doesn't really say anything, though. It says there has been an error and Windows had to be closed to prevent damage. Then it suggests a ton of stuff.

It suggests:
- check if there's enough room on the disk
- close windows and ask the microsofts if there's any updates (bullshit)
- replace the monitor adapter (eh?)
- see if there's an update for the BIOS (why would I have problems now, all of a sudden?)
- stop the BIOS processes of "caching" and "shadowing"
- delete some stuff in Safe Mode

And then the technical information, no idea what it means.

I have my harddisk set up in 2 partitions: C:/ 1 for Windows and schoolstuffs and / for music and games. I like this set-up.
Anyway: currently C has a whooping total of 1,68GB free space (D has 40-ish freespace).

As the blue screen suggests, this might be the problem. What is your opinion?


old OP

And it's hella annoying.

Every few hours or-so my PC automatically shuts down and restarts itself. This has happened at the least likely moments, such as doing nothing. I was taking the dog for a walk and when I got back, the PC had restarted itself, earlier today it was doing the same thing while I was merrily browsing around the intertubes. Yesterday it happened while playing a simple MMO and one more time whilst visiting PA.

I have already checked:

- Updates for Windows xp
- virusscan
- ventilator

I cleaned my PC yesterday after the first reboot, there was a lot of dust in there, so I figured that should have fixed it, but alas. No idea what to do next.

I have checked the logs to see what the hell happened and it only reports *that* the computer has turned on and off, I can't decipher what is causing it. There's a few error messages in the logs of system and antivirus, they're in Dutch, though. I'll roughly translate them~

system:

notification: Tcpip -- TCP/IP has reached the securitylimit of the amount of simultaneous connectionattempts through TCP

error: Disk -- Damaged block in device \Device\Harddisk0\D.

antivirus:

notification: Function setifaceUpdatePackages() has failed. Return code is 0x000004C7, dwRes is 000004C7.

TL;DR: PC automatically reboots itself, halp.


*edit: I have ServicePack 2, use Avast! and microsoft firewall.

Nozz

You're probably blue screening and your computer is set to reboot automatically upon fault, which is default for windows

Go into system settings and untick the box that says reboot immediately on crash or whatever

Then next time you crash at least you'll be able to see if you recognize whats crashing

EDIT: The damaged block thing may mean either a broken hdd, or one in need of a defrag

Aldo

Okay, unticked that box. When I restarted the PC froze at the "Welcome" screen, but I doubt that has anything to do with the problem at hand.

I'll let DisKeeper defrag now.

Thanks

Heliosphan

Whats the temperature like inside your case?
i think anything above 45-47 is getting bad and should be checked then above 53 is very dangerous

Nozz

Heliosphan wrote: »

Whats the temperature like inside your case?
i think anything above 45-47 is getting bad and should be checked then above 53 is very dangerous

completely dependent on processor make/model.

And even 53 isn't that hot, my intel core 2 duo macbook idles at 53 when it's warm out.

Aldo

Celsius, I assume? <_<>_>

I defragmentated the thing and I haven't had any reboots, yet. If the problems comes back, I'll look into the temperature some more.

Nozz

Aldo wrote: »

Celsius, I assume? <_<>_>

I defragmentated the thing and I haven't had any reboots, yet. If the problems comes back, I'll look into the temperature some more.

make sure you jot down the important information on the blue screen if it does happen to occur again

Aldo

Nozz wrote: »

Aldo wrote: »

Celsius, I assume? <_<>_>

I defragmentated the thing and I haven't had any reboots, yet. If the problems comes back, I'll look into the temperature some more.

make sure you jot down the important information on the blue screen if it does happen to occur again

Yes, I'll take a picture or something. Thanks for the help y'all. :^:

Heliosphan

oh yea, sorry i meant celsius not fahrenheit. damn american's, have to be different

Aldo

Err, yup, I gots me a bluescreen now~ It doesn't really say anything, though. It says there has been an error and Windows had to be closed to prevent damage. Then it suggests a ton of stuff.

It suggests:
- check if there's enough room on the disk
- close windows and ask the microsofts if there's any updates (bullshit)
- replace the monitor adapter (eh?)
- see if there's an update for the BIOS (why would I have problems now, all of a sudden?)
- stop the BIOS processes of "caching" and "shadowing"
- delete some stuff in Safe Mode

And then the technical information, no idea what it means.

I have my harddisk set up in 2 partitions: C:/ 1 for Windows and schoolstuffs and / for music and games. I like this set-up.
Anyway: currently C has a whooping total of 1,68GB free space (D has 40-ish freespace).

As the blue screen suggests, this might be the problem. What is your opinion?

(I've updated the OP with this as well)

Aldo

Ok, another bluescreen, this time it had a title~ "IRQL_NOT_LESS_OR_EQUAL" After a google, I understand that it is in fact a hardware problem, most likely due to overheating.

I'll look into it, you guys have been of great help in making this problem understandable for me, thanks :^:

stigweard

0x0000007e is a thread exception and the first parameter 0xc000005e is a status access violation which means a memory access violation has occurred. A couple of places to look are the processor overheating (or bad cache on the proc), a bad ram stick, faulty capacitors, or a weak power supply. There are other possibilities with that error, but those are more likely.

Aldo

stigweard wrote: »

0x0000007e is a thread exception and the first parameter 0xc000005e is a status access violation which means a memory access violation has occurred. A couple of places to look are the processor overheating (or bad cache on the proc), a bad ram stick, faulty capacitors, or a weak power supply. There are other possibilities with that error, but those are more likely.

I know how I can check for overheating (BIOS menu), is there an easy way for a layman like me to check the other things?

Aldo

Oh, this becomes sillier and sillier. :P

Now I got the following blue screen error: PAGE_FAULT_IN_NONPAGED_AREA Which -- according to microsoft indicates a problem with being unable to find certain data, most likely due to a problem with the installation of hardware. I haven't installed anything in the past year, so I suppose it's one of the less likely solutions.

What confuses me is that I'm getting a different error message every time.

stigweard

http://www.memtest86.org/ is a tool you can use to check your ram. You can go to the manufacturer's site for your hdd and download diagnostic software that will test it and tell you if it is going bad. A program like Prime95 will tell you if there is a problem with cpu / ram by performing calculations and comparing the results to known good ones.Checking for bad capacitors involves cracking the case and looking for stains or bulging tops on capacitors. Paging errors are usually an indication of either bad ram or a bad hdd, but there is no set answer because errors have a nasty habit of disguising themselves as something they aren't.

Aldo

hm, thank you. I think I'll be taking this to the mom&pop 'puter store thingie. They can do all these things without accidentally nuking it or something.

I'll be using my laptop for the time being.

topic closed I suppose.