Just had a BSOD reboot in XP--where is the info?

[Papageno]

The Event Viewer shows nothing, but I thought that Windows kept a record of the text that appears on the BSOD --where do I find this? This happens every once in a while (maybe every week or two) and I really want to get to the bottom of it, even if it means I have to replace this motherboard.

[freedoom]

if it's not in event viewer then just write down the pertinent info from the BSOD next time it happens and google it for a resolution.

[rei]

http://www.nirsoft.net/utils/blue_screen_view.html

[freedoom]

http://www.nirsoft.net/utils/blue_screen_view.html

a memory dump viewer! that's brilliant!

[Papageno]

Yeah, I started searching around and came up with the bluescreen view tool that rei just pointed out. (Thanks, rei!) Supposedly this last BSOD was caused by the NTOS kernel driver itself and caught by the Bug check string IRQL etc. shown below. Anyone have the faintest idea how to start troubleshooting this?

Mini111409-01.dmp 11/14/2009 12:22:41 PM IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0xf7800247 0x00000002 0x00000001 0x80522770 ntoskrnl.exe ntoskrnl.exe+4b770 NT Kernel & System Microsoft Corporation 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435) 32-bit C:\WINDOWS\minidump\Mini111409-01.dmp

[rei]

i gave up years ago in troubleshooting these and just reimage or start replacing things.

[HighPlainsDrifter]

Eh, some dude wrote up a process for figuring out exactly what is causing the issue, see part 1 (http://www.adopenstatic.com/cs/blogs/ken/archive/2006/10/01/Causes_2C00_-and-tips-for-debugging_2C00_-a-STOP-0x0000000A-_2800_IRQL_5F00_NOT_5F00_LESS_5F00_OR_5F00_EQUAL_2 900_-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx), part 2 (http://www.adopenstatic.com/cs/blogs/ken/archive/2006/10/03/Causes_2C00_-and-tips-for-debugging_2C00_-a-STOP-0x0000000A-_2800_IRQL_5F00_NOT_5F00_LESS_5F00_OR_5F00_EQUAL_2 900_-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx), and part 3 (http://www.adopenstatic.com/cs/blogs/ken/archive/2007/01/09/1005.aspx)

rei's method might be easier :P

[Pogo]

I think there's a way to prevent the computer from restarting on a system error. I forget if this is a Windows setting or if it's in BIOS.

I usually just wrote down the error code on the BSOD and then Googled it to find an answer.

[Coca Cola Zero]

the best way to avoid stuff like this is not to run XP, IME. These days even driver level problems tend to keep Windows in a usable state and in the rare events when they happen, Windows 7 will usually even pop up a dialog telling you about the problem in plain English and suggesting fixes that are remarkably likely to work.

I could hardly believe how good Windows 7 was at diagnosing problems when I first saw it doing so in the beta. Now I can hardly believe anyone still runs XP. Poor bastards!

[Pogo]

I haven't had a BSOD on XP in years, not counting when my motherboard was failing on my Shuttle.

Is Windows 7 going to tell me when my motherboard is failing?

[bago]

Ever since Microsoft bought Doctor Watson, all crashes are mini-dumped and logged. They still ask permission to upload crash logs.

[Zylon]

I could hardly believe how good Windows 7 was at diagnosing problems when I first saw it doing so in the beta. Now I can hardly believe anyone still runs XP. Poor bastards!
So, what you're saying is that Win7 is great for people who suck at configuring a stable system.

[Coca Cola Zero]

So, what you're saying is that Win7 is great for people who suck at configuring a stable system.

No, I'm saying XP is great for little bitches who think sticking with an "old skewl" OS makes them somehow cool but are also too stupid to run Linux or another alternative OS.

[Papageno]

Charming.

Just so you know, CCZ, I'm glad I'm dual-booting because it appears that my wireless adapter (WUSB54G v4) isn't natively supported in Windows 7 32 bit, nor is there an official driver from Linksys. So until I can resolve that little problem I can't enjoy the new hotness.