• Sign in to Neowin Faster!

    Create an account on Neowin to contribute and support the site.

Sign in to follow this  

Anyone still "BSOD-free" using Windows XP?

Have you experienced the "Blue Screen of Death"  

257 members have voted

You do not have permission to vote in this poll, or see the poll results. Please sign in or register to vote in this poll.

Recommended Posts

Keldyn    1
wow you have some serious hardware problems going on if you've got that many BSOD's. if you built your current computer, don't do it next time. (not trying to be mean, just honest)

Aye. I made much the same suggestion. Not a commentary on your skills Anita but I really do think it would help a lot to have a professional look it over for you. They may even be able to tell you where you went wrong.

Share this post


Link to post
Share on other sites
ThisSiteHasLostItsCharm    263
I've only had one non-Halo related BSOD *shakes fist at Halo programmers* and that was when I accidentaly used the new hardware detected thing to install video drivers :whistle: I've probably had about 50 BSODs from Halo :angry: :no:

yea i all i get is dam halo bsods. stupid coders.

Share this post


Link to post
Share on other sites
Malechai    120

anita.. I've found links to most of your stop errors and pasted them below. all generally point to hardware problems or incorrect bios settings. you've got big hardware problems and have quite a bit to fix with that pc of yours, sorry to say..

stop: 0x00000024

http://www.microsoft.com/technet/treeview/...md_stp_swhw.asp

stop: 0x00000050

http://www.microsoft.com/technet/treeview/...md_stp_ccgm.asp

stop: 0x0000008e

http://support.microsoft.com/?kbid=315335

stop: 0x0000007e

http://support.microsoft.com/?kbid=330182

stop: 0x0000000a

http://support.microsoft.com/?kbid=314063

stop: 0x0000007f

http://support.microsoft.com/default.aspx?...&NoWebContent=1

I've been building my computers for about 8yrs now and I NEVER had problems like this with 3.1, 95, 98, or 98se. I've had the cpu, mobo, and memory tested and I used WDs diagnostics on the HD to check them and they passed.
i'm going to wager the reason you've never had problems with earlier windows is because they were more forgiving than XP is. XP is a strickler with hardware issues, and thats a good thing because you'll know sooner and can get it fixed. you may have had the stuff tested, and each may work separately, but its obvious theres compatibility issues when they're all put together.

Share this post


Link to post
Share on other sites
memNOC    0

ive had a BSOD twice since i've been working with XP Pro since late 2001.. one for faulty RAM and another faulty HD..

:whistle:

Share this post


Link to post
Share on other sites
aem4162    0
Aye. I made much the same suggestion. Not a commentary on your skills Anita but I really do think it would help a lot to have a professional look it over for you. They may even be able to tell you where you went wrong.

it's been in the shop, people

Share this post


Link to post
Share on other sites
aem4162    0
anita.. I've found links to most of your stop errors and pasted them below. all generally point to hardware problems or incorrect bios settings. you've got big hardware problems and have quite a bit to fix with that pc of yours, sorry to say..

stop: 0x00000024

http://www.microsoft.com/technet/treeview/...md_stp_swhw.asp

stop: 0x00000050

http://www.microsoft.com/technet/treeview/...md_stp_ccgm.asp

stop: 0x0000008e

http://support.microsoft.com/?kbid=315335

stop: 0x0000007e

http://support.microsoft.com/?kbid=330182

stop: 0x0000000a

http://support.microsoft.com/?kbid=314063

stop: 0x0000007f

http://support.microsoft.com/default.aspx?...&NoWebContent=1

I've been building my computers for about 8yrs now and I NEVER had problems like this with 3.1, 95, 98, or 98se. I've had the cpu, mobo, and memory tested and I used WDs diagnostics on the HD to check them and they passed.
i'm going to wager the reason you've never had problems with earlier windows is because they were more forgiving than XP is. XP is a strickler with hardware issues, and thats a good thing because you'll know sooner and can get it fixed. you may have had the stuff tested, and each may work separately, but its obvious theres compatibility issues when they're all put together.

thanks :)

Share this post


Link to post
Share on other sites
Daybreak    1

I've had 2 BSODs so far - bad RAM and one caused by Creative's driver and VMWare interacting..

aem4162, having experienced similar problems, it looks honestly like bad RAM to me.

