Bluescreens and then reboots too quickly for me to read what it says

[mouser]

Whoever came up with the idea of having the system crash with a big blue screen with tiny text filling the screen and somewhere on there having a clue to what went wrong, followed by 500 milliseconds of delay and then a computer reboot that clears the screen, is a super genius.  i mean truly that is really something special.

now just for fun, does anyone know a way to figure out what the text might have been on a bluescreen that results in a system reset before you can read it?

ps i've been getting these bluescreens once a week lately and i suspect it's because i was crazy enough to install windows xp 64bit, but that's another matter.

[TucknDar]

there should be some files in Windows\Minidump with the information from every Bluescreen. They can be read with MS Windows Debugging tools.

[nosh]

Check out this thread.

Even if it disobeys the "stop on error" you should be left with a crashdump to analyze

[TucknDar]

Also, you might want to check the following "change the value of 'AutoReboot' to equal '1' for automatic reboot, or '0' for disabled."  You'll find it in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

[Veign]

If the blue screen occurs during the boot process you may want to check out BootVis and see if that gives you any clue.

[Josh]

Blue screens are always recorded in the event viewer. Check eventvwr.msc (start - run) and look under system. You will see a listing for bug check. The first hex code is the one you want. You can get more detail on the code from the windows debugging tools at microsoft.com

[mouser]

what i want to know is, why does it take so long to get a response on this forum, i mean it's been amost 50 minutes and only 5 useful replies?

[Veign]

Blue screens are always recorded in the event viewer. Check eventvwr.msc (start - run) and look under system. You will see a listing for bug check. The first hex code is the one you want. You can get more detail on the code from the windows debugging tools at microsoft.com

And if you want to find more information on an Event check out EventID.net (just made my blog yesterday - leave a comment if it helped).

[Veign]

what i want to know is, why does it take so long to get a response on this forum, i mean it's been amost 50 minutes and only 5 useful replies?

[Josh]

what i want to know is, why does it take so long to get a response on this forum, i mean it's been amost 50 minutes and only 5 useful replies?

Its called being mousered. Now you know how it feels! HAH!

[mouser]

i was being sarcastic.

[Josh]

And I was just using a potential opportunity to get a hit in on you!

[wauiler]

Bluescreens and then reboots too quickly for me to read what it says

You can fool around for hours trying to change the autorestart on error flag in the registry or....
you can simple record the screens during  boot  with your digital camera using the movie option.  Be sure to record a few seconds past the  blue screen flash.  then upload to another pc and scroll thru the frames until you get to the blue screen. 

[tinjaw]

Damn mouser. Search your own forum first. I'm pretty sure I have answered that question already. 

[f0dder]

Bluescreens and then reboots too quickly for me to read what it says

You can fool around for hours trying to change the autorestart on error flag in the registry or....
you can simple record the screens during  boot  with your digital camera using the movie option.  Be sure to record a few seconds past the  blue screen flash.  then upload to another pc and scroll thru the frames until you get to the blue screen. 

And you're saying that this is easier than simply turning the autoreboot off? O_o

mouser: do you, by any chance, have an onboard NIC of the Attansic/Atheros brand? I get BSODs whenever I change advanced properties of mine (things like frame size, interrupt moderation, ...) - dunno if it's the chip that's a piece of shite, or the x64 drivers. Other than that, no problems with XP64 here.

Let us know what the BSOD error code is, and whether it mentions a driver name. Also, as TucknDar mentioned, the minidump images contain a lot of useful information as well.

I'm fed up with the onboard NIC because of the BSODs, periodic errors when using a non-1500 frame size (I want gigabit speeds, dammit!), and abysmal performance... so I'm getting a gigabit PCI-e Intel NIC on monday.

[rjer2]

Mouser
You can view that blue screen by
making a change in the system
properties.
         Right click mycomputer and
click properties,click advanced at
the top then Startup and Recovery
tab at the bottom of the page.
         Uncheck Automatically Restart
box, and check write an event
to the system log.
          In the write debugging
information box select
kernel memory dump.
It will create a much
smaller file with all the
info you need.
          Click ok and
exit . The next bsod will stop
so you can look at all the info.
For as long as you like.
                                 

[mouser]

thanks everyone for the advice -- the next time it happens i will now be able to see it since i changed the reboot switch, and thanks to you guys i now know about the dump files 

ps. i guess the auto reboot could be useful if its a remote pc or something.  a MUCH smarter choice would have been to ALWAYS PAUSE on a blue screen for a few seconds.

[lanux128]

a little late but as rjer2 mentioned, unchecking the auto-restart option could be helpful. also attaching a screenshot.

[attach=#]

[f0dder]

ps. i guess the auto reboot could be useful if its a remote pc or something.  a MUCH smarter choice would have been to ALWAYS PAUSE on a blue screen for a few seconds.

Spot on the sugar, wrt. both points.

[Carol Haynes]

You can also get extra info from MSKB from the EventViewer just double click the event and then click on the support link. It will open Windows Help with any info available - but also has an automatic search on the left of MS KB.