Weird thing just happened...

d3moliti0n · 25 Sep 2008 at 23:41

Hi

So like a minute ago my computer just crashed, and it came up with a screen with a dark blue background full of writing saying something about encountering an error, but this only appeared for like 5 second or less before my computer restarted back to the desktop perfectly fine. Does anyone have any idea what this may be related to, and if it's anything I should be worrying about for the future incase my computer crashes all together?

Thanks for your help,

d3moliti0n

Burningmace · 25 Sep 2008 at 23:48

BSOD?

d3moliti0n · 25 Sep 2008 at 23:51

I have no idea what it was, I didn't even have a chance to read it as it appeared and dissapeared within a few seconds. I just saw the first line saying something about an error.

Burningmace · 25 Sep 2008 at 23:55

Sounds like a bluescreen. Check your event log (Start -> Run... eventvwr.msc) and look for errors under the System category (if you're on Vista, it's under Windows Logs > System). Look for anything recent labelled as 'Error' and post all the info you can from it.

cooljimy84 · 25 Sep 2008 at 23:57

i know in windozs XP it's set to display the BSOD for a few seconds and then auto reboot....

d3moliti0n · 25 Sep 2008 at 23:59

Yeah, there are quite a few errors, looks to be like something to do with applications on my system. Got errors for: .NET Runtime 2.0 Error Reporting, Msi Installer, Service Control Manager and ati2mtag.

Burningmace · 26 Sep 2008 at 00:05

cooljimy84 said:
i know in windozs XP it's set to display the BSOD for a few seconds and then auto reboot....

Actually it's configurable. By default, the system just reboots instantly without displaying the BSOD.

You can change this by right clicking My Computer > Properties...
Then go to the Advanced tab and click the Settings button under Startup and Recovery.

In XP, the 'Automatically Restart' setting will cause the machine to reboot without displaying the BSOD. In Vista, it sets whether the system reboots itself after the BSOD does a memory dump, or whether you reboot it manually. If the dump type is set to Small Memory Dump (64KB), it only takes a few tenths of a second to complete the dump and you'll only see the error for a split second. I personally use Kernel Memory Dump, as I can usually deduce errors without doing a full memory dump.

Another thing that can cause a BSOD to cut short is if it fails to write the dump to the drive. This can happen if your hard disk is on the way out.

Burningmace · 26 Sep 2008 at 00:06

d3moliti0n said:
Yeah, there are quite a few errors, looks to be like something to do with applications on my system. Got errors for: .NET Runtime 2.0 Error Reporting, Msi Installer, Service Control Manager and ati2mtag.

They're application errors. On the left there are several categories - choose System instead of Applications.

Hen_Dawg · 26 Sep 2008 at 00:07

I get them now and then, only start to worry if they happen all the time

d3moliti0n · 26 Sep 2008 at 00:09

Yeah, the Service Control Manager and ati2mtag errors are under the System category. There are also a few warnings there aswell, Dhcp, W32Time and Tcpip.

Burningmace · 26 Sep 2008 at 00:13

Are you on XP or Vista? Look for any where the event source is 'System Error'.

d3moliti0n · 26 Sep 2008 at 00:13

I'm on Windows XP, and no, theres nothing saying System Error in the event source.

Burningmace · 26 Sep 2008 at 00:14

So, are there any under 'System Error'?

d3moliti0n · 26 Sep 2008 at 00:18

No, theres nothing saying 'System Error' on the event source in the System category. Just Service Control Manager and ati2mtag, these are the only errors.

Burningmace · 26 Sep 2008 at 00:20

In which case I can't do much to help. For now you'll just have to consider it an isolated incidence and hope it doesn't happen again. If it does, then feel free to drop back and I'll do all I can to help.

d3moliti0n · 26 Sep 2008 at 00:21

Ok, thanks for your help though.