You used memtest86 yet? Even then, it doesn't pick out bad RAM all the time... For my case of bad RAM, it failed to pick up anything even after one or two complete cycles... It was only in desperation when I removed one ( of the two ) memory modules did it start detecting errors.

Share this post


Link to post
Share on other sites
~Bull}{Dog~    0

Only ever had blue screens when XP was first released.

Was the Nvida ones that everyone was getting.. Nothing like that at all now.

Share this post


Link to post
Share on other sites
Gweedo    0

I've had a few, couple of them from a software RAM drive I was installing. A couple others were from conflicts with the two video cards I have in my system. No biggies though.

Share this post


Link to post
Share on other sites
wired57    4

I've seen them on customers machines, along with my own development/test machines where I had some bad ram to test and such but otherwise none on my notebook

Share this post


Link to post
Share on other sites
CoolShady2002    0

Ive had dozens due to bad drivers and I have also had about 6 or 7 one-offs which OCA has been unable to determine the cause of.

I also had NAV cause a BSOD on shutdown once too.

Share this post


Link to post
Share on other sites
midway40    0

Only a couple of BSOD's when I was testing Whistler Beta (I think it was the Nvidia problem back then). None since I went to WinHome. :)

Share this post


Link to post
Share on other sites
aem4162    0
I've had 2 BSODs so far - bad RAM and one caused by Creative's driver and VMWare interacting..

aem4162, having experienced similar problems, it looks honestly like bad RAM to me.

You used memtest86 yet? Even then, it doesn't pick out bad RAM all the time... For my case of bad RAM, it failed to pick up anything even after one or two complete cycles... It was only in desperation when I removed one ( of the two ) memory modules did it start detecting errors.

I don't know if Memtest86 has been tried yet...I'm dling it now

thanks :)

Share this post


Link to post
Share on other sites
Yuxi    2

I only got two, both from bad RAM. After that, no more BSODs for me :D

Share this post


Link to post
Share on other sites
KeR    84

I have never had one....not even since I was testing it starting with Beta1

Share this post


Link to post
Share on other sites
AshMan    0

XP has never crashed on me, not even the beta version. I haven't seen a BSoD sice late 1999.

Share this post


Link to post
Share on other sites
NeoMasamune    0

I've never had a bsod in xp, but I have had the computer just freeze up on me.

Share this post


Link to post
Share on other sites
dreamz    4

just one when kerio crashed on me, but xp has been stable since i installed it july 1 this year. :)

Share this post


Link to post
Share on other sites
BTallack    0

I see them almost every day. I'm also a computer tech, and I usually have at least 10 computers through my shop a day.

Share this post


Link to post
Share on other sites
devBrian    64

No problems here.

Share this post


Link to post
Share on other sites
M$ Agent #2    0
I only had some BSOD's when I had a bad stick of Ram now I use name brand memory

no more of that Centon Ram for me..... (took me almost a week to figure out it was bad ram)

lol talk about hair pulling :) Now of course I have a bootable Ram test CD :)

bootable ram cd test ?

Yeah its a program that boots your computer from the CD and it tests the ram with like 12 different tests and will tell you wich stick of ram is bad. I can send the image to you as I think its freeware (ill have to check it first tho) PM me and if it is I will Email you it if your interested. Totaly awsome if you suspect bad ram this will weed out that problem.

Edit: Also compressed its only like 12 megs or so. So even if your on Dial up shouldnt be a problem.

Share this post


Link to post
Share on other sites
AshMan    0

Oh, I've just GOT TO add, I've had more crashes on OSX than I ever had on WinMe. In fact, Sony Viao supported WinMe so well, that I don't ever recall any problems let alone crashes with WinMe. And as for the BSoD, at least they offer some useful information as to the nature of the crash, as oppose to OSX that just crashes.

I don't see why Apple made such a bitchy ad about Windows crashing. As far as I see it, it's false advertising.

Well done Microsoft. (Y)

Share this post


Link to post
Share on other sites
OptiPlex    0

It crashed because Halo crashed. :ninja:

Other than that, it never crashes (Y)

Share this post


Link to post
Share on other sites
nekrosoft13    747

i had maybe 4-5 since july 2001

Share this post


Link to post
Share on other sites
[hxc]    0

only one i have had was yesterday! my mp3 player was connected to my computer via usb and i was transferring stuff...my brother unplugged the usb side of the cord thinking it was my webcam... BAM! BSOD :(

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.