BSODs on Startup

[TClarke91]

bump

 

[H2SO4]

Nope

That would be because you edited your earlier post with the link to the full dump, rather than posting again

It's not a reprehensible thing to do, of course, but it meant I never got notified because there was no new post. I'm downloading the full dump now and I'll take a look ASAP.

 

[TClarke91]

oh, makes sense
I tried installing ati drivers and now my computer shuts off completely while booting..

 

[TClarke91]

Somehow I got back on my computer and I got this upon startup:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: c000021a
BCP1: FFFFF8A00006C260
BCP2: 0000000000000000
BCP3: FFFFFFFFC0000001
BCP4: 00000000001004C0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1






Oh and I'm running the 64 bit-OS.

 

[H2SO4]

Somehow I got back on my computer and I got this upon startup:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: c000021a
BCP1: FFFFF8A00006C260
BCP2: 0000000000000000
BCP3: FFFFFFFFC0000001
BCP4: 00000000001004C0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1






Oh and I'm running the 64 bit-OS.

That one (0xc00021a) is a Winlogon.exe crash. Another critical system process terminating, similar to your previous wininit.exe crash for which you uploaded the full dump.

I'm reasonably certain that your machine has hardware problems. The full dump suggests that wininit crashed because of a completely wild memory write supposedly in system code. That just doesn't happen on healthy hardware. Coupled with the fact that multiple reinstalls seem to produce a cornucopia of exotic crash types, there seems no particular reason to avoid suspecting the hardware.

You might want to start off with a few hours worth of memory diagnostics.

 

[TClarke91]

Oh noo.. how do I do that?

 

[H2SO4]

Oh noo.. how do I do that?

Run MDSCHED and follow the bouncing ball from there.

 

[TClarke91]

and I didn't have any problems until I upgraded til windows 7.. It was doing fine until I updated it.

 

[H2SO4]

and I didn't have any problems until I upgraded til windows 7.. It was doing fine until I updated it.

By itself, that info is interesting but inconclusive. There's no simple way for software to damage hardware (it's possible, but you really have to try hard). What a different software environment can sometimes do is to expose underlying flaws in hardware which were always present but never previously encountered because the old software operated differently.

Grandma would probably never notice that going into 6th causes the gearbox to launch itself vertically through the car roof at high speed.

 

[TClarke91]

Okay, I DID run the diagnostics tool a few hours ago and it came up with no problems detected. How would I run it for a few hours if it's

 

[TClarke91]

I've had no errors whatsoever.. Now I'm back in Vista and the computer's running like a charm.. hopefully it's not a hardware issue.. any other tests I can do from the Vista end?

 

[TClarke91]

bump

 

[H2SO4]

1) Make sure the motherboard is on the latest BIOS.

2) Check that nothing is over-clocked. Ensure adequate cooling.

3) Reinstall Win7 from scratch. Do not apply any updates. Do not connect it to the network. Do not install any apps, games, or utilities. Keep it physically disconnected from all networks.

4) Test what happens when you "use" the machine that way for a few hours. Play some Solitaire, author some documents in Notepad.exe... if there's a crash, your hardware is defective almost beyond any doubt.

5) If you don't experience any crashes at all for several days, start very carefully and slowly applying updates and installing your apps/games. If the crashing resumes at a certain point, at least you'll know the likely trigger - it's the thing you installed last.

 

[TClarke91]

I'm 100% nothing's overclocked. I thought there was a BIOS update but I had the most recent version.. My computer seemed the most stable when I didn't have automatic updates and did nothing, basically. I'll give it a shot this weekend. Thanks!

 

[H2SO4]

Could that make a huge difference?

Yes, potentially. Given your symptoms, it is very important that a BIOS update be attempted. That's what they'd do if you paid a shop to "fix it".

As long as you follow the instructions carefully, the update will go smoothly.

 

[TClarke91]

Also, since I got my ISO from MSDNAA, could it be that there was a missing component in the ISO file and it didn't do a perfect installation, causing the problems?

and yeah, I edited that post
bad habit..

 

[H2SO4]

Also, since I got my ISO from MSDNAA, could it be that there was a missing component in the ISO file and it didn't do a perfect installation, causing the problems?...

Highly unlikely. The incidence of "bad ISO" problems is vastly overstated. In truth, the error checking mechanisms would catch/repair/report minor problems during the download, and anything bigger would likely truncate the download anyway.

No harm in trying another download though. If you still get these wininit and winlogon crashes on a completely "vanilla" install, with an updated BIOS too.... hardware.

 

[TClarke91]

There isn't a BIOS update for my motherboard yet, but I think it's a problem with Toshiba.. Apparently lots of people with Toshiba's laptops are having this exact problem. I have a support case open with them though, so hopefully they'll figure something out soon.

 

[H2SO4]

There isn't a BIOS update for my motherboard yet, but I think it's a problem with Toshiba.. Apparently lots of people with Toshiba's laptops are having this exact problem. I have a support case open with them though, so hopefully they'll figure something out soon.

Good luck with it. I hope the BIOS update does the trick - as far as "hardware" fixes go, that's the cheapest option

 

[TClarke91]

Yeah, hopefully it works. Thanks for all the suggestions!