Windows 7: Need Help to figure out my BSOD problem.

emperact · 20 Jun 2010

Sound good. I am glad that my Eset NOD32 is still a trial, and I havent paid for it yet.

Tews · 20 Jun 2010

Quote: Originally Posted by emperact

Thank you guys, I'll try it right away. The funny thing is, that after I took the Memtest, I haven't had a BSOD since 2 days ago. But I will try the MSE.

Thats good news, however keep in mind that Memtest only tests your ram, it doesn't repair anything!

emperact · 20 Jun 2010

Quote: Originally Posted by Tews

Quote: Originally Posted by emperact

Thank you guys, I'll try it right away. The funny thing is, that after I took the Memtest, I haven't had a BSOD since 2 days ago. But I will try the MSE.

Thats good news, however keep in mind that Memtest only tests your ram, it doesn't repair anything!

I know that, but I still find it a little bit funny.

emperact · 20 Jun 2010

Done guys, I have now installed MSE, and my NOD32 is completly removed. I will write if anything happens, or if Eset was the problem. Thanks for all your time and help. :-)

richc46 · 20 Jun 2010

All that have contributed wish you luck.

CarlTR6 · 20 Jun 2010

I am delighted to hear that you have not a BSOD in a couple of day. I hope it runs smoothly for you. Please post back in you have any more trouble.

emperact · 20 Jun 2010

Well it was good as it lasted. Had a BSOD, but this is different. This time, my pc could only turn on, I only saw the Acer bootscreen, and it just loads forever, nothing happens. I had to make an ISO of my Windows 7 Disc, and put it onto a USB and use the repair function. It worked but here is the new minidump, wich i would like you to check out. Thanks.

CarlTR6 · 20 Jun 2010

Sorry to hear you are still having problems. I hoped it would be solved.

Quote:

STOP 0x00000019: BAD_POOL_HEADER

Usual causes: Device driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, 8321b378, 86fec1b5, b069c64d}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+664 )

Followup: MachineOwner

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: 00000003, the pool freelist is corrupt.
Arg2: 8321b378, the pool entry being checked.
Arg3: 86fec1b5, the read back flink freelist value (should be the same as 2).
Arg4: b069c64d, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 818ed30e to 8196d66e

STACK_TEXT:  
a6a47934 818ed30e 80000001 00000230 74536d4d nt!ExAllocatePoolWithTag+0x664
a6a47964 818e53cd 850ca718 0000008c 00000000 nt!MiAddViewsForSection+0x74
a6a47994 81a899cc 850ca718 0000008c 00000000 nt!MiAddViewsForSectionWithPfn+0x88
a6a47a08 81aa31cc 8475a940 85381c60 aac78d64 nt!MiPfPrepareReadList+0xd6
a6a47a38 81aa05b9 0000001d a8225ce8 00000005 nt!MmPrefetchPages+0x64
a6a47ab4 81a97a84 00a47ad4 00000000 00000000 nt!PfSnPrefetchSections+0x34c
a6a47c34 81a79380 aac78000 a6a47c64 a6a47c70 nt!PfSnPrefetchScenario+0x193
a6a47cc8 81a8507f 81a6acea 85373a18 a6a47d20 nt!PfSnBeginAppLaunch+0x382
a6a47cd8 81a7e5ab b0e6830e 00000000 00000000 nt!PfProcessCreateNotification+0x65
a6a47d20 818df159 00000000 77d164d8 00000001 nt!PspUserThreadStartup+0x113
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+664
8196d66e cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+664

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cac3

FAILURE_BUCKET_ID:  0x19_3_nt!ExAllocatePoolWithTag+664

BUCKET_ID:  0x19_3_nt!ExAllocatePoolWithTag+664

Followup: MachineOwner

This still a hardware error. You have run memtest and found no problems with your RAM. Recommend you run Driver Verifier: Using Driver Verifier to identify issues with Drivers

Quote:

Please follow these instructions in order to run it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

If you have any questions about this, please ask.

emperact · 21 Jun 2010

Thank you, I am trying out the driver verifier. It has been running since 09:30, no BSOD yet. I will post again, when something happens.

richc46 · 21 Jun 2010

If nothing happens run it at least for 36 hours.

Windows 7: Need Help to figure out my BSOD problem.

Need Help to figure out my BSOD problem. problems?