+- Southperry.net (https://www.southperry.net)
+-- Forum: Maplers Helping Maplers (https://www.southperry.net/forumdisplay.php?fid=9)
+--- Forum: Technical Help (https://www.southperry.net/forumdisplay.php?fid=84)
+--- Thread: BSoD at startup (/showthread.php?tid=9822)
BSoD at startup - Kaasoljoyyx - 2009-04-02
- Windows XP
Had comp turned on this morning, came back home after work and had BSoD
Try restarting, windows tries to load, everytime it goes through the loading bar, i keep getting hit with another BSoD
Anyone got an idea of what to do? It's really pissing me off atm.
BSoD at startup - butterfλi - 2009-04-02
Loose memory/CPU/Graphics card?
Memory/CPU/Graphics card burned out?
Virus infected HD?
Conflicker'd? (lol)
That's all I can think of. Without knowing details, its hard to say for sure. If you're able to see the Window loading screen, I think the memory/CPU/Graphics card are in tact and that it's the HD. Could be (a) corrupted file(s) in the HD.
BSoD at startup - shouri - 2009-04-02
If you have access to another desktop look into a program called spinrite. You can get it via certain means. You'll have to burn an image of the program onto a CD using daemon tools or something. That program will help restore corrupted pieces of your HD (if that's the issue). A level 2 scan of spinrite should do.
Edit: If you become really interested in attempting this, I have an email with the links to obtaining spinrite (my friend decided to host a copy of it on his site). As well as a program for burning spinrite onto a CD. PM me your email address if you wish, and I'll gladly forward you the software.
BSoD at startup - MaxHudson - 2009-04-02
Just alittle thing to check if its not somthing simple. Take one RAM card out. Turn it on. if it BSoD's Then put that card back in and take the other one out. Bad RAM is a common cause for BSoD.
If that does not work, listen to the more advance answers.
BSoD at startup - KajitiSouls - 2009-04-02
As much as some of us hate sw.net, Chafalcar wrote a pretty good basic trouble-shooting guide for BSODs.
http://sleepywood.net/forum/showthread.php?t=1019848
And also, whenever you hit a BSOD, you should really pay attention to the error report info. Just telling us "there's a BSOD" doesn't mean much, and my only response without an error type/number would be "get a better computer".
BSoD at startup - Kaasoljoyyx - 2009-04-03
I'll take a look at that tomorrow at school but i had 2 diff bsod's
- First one was unique and had a very long msg, didn't really read it but it did mention things i usually didn't see on old bsod's
- Repeating ones are like half a screen long and i have the error code [0x________ code] or w/e. Not sure if that means anything or whatever