Vista BSoD on Splash Screen

[eits]

is there any way around it? can i repair it? i think it's a problem with my hard drive because it's done it the last time i reformatted too.

it used to bsod a few times and then i'd be able to load up windows. now, i can't even get into windows.

 

[BlueAcolyte]

Vista is not supposed to BSoD. Period. Check your hard drive with some tool like chkdsk from the vista install cd or download the diagnostic tools from your HDD manufacturer.

Also run Memtest. The fact that you were BSoDing after even a new reinstall says that you have a hardware problem or your vista CD is fubar (not likely).

 

[eits]

i ran the diagnostic.... 0 errors found. i'm gonna run an extended test though.

regardless, i'm gonna get a new hdd and transfer everything.

 

[eits]

it freezes...

 

[zerogear]

Do you have 45nm CPU btw?

 

[eits]

yes... e8400

so, i ran extended tests on both hdd's... both had 0 errors.

i ran memtest, all passed.

here's the weird part... so, i unplugged the backup hdd and left the hdd that has windows on it and tried booting it up. it didn't even get to the splash screen... it gave me an error and told me that i needed to repair windows or reformat. so, i plugged in the back-up hdd and restarted and it loaded the windows splash and bsod'ed. i did this over and over again to make sure it wasn't a fluke. for some reason, i need both drives plugged in to load windows, but i don't have any windows files on the back-up drive and i didn't raid them or anything whenever i installed windows on the primary drive.

 

[novasatori]

sounds like you have the wrong hard drive selected in bios for boot HD

I had a similar problem, it seems to put the boot info on the primary boot drive as assigned by the bios, and not to the HD you select during install.

 

[eits]

Originally posted by: novasatori
sounds like you have the wrong hard drive selected in bios for boot HD

I had a similar problem, it seems to put the boot info on the primary boot drive as assigned by the bios, and not to the HD you select during install.

it's not an option when i don't have the other hdd plugged in. whatever hdd i plug in is what shows up in bios.

 

[eits]

this is bullshit... i come here for help with windows and no one comes to this section. i guarantee that there are tons of people in atot who could help me, but God forbid i put this thread somewhere else other than this ghost town of a forum section...

 

[clarkey01]

Originally posted by: eits
this is bullshit... i come here for help with windows and no one comes to this section. i guarantee that there are tons of people in atot who could help me, but God forbid i put this thread somewhere else other than this ghost town of a forum section...

I find that statement a bit offensive and a lack of respect for what guys here do..

You shouldn't be relying on forums anyhow (not completely) to solve all your issues, sure we're all here to help each other but take a chill pill and calm down.

It sounds like your HD is either wrong set to slave in the bios or maybe it's a boot sequence issue, please check.

 

[eits]

Originally posted by: clarkey01

Originally posted by: eits
this is bullshit... i come here for help with windows and no one comes to this section. i guarantee that there are tons of people in atot who could help me, but God forbid i put this thread somewhere else other than this ghost town of a forum section...

I find that statement a bit offensive and a lack of respect for what guys here do..

You shouldn't be relying on forums anyhow (not completely) to solve all your issues, sure we're all here to help each other but take a chill pill and calm down.

It sounds like your HD is either wrong set to slave in the bios or maybe it's a boot sequence issue, please check.

i did check. it doesn't really matter, considering how it's the only hard drive plugged in, so it will automatically be designated as the master drive

and i didn't mean to be offensive to any of the people who give advice here... it's just that there are many others who are experts with operating systems and they don't frequent this area. seriously, in 3 days, only 2 or 3 people have responded to this thread.

 

[pcslookout]

Originally posted by: clarkey01

Originally posted by: eits
this is bullshit... i come here for help with windows and no one comes to this section. i guarantee that there are tons of people in atot who could help me, but God forbid i put this thread somewhere else other than this ghost town of a forum section...

I find that statement a bit offensive and a lack of respect for what guys here do..

You shouldn't be relying on forums anyhow (not completely) to solve all your issues, sure we're all here to help each other but take a chill pill and calm down.

It sounds like your HD is either wrong set to slave in the bios or maybe it's a boot sequence issue, please check.

:thumbsup:

 

[brandonb]

What is the BSOD error? BSOD can mean anything.

I've had BSOD while booting, but it was related to a bug in the raid driver, which my motherboard supplier never fixed. I could not use raid on the computer with vista. That was a gigabyte mb.

Whats your MB? Bios version? Are you using raid? If you aren't, do you have RAID bios turned on in MB? (The MB Bios will allow you to turn on Raid BIOS).

 

