[OverEasy]

Does anyone know how to fix the dreaded " BLUE SCREEN OF DEATH " ?

[JT]

Did you happen to take an update for Norton recently? If so, your going to have to do a system repair using your XP install disk.

[fubr]

get the number off of it if it gives one....
0000xxxxx0000083.....( or something simular)
type that in google it will tell you what needs fixed.
BOS is usually a fatal error within windows that it oes not know what to do.
re-installing windows by doing a repiar instal may fix it.
might can even use recovery console to fix it by booting to the xp cd but you have to know what your doing and which file to copy over.

[OverEasy]

Thanks guys I contacted microsoft and they didn't know what the error is they wanted to send me to tech suport but I didn't have time so I thought I would ask here.

STOP: 0X000000D1 (0X3D5202C9,0X00000002,0X00000000,0XF6C79386)
this is one of the errors. I think its bad RAM.

THANKS OverEasy

[elperro]

Blue error screen could be bad ram. If you have both memory dimm slots filled take one out and boot computer; if you get same blue screen then try the other memory dimm by itself and boot system again. If you still get blue error screen try using a third memory dimm from another computer that is working (with same style pc100, ddr, or ddr2). If computer does not boot up after this steps then it could be a bad harddrive.

[fubr]

ram can be picky about who it plays with... rule of thumb is use same model, same vendor perferably ran on same assembly line in the same batch.
Now that last part would be luck.
I had three diferent vendors in a old desktop and it worked fine for awhile then got BOS on it and after screwing with hard drive for two days I pulled all the ram out and only stuck one stick back in.
then I added the another stick same kind and all was well. The third stick it will not take so I left it out.

good call overeasy and elperro

[James-x]

use nortan goback or windows system restore

[rg6a]

Originally Posted by James-x

use nortan goback or windows system restore

He didn't (not that I read) say what version of 'Doze he's running. The blue screen infers 95-98, and he also didn't give the platform nor the Ram.

Here are a few hints, don't use wallpaper, keep the startup screen as Clean as possible. You don't need a shitload of shortcuts........drag them to Start and leave them there.

Don't Load everything that you don't use , if the task bar is full of icons......it's sapping your reserves and don't need them in Memory.

For all 'Doze disabled non command line peeps.......start-> run -> msconfig and look at start up and disable the Shit that you don't need.

Whole S-load of TIPS available online.........take a look...........the above musings were my own based on my early head banging daze and it's a wonder that my forehead isn't FLAT! ;-)

[Crazy1_79]

We can probally safely assume it is XP he is using.

[fubr]

I was thinking same thing crazy

[rg6a]

Originally Posted by Crazy1_79

We can probally safely assume it is XP he is using.

Well, have two notebooks running XP SP2 and two desktops running 98SE and never ever have seen the B.S.O.D. on XP.


He mentioned that he didn't have time to speak to MS, yet asks here without giving any details of the hardware/software and what he ran when the system cacked out and is an M.I.A. on this <T>hread.

Time for the Mod to DELETE this <T>hread!


PS IMHO, wanted to see his ASCII displayed here.

[Crazy1_79]

Originally Posted by rg6a

Well, have two notebooks running XP SP2 and two desktops running 98SE and never ever have seen the B.S.O.D. on XP.


He mentioned that he didn't have time to speak to MS, yet asks here without giving any details of the hardware/software and what he ran when the system cacked out and is an M.I.A. on this <T>hread.

Time for the Mod to DELETE this <T>hread!


PS IMHO, wanted to see his ASCII displayed here.

Never seen the BSOD on XP!! you are one lucky fellow! lol, it does happen I have seen it countless times. I am networking student and have had access to computers having no business running xp because of lack of processor and ram. you throw xp on these systems and they will run (more like crawl) but BSOD becomes more prevalant during standard operations

[OverEasy]

Sorry ! ! Fellows for being M.I.A. had other engagements thanks for all the replys.

Toshiba Satellite P25-S5262 Notebook

Intel P4 3.0GHz
Windows XP Pro SP 2
2x512MB PC2700 DDR Ram
Nvidia GeForce FX Go5200

Never before experienced BSOD myself. First time for everything I guess.
Solved the BSOD by replacing one of the sticks of ram. The good stick of ram wasn't even seeded properly.

I was looking at it for a close friend. He took it to the geek squad and they had
it for 2 months and told him the best thing to do would be to buy a new one. What a joke !
I figured it out (w/everyone's help) in 2 days. Would have been quicker if I had more time to work on it.

THANKS AGAIN OverEasy

[Pete391]

I have a computer that gets the dreaded BSOD all the time..And gives different numbers everytime....have tried different memory different processor....Same thing....Only way I can get it to run is in the bios turn the bus speed down and it runs fine...It has a pc chips M848 motherboard and an athlon xp2400 in it..The bus speed in bios when run correctly is 133mhz which it doubles it to 266mhz..I can turn it down to 100mhz and match the memory speed to 100mhz and it never gets the BSOD..Of course turning the bus speed down, instead of showing the correct 2400 cpu it shows as a 1500mhz with the bus speed turned down....And im sure it slows the computer down also doing it that way, but its the only way it will run without getting the BSOD all the time....