• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD during winXP boot logo (old P4 machine)

S

-Slacker-

Golden Member
Barebone PC, P4 @3Ghz, intel integrated graphics, 1 stick of 512mb ddr 400...

The problem is as described in the title^^^

The damn sucking thing will bsod during the windows boot screen.

Tried every booting mode, including safe mode, same crap.

I even tried replacing the memory stick with an older one, it didn't help - froze with bsod on the os boot screen again.

So ... I really don know how else to describe the problem. I'm stumped.
 
I'd try memtest86 for a few minutes just to see if errors start building up quickly. I've had memory I've swapped in be bad - don't rule out bad memory just because you swapped it. 🙂

If it's not the memory, it could either be a hard drive going bad, something in the OS missing or corrupt, or less likely mobo/cpu related.

I would pop in your XP cd, assuming you have one, and perform a repair install. Keep in mind you'll need to run windows update afterwards.

http://www.michaelstevenstech.com/XPrepairinstall.htm
 
Ah, well I don't have a memtest86 cd, so I'm going to go with the repair route first ... if that doesn't work, then I guess I'll have to get a memtest86 cd ... it would suck though, because I can't seem to find a retail version in my country, so I guess I'll have to order it from abroad and wait.

Anyway, thanks for the tips, the only other suggestions I've found on google involved some weird DOS fix thingie, which I don' think I have ( pre-windows ms-dos, I mean), and some other stuff about a "ndis.sys", which I have no idea how to access without being able to boot into windows...
 
It might be some chipset driver or something. I recently bought a mobo off of ebay, I installed windows and all, everything worked perfectly fine, until I installed the modo/chipset drivers downloaded the from mobo manufacturer's website (abit). BSOD, reboot, after couple of minutes of operation, BSOD, wouldn't even let me roll back. I reinstalled everything all over again, worked perfectly fine.

Did you update drivers? or maybe some other automatic update did that. Memory is the most sort after for BSODs but in my experience replacing them rarely fixed it. IMHO, try a fresh install...
 
-Slacker- said:
Ah, well I don't have a memtest86 cd, so I'm going to go with the repair route first ... if that doesn't work, then I guess I'll have to get a memtest86 cd ... it would suck though, because I can't seem to find a retail version in my country, so I guess I'll have to order it from abroad and wait.

Anyway, thanks for the tips, the only other suggestions I've found on google involved some weird DOS fix thingie, which I don' think I have ( pre-windows ms-dos, I mean), and some other stuff about a "ndis.sys", which I have no idea how to access without being able to boot into windows...
Click to expand...
memtest86 is free.

http://www.memtest86.com/

Just go to the downloads section and choose the first link for windows. Once you download the .iso, burn it to a cd using a program such as ImgBurn:

http://www.imgburn.com/index.php?act=download

Also - do you have the specific error from the BSOD?
 
^Nice ... I saw the $9.95 price tag and didn't bother to look around more so I missed "free download" link

But ... uh ... wow, this is kind of embarrassing ... So I just noticed/remembered that the rig doesn't have an optical unit anymore ... it's my brother's machine and all ...

Yeah ... Is there another way to solve this without the use of a cd? Provided that replacing the memory and maybe the HDD doesn't work - I'd like to try something less drastic, if possible ... nevermind the fact that if it comes to that, it would probably be better to just get a cheap, new rig, because my bro's little tin can isn't really worth investing any more money into ...

I also don't think that getting an optical unit will work ... I already ordered a new one a few months back, and it didn't work for some reason... not gonna risk wasting any more money for another one (E-IDE crap, can't even use it on my own sata rig)

So I'm going to stop rambling now
 
-Slacker- said:
^Nice ... I saw the $9.95 price tag and didn't bother to look around more so I missed "free download" link

But ... uh ... wow, this is kind of embarrassing ... So I just noticed/remembered that the rig doesn't have an optical unit anymore ... it's my brother's machine and all ...

Yeah ... Is there another way to solve this without the use of a cd? Provided that replacing the memory and maybe the HDD doesn't work - I'd like to try something less drastic, if possible ... nevermind the fact that if it comes to that, it would probably be better to just get a cheap, new rig, because my bro's little tin can isn't really worth investing any more money into ...

I also don't think that getting an optical unit will work ... I already ordered a new one a few months back, and it didn't work for some reason... not gonna risk wasting any more money for another one (E-IDE crap, can't even use it on my own sata rig)

So I'm going to stop rambling now
Click to expand...
Can you just borrow your brother's drive for the repair install? I'd be willing to bet $5 it'd fix your issues.

With IDE drives, you have to make sure the jumpers are set to cable select or master/slave depending on which plug you're using on the IDE cable. That might be why you had issues before.
 
goobernoodles said:
Can you just borrow your brother's drive for the repair install? I'd be willing to bet $5 it'd fix your issues.
Click to expand...

Nah, nah, it's my brother's rig that has both the bsod problem and the lack of an optical drive. Or if you meant that I should borrow him my dvdrw, that's not an option either - mine is sata, his is EIDE...

Hope I had that cleared out (I should have mentioned right form the start that it's my bro's rig that has the issue)

With IDE drives, you have to make sure the jumpers are set to cable select or master/slave depending on which plug you're using on the IDE cable. That might be why you had issues before.
Click to expand...

^That could actually be it, I don't remember checking the jumpers at all, I just assumed it should work right off the bat.


fffblackmage said:
You can also make a bootable USB thumb drive with memtest 86+ on it.
Click to expand...

Sweet! I had no idea usb sticks were useful without an OS 😀 I'll try that out too
 
-Slacker- said:
Sweet! I had no idea usb sticks were useful without an OS 😀 I'll try that out too
Click to expand...

Well technically if the stick is bootable, it has an OS, its just very BASIC. DOS is an operating system (Disk Operating System). Regardless, this is a good suggestion, however my first course of action would be to run chkdsk /r on the drive, this has had a tendency, in my experience, to fix a vast array of blue screens that occur during the bootup sequence. However, this of course would be easiest with a CDROM. You can use the 'r' repair using the recovery console option ( i always try this prior to doing the repair installation), or you could use a command prompt in the Windows PE found on hiren's disc.

If the CD is just not an option, Hiren's CAN be used from USB disk as well, try here

http://www.hiren.info/pages/bootcd-on-usb-disk
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top