Bad_pool_header

richc46 said:

I have just discovered that you have another theread with this same problem.
I am going to discontinue work on this thread and have the two combined.

I'm sorry for creating a new thread but I thought the problems were different from one another and didn't want to confuse anyone trying to solve the second one with details from the first.

Are there any more recent BSODs? The ATI one and the dxgmms1 one are a few days old and I think I solved them.

I checked the folder and saw a dump on Aug 30 at 19:16. I do not know how to open these files, let alone analyze them. Could somebody have a look? (the most recent zip is a few posts back)

Jonathan_King said:

I recommend uninstalling all traces of your current ATI drivers with Driver Sweeper. Then install these ones: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe

Test GPU temps: SpeedFan - Access temperature sensor in your computer

Test GFX card: Video Card - Stress Test with Furmark

Although you are having apparent GFX errors, it can't hurt to eliminate other causes. Please uninstall Daemon Tools Lite, and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v172-x64.exe

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 14:14:55.543 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:28.963
BugCheck A, {100060008, 7, 1, fffff80002a6b9c6}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+64401 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  QuickPar.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

You can install MagicDisc if you need a replacement.

Thank you for everthing. I have since reinstalled Windows 7 and this problem has not reoccured. I have stopped using Daemon Tools after reading that it can cause these sorts of problems.

Since the creation of this thread I have had several other BSODs, mostly, it seems, relating to RAM.

I had a BSOD that said there was a page fault in non paged area and another one that said a driver (apparently my audio driver) was mismanaging PTEs. The page fault error has not occured since I change my page file to 4093mb (one less than 4GB) - a solution I read about online. The issue with the driver, however, persists.

After creating this thread I discovered that my RAM setting in the BIOS did not match the manufacturer's recommended settings as a result of purchasing Intel optimized RAM for an AMD system. I manually changed the RAM's voltage and timings to match the manufacturer's specs. I ran memtest86+ for 12 hours and there were no errors so I assume my RAM is stable.

I thought fixing the RAM like this might have fixed the driver issue (seeing as mismanaging PTEs seems to be memory related), but it did not help. Without this driver my 5.1 speakers only work in a 2.1 configuration. For the moment, fortunately, I do not receive any unexpected BSODs - they only appear upon rebooting if I try to install the audio drivers. When the BSOD occurs, no minidump file is created so I have nothing to upload for now.

I have tried the drivers on the mobo disc and the slightly newer ones online, but they both resulted in BSODs. I have looked for older drivers online but they are not available. I even asked ASUS directly but they had no other drivers.

I uninstalled and reinstalled the Microsoft audio drivers before installing the manufacturer's ones but that did not work either.

Running Driver Sweeper does not reveal any remnants of other audio drivers that could get in the way.

My chipset and graphics drivers are all up to date.

The drivers worked on a previous Windows 7 install on the same computer and also work fine on another indentical computer to this one.

The driver in question is: VIA VT1818 Audio Driver V6.0.1.8100 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit 7.

This is a driver designed specifially for my mobo

If it is of any relevance, any BSODs other than the driver-related one occur while playing games.

jalebi said:

Since the creation of this thread I have had several other BSODs, mostly, it seems, relating to RAM.

I had a BSOD that said there was a page fault in non paged area and another one that said a driver (apparently my audio driver) was mismanaging PTEs. The page fault error has not occured since I change my page file to 4093mb (one less than 4GB) - a solution I read about online. The issue with the driver, however, persists.

After creating this thread I discovered that my RAM setting in the BIOS did not match the manufacturer's recommended settings as a result of purchasing Intel optimized RAM for an AMD system. I manually changed the RAM's voltage and timings to match the manufacturer's specs. I ran memtest86+ for 12 hours and there were no errors so I assume my RAM is stable.

I thought fixing the RAM like this might have fixed the driver issue (seeing as mismanaging PTEs seems to be memory related), but it did not help. Without this driver my 5.1 speakers only work in a 2.1 configuration. For the moment, fortunately, I do not receive any unexpected BSODs - they only appear upon rebooting if I try to install the audio drivers. When the BSOD occurs, no minidump file is created so I have nothing to upload for now.

If you believe it to be a driver and not hardware, ram, or OS there is something you can run called driver verifier

Beyond that, please run Verifier with these settings:

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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

let us know if you need assistance with any of this



Ken J

Jonathan_King said:

Driver verifier should not be enabled, unless you are testing for BSODs.

It will cause BSODs if it finds a bad driver. It should be disabled unless someone asks you to turn it on.

Since you are not having BSODs, it means that your drivers are not the fault. If you get more BSODs, it is almost certainly caused by hardware.

Yeah, that part I understand.

But surely if the BSOD always happens after installing a specific driver and then disappears after system restoring to the point before installation of that driver, then it is the driver that is at fault?