Heh, so for the first time, I saw the BSOD for Windows XP Home. Happened an hour or so ago when I tried to shut down my computer. I didn't even know XP still had the BSOD. Now I'm curious what did it, since I did all the same things I normally do, and my computer showed nothing wrong until shutdown time. Of course, it could've been a one time thing....could've been something else Norton failed to protect me from.
XP has the BSOD. I learned something today. =P
Hiead
ID:185862
 Oct 11 2005, 5:19 pm
|
|
|
Oct 11 2005, 5:25 pm
|
|
Scoobert
 |
The BSOD is "Disabled" by forcing the computer to restart. You never see it because the computer just restarts rather than showing you it. There are many things that can cause it. It is hard to pin it down, might want to check your logs to see what services might have crashed or been acting weird.
|
I was just surprised that XP had it at all. I had never seen it at all, and my dad has had XP Home since about the time it came out(and his computer has always been virus/spyware/adware/etc. ridden). His computer would normally just crash, so I had always assumed that that was the default function of XP.
Kinda nice to see the BSOD, though. Kinda like an old friend that I spent a lot of time with back when I used 3.1, 95, 98, 98SE, and especially ME. Hiead | |
Heh, ya, you can toggle it on and off, but I don't remember where. I never get it, or the reboot that replaces BSOD, I am not sure what causes it, but I think it is hardware issues, most of the time at least.
| |
Well the hardware's all fairly new bought. I just got the whole PC a little before school started back. So the only hardware that I might expect to be faulty would be wireless network adapter(Hawking Tech., cost me about $5 after rebates, on sale).
It's not exactly Netgear or Linksys or anything, some little USB thing about the side of a small gum packet that sucks at picking up reception(signal strength is always Low or Very Low, and the router is about 2 small rooms away(through walls)). I won't really worry about it now, but if I see it again I think I'll start reading logs. Hiead | |
Well, a USB adapter is not your problem. It could have just been a random memory fluke. If it starts happening on a regular basic, watch out, it could be bad.
| |
From what I've read, the XP BSOD is much more serious than the old 9x BSODs... That's why no one ever sees them... Something needs to be royally screwed up to make it appear (whereas you could sneeze and the 9x BSOD would come up...lol)
Of course, that's no reason to panic, it's just what I've heard...lol I've only seen it once myself, on a laptop I was working on for someone... Their Windows install was somehow corrupted (the machine wouldn't get past the Loading XP screen, except for in Safe Mode, in which it crashed for not finding two files), so I used my XP disc to repair it... The problem was that my XP disc is only SP 1, and their original install was SP 2... Not a huge deal, the computer would now at least boot up, but I wanted to put it back exactly the way they had it... So, the logical step was to install SP 2, right? Well, it would install the entire thing, and at the end it decided that it didn't have access, and would uninstall the whole thing, then reboot... Upon reboot, I got the BSOD (well, it reboots vry quickly after it comes up, but it was there)... Apparently, it got stuck somewhere between SP 1 and 2, and it didn't like that...lol I had to start all over... So, your BSOD might be related to a Windows file problem, in addition to what Scoobert mentioned... | |
Hiead wrote:
Heh, so for the first time, I saw the BSOD for Windows XP Home. Happened an hour or so ago when I tried to shut down my computer. I didn't even know XP still had the BSOD. Now I'm curious what did it, since I did all the same things I normally do, and my computer showed nothing wrong until shutdown time. Of course, it could've been a one time thing....could've been something else Norton failed to protect me from.Here's something for you. If I remember right, the X-Box has the BSOD. | |
SuperSaiyanGokuX wrote:
(whereas you could sneeze and the 9x BSOD would come up...lol) Heh... I have an old computer running Windows 95... There have been times it's on that every other action (click, type, execute program) gave the BSOD and the others gave: "This program has performed an illegal operation and will be shut down." I really hate that: Primarily because restarting stopped the problem. odd... --Vito | |
I used Windows 98 for a good five years and didn't encounter it except for when I'd do something stupid that caused it (most of the time a program I'd make would cause a memory leak or whatnot). I never encountered it out of turn. Windows 95 is another story, though.
| |
SuperSaiyan....:
It did it the last time I shut down, too. I'm not really too interested in looking into it(although I said I would if it happened again). It gets through the entire shutdown process, and I don't encounter any problems while it's running, so unless I notice any escalation in problems, I'll put up with a blue screen each time I shut down. Nadrew: I noticed you didn't even bring up Millenium Edition. =P Would that be because you never used it, or because ME was such a failure of an OS that it doesn't deserve mentioning? Hiead | |
Hiead wrote:
Nadrew: Probably. It's what I'd do. | |
I never really bothered with ME, my sister had it on her computer and I had to fix the thing once a week. 2000 was fine, but I never used it for personal use.
| |
Nadrew wrote:
I used Windows 98 for a good five years and didn't encounter it except for when I'd do something stupid that caused it. Heck, I used windows ME and I never got BSOD'd except when I did something stupid that caused it. Honestly, I only stopped using ME because of software that was being written for XP instead of ME and was becoming incompatable. I realize that a lot of people had bad experiences with ME, but here's one user that has mostly good things to say. | |