Solved Random BSODs on new system

[estebe1]

Hi all,

I bought a new office computer 3 days ago, installed W7 Home Premium x64 and it just won't work. I have received a number of 4 BSODs in 2 days which I am attaching copies of as instructed by the forum rules. All drivers seem to be up to date and have updated BIOS as well.

Any help much appreciated!

PS. Microsoft Security Essentials is installed

 

[FredeGail]

Hello estebe and welcome to Sevenforums.

I believe you've done a little mistake regarding the attachment. It seems like you've provided the .exe file for the jc software. If it's not too much to ask please read the tutorial once more. If you're having any questions just ask away.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Also if you don't understand the method on gathering your minidumps, or can't enable them or even find them-

Your Minidump content should be in the folder at the path C:\Windows\Minidump. If there's no files inside, make sure minidumps are enabled by -
Go to Start, then Run, then type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Next time you'd experience a BSOD, a dump is supposed to be generated. When it's generated, wrap it up in a zip and upload it.

I hope this helps,
Frederik.

 

[estebe1]

Sorry about that. Please find attached the dump files

 

[FredeGail]

Hello again Estebe, and no problem!

BSOD Analyse

I'd recommend you to check your memory sticks.

Looking at your bugcheck it's likely that a memory corruption event were there. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

If you're getting no errors, we'd proceed to Verifier.

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff880049da5d0, the pool entry being checked.
Arg3: ff00f880049da5d0, the read back flink freelist value (should be the same as 2).
Arg4: fffff880049da5d0, the read back blink freelist value (should be the same as 2).

Best Regards,
Frederik.

 

[estebe1]

Thank you Frederik,

Unfortunately you are right, I did a Memtest and after just 1 pass it showed a couple of thousand of errors. It's a single 4 gig stick but it;s under warranty so I'll have it sorted out. Thanx again!

 

[FredeGail]

Thank you Frederik,

Unfortunately you are right, I did a Memtest and after just 1 pass it showed a couple of thousand of errors. It's a single 4 gig stick but it;s under warranty so I'll have it sorted out. Thanx again!

If you can RMA it I'm very happy. I actually had the same bugcheck as you did a couple of years ago, and I also had all these errors with my sticks. By replacing them, I never had a BSOD since.
It's such a common causer!

All the best for you, Estebe. If you have any questions, just return here at Sevenforums. We're more than grateful to help you out in any way!

Cheers,
Frederik.