I got a BSOD while playing a game and now the computer is having issues booting up. I have managed to boot into safe mode and have created a Windows_NT6_BSOD_jcgriff2 zip file and I've also included my minidump. Please help me diagnose this problem.
OS: Windows 7 Ultimate x64 Retail
OS Age: 2 weeks
PC Age: 2 weeks
EDIT: I forgot to attach the files
OS: Windows 7 Ultimate x64 Retail
OS Age: 2 weeks
PC Age: 2 weeks
EDIT: I forgot to attach the files
STOP 0x00000019: BAD_POOL_HEADER Usual causes: Device driver
Offending driver per report
Atikmpag.sys
file descriptionProductname:
AMD driver
Company: Advanced Micro Devices, Inc.
File size: Various
Install current driver.
Code:
icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\082810-19000-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50 Debug session time: Fri Aug 27 19:34:48.152 2010 (GMT-4) System Uptime: 0 days 1:57:49.822 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffffa8004093690, fffffa8004093750, 40c0005} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+5a13 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000020, a pool block header size is corrupt. Arg2: fffffa8004093690, The pool entry we were looking for within the page. Arg3: fffffa8004093750, The next pool entry. Arg4: 00000000040c0005, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0 fffffa8004093690 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: ShippingPC-BmG CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002bab6d3 to fffff80002a78740 STACK_TEXT: fffff880`09576848 fffff800`02bab6d3 : 00000000`00000019 00000000`00000020 fffffa80`04093690 fffffa80`04093750 : nt!KeBugCheckEx fffff880`09576850 fffff880`03667a13 : fffff8a0`09098a70 fffff880`0487a0d1 00000000`5958504b fffffa80`05d25000 : nt!ExDeferredFreePool+0x12c4 fffff880`09576900 fffff8a0`09098a70 : fffff880`0487a0d1 00000000`5958504b fffffa80`05d25000 00000000`00000001 : atikmpag+0x5a13 fffff880`09576908 fffff880`0487a0d1 : 00000000`5958504b fffffa80`05d25000 00000000`00000001 fffff8a0`09098a70 : 0xfffff8a0`09098a70 fffff880`09576910 fffff880`048ad0f0 : fffffa80`05d25000 00000000`00000000 fffff880`095769b0 00000000`00000000 : dxgkrnl!DXGADAPTER::AcquireDdiSync+0xc9 fffff880`09576950 fffff880`048b1205 : fffff8a0`09098a70 00000000`00000000 00000000`00000000 fffff8a0`003ea000 : dxgkrnl!DXGADAPTER::DdiDestroyAllocation+0x50 fffff880`09576980 fffff880`048b054b : fffff8a0`003ea000 00000000`00000000 fffff8a0`00000000 00000000`00000003 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x83d fffff880`09576a70 fffff880`048b618f : 00000000`00000799 00000000`00000001 fffff880`09576ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3 fffff880`09576ac0 fffff960`001cb336 : 00000000`0956e7d0 ffffffff`c002df00 00000000`fff9e000 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b fffff880`09576bf0 fffff800`02a77993 : fffffa80`043dab60 00000000`00000f68 fffff880`00000000 fffffa80`03d4e2d0 : win32k!NtGdiDdDDICreateAllocation+0x12 fffff880`09576c20 00000000`7395119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0956e788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7395119a STACK_COMMAND: kb FOLLOWUP_IP: atikmpag+5a13 fffff880`03667a13 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: atikmpag+5a13 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e FAILURE_BUCKET_ID: X64_0x19_20_atikmpag+5a13 BUCKET_ID: X64_0x19_20_atikmpag+5a13 Followup: MachineOwner --------- Atikmpag.sys
file descriptionProductname:
AMD driver
Company: Advanced Micro Devices, Inc.
File size: Various
Install current driver.
I haven't installed any new drivers for a few days at least. Could it have been the game that triggered this problem? I've been playing it (Batman Arkham Asylum) for a few days and nothing has happened till now.
How do I identify the faulty drivers (probably HDD right?) and fix the problem accordingly?
Thanks
How do I identify the faulty drivers (probably HDD right?) and fix the problem accordingly?
Thanks
You read my post before I was done. Read again.
I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
�� Quote: Originally Posted by richc46 
You read my post before I was done. Read again.
I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
I'm not quite understanding if its the video card drivers (ATI) or the CPU drivers (AMD) since your post mentions both. Do I just try and install the newest drivers?
In case it is of any use, my graphics card is an ATI Radeon HD 4850 and my CPU is an AMD Athlon II X3 440 (3.0ghz).
Thanks for your help so far
The offending driver is part of the graphics driver package and can be updated from here - Graphics Drivers & Software
I have a list of drivers and the mfg.
This is the driver that has to be replaced
Atikmpag.sys
According to my information this is the Company that manufactures it
Productname: AMD driver
Company: Advanced Micro Devices, Inc.
If you do have additional drivers that are outdated, by all means update them too.
Thanks for the back up Reventon.
This is the driver that has to be replaced
Atikmpag.sys
According to my information this is the Company that manufactures it
Productname: AMD driver
Company: Advanced Micro Devices, Inc.
If you do have additional drivers that are outdated, by all means update them too.
Thanks for the back up Reventon.
I reinstalled the newest ATI drivers but the computer BSODed again overnight. Could it be a compatibility issue with some other hardware?
Upload the latest Minidump file from C:\Windows\Minidump please. You will have to copy it to the desktop before zipping it up.
Here's the output of a newer test
No minidump created for the overnight BSOD - and as far as I can see the last BSOD recorded elsewhere in the logs was the one that richc46 posted.
What this usually means is that the system failed so fast it did not have time to record the BSOD, representative of some form of hardware fault.
From earlier - this appears to be a graphics fault.
So, run a graphics stress test - Video Card - Stress Test with Furmark
What this usually means is that the system failed so fast it did not have time to record the BSOD, representative of some form of hardware fault.
From earlier - this appears to be a graphics fault.
So, run a graphics stress test - Video Card - Stress Test with Furmark
I ran the test and there were no issues/crashes. Does this mean there's nothing wrong with the GPU?
Also, I think I should mention that I did not actually see the latest BSOD. The computer was running overnight and when I checked in the morning it was unexpectedly off. Booting up revealed it had not shut down properly. Whether this was a BSOD is not certain but the symptoms seem to match what happened before.
Also, I think I should mention that I did not actually see the latest BSOD. The computer was running overnight and when I checked in the morning it was unexpectedly off. Booting up revealed it had not shut down properly. Whether this was a BSOD is not certain but the symptoms seem to match what happened before.
I tried playing the game again and after about 5 minutes I got another BSOD. This time the error code was "dxgmms1.sys"
I am attaching another one of those tests so you can see for yourselves. Playing the game seems to instigate these BSODs. Does this mean it's most likely a GPU problem?
I am attaching another one of those tests so you can see for yourselves. Playing the game seems to instigate these BSODs. Does this mean it's most likely a GPU problem?
I ran "sfc.exe /scannow" in an command prompt and I got this message:
Does that provide you with any clues?
Quote:
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
The dump seems to point to an ATI driver issue with handling the DMA request Windows made of it. Either the driver is at fault, or the hardware beneath it is (either way, there's no real way to say for sure). It looks like you have the August release of the ATI driver suite, which is probably the 10.8 catalyst suite. I'd try downloading and testing older versions in 10.x, as far back as you're comfortable, to see if any other versions make your system more stable. If not, you probably want to contact AMD/ATI to test that video card's hardware or the driver if you've already passed Prime95 and FurMark stress tests.
�� Quote: Originally Posted by jalebi I ran "sfc.exe /scannow" in an command prompt and I got this message:
Does that provide you with any clues?
Quote:
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
Is there any chance its a DirectX problem? (wouldn't this explain the fact that one of the BSODs was a dxgmms1.sys error?)
Anything is possible.
You can update DirectX here - Microsoft Download Center: Product Family Search Results
If that fails to fix it then this really does look like a hardware problem. Get the GPU replaced under warranty.
You can update DirectX here - Microsoft Download Center: Product Family Search Results
If that fails to fix it then this really does look like a hardware problem. Get the GPU replaced under warranty.
I played the game for a good hour right now and there were no problems. Maybe that sfc.exe thing fixed it. The fact that it was located in registry\machine\components makes me think it was very important. I am no expert though. If there are further issues, I will come back.
Thank you all very much. Its great to know there are people willing to help you with your computer problems.
Thank you all very much. Its great to know there are people willing to help you with your computer problems.
There is a new problem. I'm not sure if it has to do with crashes and debugging or whether it should be in a different forum, so tell me if I need to make a new thread.
I was playing Batman Arkham Asylum and, during a cutscene, the screen froze and the speakers produced a cackling sound. I could not ALT+TAB or CTRL+ALT+DELETE out of it so I shut down the computer manually. Since then I have been unable to restart it. Thinking it might be overheating, I've let the computer rest for an hour (this worked the last time it wouldnt restart) but it still doesnt boot up. All the components and fans seem to start up but nothing is displayed.
I thought it may be a faulty graphics card (this would have explained the previous problems) but then I realized that the computer doesnt make the usual beep when booting up nor does it make that beep to signal something is wrong. What is the issue? Could it be a power issue (not PSU but mains power)?
I was playing Batman Arkham Asylum and, during a cutscene, the screen froze and the speakers produced a cackling sound. I could not ALT+TAB or CTRL+ALT+DELETE out of it so I shut down the computer manually. Since then I have been unable to restart it. Thinking it might be overheating, I've let the computer rest for an hour (this worked the last time it wouldnt restart) but it still doesnt boot up. All the components and fans seem to start up but nothing is displayed.
I thought it may be a faulty graphics card (this would have explained the previous problems) but then I realized that the computer doesnt make the usual beep when booting up nor does it make that beep to signal something is wrong. What is the issue? Could it be a power issue (not PSU but mains power)?
I have reset the CMOS and the computer boots up again. What the hell is happening? Can a game really cause this much havoc? Is there some deeper problem that I am not spotting?
EDIT: Also, what does resetting the CMOS do exactly and how does it solve problems such as mine?
EDIT: Also, what does resetting the CMOS do exactly and how does it solve problems such as mine?
CMOS clears BIOS, not sure if a game could do that kind of damage.
�� Quote: Originally Posted by falafel CMOS clears BIOS, not sure if a game could do that kind of damage.
I think the real question here is why you have registered two accounts and are replying to your own posts under another username 
If you sit in front of a mirror you could have hours of fun conversation without going near the internet
If you sit in front of a mirror you could have hours of fun conversation without going near the internet
�� Quote: Originally Posted by z3r010 I think the real question here is why you have registered two accounts and are replying to your own posts under another username
If you sit in front of a mirror you could have hours of fun conversation without going near the internet
If you sit in front of a mirror you could have hours of fun conversation without going near the internet
�� Quote: Originally Posted by jalebi I thought it may be a faulty graphics card (this would have explained the previous problems) but then I realized that the computer doesnt make the usual beep when booting up nor does it make that beep to signal something is wrong. What is the issue? Could it be a power issue (not PSU but mains power)?
The Graphics Stress passing does not rule out a Graphics Card error either.
�� Quote: Originally Posted by reventon �� Quote: Originally Posted by jalebi I thought it may be a faulty graphics card (this would have explained the previous problems) but then I realized that the computer doesnt make the usual beep when booting up nor does it make that beep to signal something is wrong. What is the issue? Could it be a power issue (not PSU but mains power)?
The Graphics Stress passing does not rule out a Graphics Card error either.
CPU: AMD Athlon II x3 440
Resetting the CMOS battery clears the BIOS but how did that fix the problem (why wouldn't the computer boot up to begin with?)
After having seemingly solved my BSOD problems, I was browsing the internet when I received a sudden BSOD. I was unzipping a file in the background, but other than that, the computer was not doing anything resource-hungry.
The BSOD did not provide any indication of what was wrong, but I am no expert. I am attaching the important files in the hope that someone here knows what's wrong.
Could all these problems be solved through a simple reinstall of Windows 7?
The BSOD did not provide any indication of what was wrong, but I am no expert. I am attaching the important files in the hope that someone here knows what's wrong.
Could all these problems be solved through a simple reinstall of Windows 7?
I began posting your analysis in another thread, only to find that you have posted the same problem here. Your BSOD problem is in capable hands. Double posting a BSOD problem will only add to the difficulties.
I merged this and the other thread, here.
How do you know whose advice you should take?
I merged this and the other thread, here.
How do you know whose advice you should take?
Sorry for my lack of knowledge, but reading through the dates in what you put it, seems like those were the previous BSODs. Is there anything about the recent one (i.e. in the past hour)?
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 am going to discontinue work on this thread and have the two combined.
�� Quote: Originally Posted by richc46 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 am going to discontinue work on this thread and have the two combined.
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)
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: You can install MagicDisc if you need a replacement.
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 �������������������������������������������������������������������������������������� �� Quote: Originally Posted by Jonathan_King 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: You can install MagicDisc if you need a replacement.
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 �������������������������������������������������������������������������������������� 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.
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.
�� Quote: Originally Posted by jalebi 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 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:
Quote:
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:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
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
let us know if you need assistance with any of this
Ken J
According to ttran in this thread, analyzing the minidump revealed that it was driver verifier that was causing the BSODs with the following messages:
I let driver verifier run for 36 hours more and those BSODs did not occur again so maybe it was a fluke. (Note: this was before I adjusted my RAM settings).After the 36 hours, I turned off driver verifier and tried installing the audio drivers but it BSOD'd. The driver seems to be failing even without driver verifier stressing it.
Sorry for not mentioning this before but I forgot about it.
EDIT: I've just enabled driver verifier with the settings from your post zigzag. I'll let it run for a while. If it can find the cause of any problems its worth a try. BTW, what's the worst that can happen if driver verifier is left disabled and the drivers go on unchecked (but there are no BSODs)?
Quote:
A device driver has a bug that attempted to access free memory that it is not allowed to access.
Quote:
Page fault in a non page area
Sorry for not mentioning this before but I forgot about it.
EDIT: I've just enabled driver verifier with the settings from your post zigzag. I'll let it run for a while. If it can find the cause of any problems its worth a try. BTW, what's the worst that can happen if driver verifier is left disabled and the drivers go on unchecked (but there are no BSODs)?
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.
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.
�� Quote: Originally Posted by Jonathan_King 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.
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.
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?
It's likely, but who knows what else happened during that period. 
�� Quote: Originally Posted by Jonathan_King It's likely, but who knows what else happened during that period.
The fact that the driver is "mismanaging PTEs" suggests it's something to do with RAM but I don't know how I can test it.
�� Quote: Originally Posted by Jonathan_King Quote:
VIA VT1818 Audio Driver V6.0.1.8100 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit 7.
Không có nhận xét nào:
Đăng nhận xét