[eits]

Originally posted by: brandonb
What is the BSOD error? BSOD can mean anything.

I've had BSOD while booting, but it was related to a bug in the raid driver, which my motherboard supplier never fixed. I could not use raid on the computer with vista. That was a gigabyte mb.

Whats your MB? Bios version? Are you using raid? If you aren't, do you have RAID bios turned on in MB? (The MB Bios will allow you to turn on Raid BIOS).

it flashes on the screen for a fraction of a second before it restarts.

i have a new gigabyte mobo, but that's inconsequential, considering how, a, i don't raid my hdds, and, b, how this bsod thing was an issue with my asus mobo too. it just wasn't as bad... i could eventually get into windows with enough luck and restarts. now, i can't.

 

[zerogear]

Originally posted by: eits
yes... e8400

so, i ran extended tests on both hdd's... both had 0 errors.

i ran memtest, all passed.

here's the weird part... so, i unplugged the backup hdd and left the hdd that has windows on it and tried booting it up. it didn't even get to the splash screen... it gave me an error and told me that i needed to repair windows or reformat. so, i plugged in the back-up hdd and restarted and it loaded the windows splash and bsod'ed. i did this over and over again to make sure it wasn't a fluke. for some reason, i need both drives plugged in to load windows, but i don't have any windows files on the back-up drive and i didn't raid them or anything whenever i installed windows on the primary drive.

I had this problem before, same on splash screen, but not sure if it applies to you or not. On my BIOS there is a Loadline Calibration option where you adjusts the CPU for vdroop, unfortunately 45nm CPUs can't really take constant voltage regulations, so it gives a BSOD after booting in windows. Not sure if it'll help, but it might be an issue.

 

[eits]

Originally posted by: zerogear

Originally posted by: eits
yes... e8400

so, i ran extended tests on both hdd's... both had 0 errors.

i ran memtest, all passed.

here's the weird part... so, i unplugged the backup hdd and left the hdd that has windows on it and tried booting it up. it didn't even get to the splash screen... it gave me an error and told me that i needed to repair windows or reformat. so, i plugged in the back-up hdd and restarted and it loaded the windows splash and bsod'ed. i did this over and over again to make sure it wasn't a fluke. for some reason, i need both drives plugged in to load windows, but i don't have any windows files on the back-up drive and i didn't raid them or anything whenever i installed windows on the primary drive.

I had this problem before, same on splash screen, but not sure if it applies to you or not. On my BIOS there is a Loadline Calibration option where you adjusts the CPU for vdroop, unfortunately 45nm CPUs can't really take constant voltage regulations, so it gives a BSOD after booting in windows. Not sure if it'll help, but it might be an issue.

i have no idea what vdroop is, but messing with the loadline calibration made the bsod show up a little later in the splash screen than before.

 

[brandonb]

Originally posted by: eits

it flashes on the screen for a fraction of a second before it restarts.

i have a new gigabyte mobo, but that's inconsequential, considering how, a, i don't raid my hdds, and, b, how this bsod thing was an issue with my asus mobo too. it just wasn't as bad... i could eventually get into windows with enough luck and restarts. now, i can't.

Are you running Vista 64 bit? Do you have more than 2 gigs RAM? You said this happens when you reinstall, and do you have the Vista SP1 disk or RTM disk? There's known problems with more than 2 gigs of RAM with original Vista 64 bit.

You should also turn off the auto restart when blue screen next time you format. But if you have the above scenario, remove memory until you hit 2 gigs and see if the problem goes away.

 

[SickBeast]

This sounds PSU related to me.

I had BSODs all over the place in Vista when I had a crappy PSU.

It could also be related to your graphics card drivers.

 

[eits]

Originally posted by: brandonb

Originally posted by: eits

it flashes on the screen for a fraction of a second before it restarts.

i have a new gigabyte mobo, but that's inconsequential, considering how, a, i don't raid my hdds, and, b, how this bsod thing was an issue with my asus mobo too. it just wasn't as bad... i could eventually get into windows with enough luck and restarts. now, i can't.

Are you running Vista 64 bit? Do you have more than 2 gigs RAM? You said this happens when you reinstall, and do you have the Vista SP1 disk or RTM disk? There's known problems with more than 2 gigs of RAM with original Vista 64 bit.

You should also turn off the auto restart when blue screen next time you format. But if you have the above scenario, remove memory until you hit 2 gigs and see if the problem goes away.

vista 32 bit. 4 gb ram.

i even tried using each stick by themselves in each ram slot just to make sure the memtest didn't bullshit me.