BSOD playing WoW, 3 constant errors 0x0A, 0x50, 0x1E

Is there anyway I can do a clean reinstall with my preinstallrd version of win7 on lenovo laptop because my computer won't even boot to the desktop now

So I attempted a clean reinstall of windows 7 and now its not even letting me get through the setup of windows 7, it keeps giving me SYSTEM_SERVICE_EXCEPTION and BAD_POOL_CALLER

Code:

BugCheck 19, {3, fffffa8003929820, 53005700000000, 6c}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Code:

1: kd> !pool fffffa8003929820
GetPointerFromAddress: unable to read from fffff800030b0100
Pool page fffffa8003929820 region is GetUlongFromAddress: unable to read from fffff800030b01c0
Nonpaged pool
*fffffa8003929000 size:  920 previous size:    0  (Allocated) *.... (Protected)
		Owning component : Unknown (update pooltag.txt)

fffffa8003929920 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff8000301ea38
fffffa8003929920 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
fffffa8003929920 is freed (or corrupt) pool
Bad previous allocation size @fffffa8003929920, last size was 92

Code:

1: kd> !poolval fffffa8003929820
Pool page fffffa8003929820 region is Nonpaged pool

Validating Pool headers for pool page: fffffa8003929820

Pool page [ fffffa8003929000 ] is __inVALID.

Analyzing linked list...
[ fffffa8003929000 --> fffffa80039292d0 (size = 0x2d0 bytes)]: Corrupt region


Scanning for single bit errors...

None found

We are dealing with a corrupt pool free list, which is a linked list of free memory allocations, we can see that the block was allocated, although the corresponding pool tag is unknown. The Protected bit shows us that allocation being freed is the intentional one.

Code:

1: kd> k
Child-SP          RetAddr           Call Site
fffff880`076aa668 fffff800`02fab4b3 nt!KeBugCheckEx
fffff880`076aa670 fffff800`03174b7f nt!ExDeferredFreePool+0xa53
fffff880`076aa760 fffff800`0317499b nt!ObpAllocateObject+0x12f
fffff880`076aa7d0 fffff800`03140f64 nt!ObCreateObject+0xdb
fffff880`076aa840 fffff800`0314d5b3 nt!SepDuplicateToken+0xf4
fffff880`076aa8e0 fffff800`0313f107 nt!SeCopyClientToken+0x5f
fffff880`076aa970 fffff800`031552b9 nt!SepCreateClientSecurity+0xb7
fffff880`076aa9a0 fffff800`03155750 nt!SeCreateClientSecurity+0x59
fffff880`076aaa00 fffff800`0315bc37 nt!AlpcpCreateClientPort+0x464
fffff880`076aaab0 fffff800`02e77e93 nt!NtAlpcConnectPort+0x14b
fffff880`076aabb0 00000000`77961a5a nt!KiSystemServiceCopyEnd+0x13
00000000`00d8dc48 00000000`00000000 0x77961a5a

The Object Manager creates a new object, and then allocates the object a allocation of non-paged pool, the object never seems to be freed, so maybe the pool page became corrupt due to hardware.

-----------------------------------------------------------

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

I did a memtest with both chips errors came up on the first pass... tested ramstick 1 in both slots for 7 passes no errors.. test stick 2 in both slots... slot 1 went 6 passed then about 80000 errors came up and slot 2 3rd pass when I was letting it run came back with like 600000 errors lol,so this means I have bad RAM right?

It seems you have bad RAM, I would order a replacement, do the sticks still have warranty or any return policy remaining?

Noo my warranty ran out last year but I went to the store and spent 55$ on new RAM I put them in so ill see how the computer runs for a couple days and report back... thank you guys so much for the help =] I couldn't have done it without u guys

Welcome, hope everything runs fine for the next few days :)

So my computer worked completely fine... crashed again with 0x19 BAD_POOL_HEADER and now when it boots up it works for like 15 secs then freezes and loads a bunchbof red lines across the screen and stops working. =/

Whenever i try to enter startup repair the screen goes black then asks me again if I wana go to startup repair.. and it keeps doing that over and over