BSODs on Startup

bump

TClarke91 said:

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.

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

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.

TClarke91 said:

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.

Oh noo.. how do I do that?

TClarke91 said:

Oh noo.. how do I do that?

Run MDSCHED and follow the bouncing ball from there.

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

TClarke91 said:

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.

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