Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: all drivers up-to date: still getting BSODs

15 Apr 2011   #21
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi DaTa82. I looked at all five of your dumps and I see five different error codes. all five indicate memory corruption and two directly blame memory corruption. Unfortunately, they do not give us the specific cause of the memory corruption. The five different error codes or bugcheck codes generally indicate a hardware or hardware related problem. You stated your BSOD's only seem to occur when you are running games. This plus the the fact the two dumps blamed the Windows system Direct X driver and one blamed your video driver lead me to believe you definitely have a conflict.

I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.

What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.

Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.

Let's see Driver Verifier shows and we will go from there.

Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03264e90
Debug session time: Fri Apr 15 13:10:51.220 2011 (GMT-4)
System Uptime: 0 days 0:27:01.796
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {31d0, 2, 1, fffff800030a81b3}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.

Debug session time: Fri Apr 15 10:37:08.132 2011 (GMT-4)
System Uptime: 0 days 0:16:35.709
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 10e3dc, 2, 12b3db}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.

Debug session time: Fri Apr 15 11:50:40.246 2011 (GMT-4)
System Uptime: 0 days 1:12:32.822
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00cfcd160, 0, fffff8800432d586, 0}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+636 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.

Debug session time: Fri Apr 15 17:55:52.633 2011 (GMT-4)
System Uptime: 0 days 0:35:12.210
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004e8754b, fffff8800adfc790, 0}

Probably caused by : atikmdag.sys ( atikmdag+3c254b )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004e8754b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800adfc790, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debug session time: Fri Apr 15 17:19:32.456 2011 (GMT-4)
System Uptime: 0 days 4:07:57.642
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880053d3d90, fffff880027916a8, fffff88002790f00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit.



My System SpecsSystem Spec
.
15 Apr 2011   #22
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Can you add your system specs?
In the lower left corner of any of your posts, "My System Specs".

This will help troubleshooting your system.
My System SpecsSystem Spec
16 Apr 2011   #23
DaTa82

Windows 7 x64
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post

I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.

What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.

Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.

Let's see Driver Verifier shows and we will go from there.

[/code]
Good morning!

Thank you so much for checking my files. I will enable Driver Verifier today and let you know the results.

Im not aware of any other security programs installed on my PC. I have only the standard, Windows built-in Firewall - no other specific firewall program installed

Regarding the CCC: I tried this several times during the last couple of months and unfortunately it didn't help.

I will update my systems specs as well but in the meantime I attach for your reference a screenshot from my order confirmation back from October last year, maybe it will help you already.

Guys, thanks againg for all the help and for all your replies, it's a really good forum and definetely worth to recommend!
My System SpecsSystem Spec
.

16 Apr 2011   #24
DaTa82

Windows 7 x64
 
 

I updated my system specs and will enable driver verifier now. Will keep ya posted and I'm looking forward to hearing from you!
My System SpecsSystem Spec
16 Apr 2011   #25
DaTa82

Windows 7 x64
 
 

So verifierer enabled: I got immediately 2 BSODs, both with the same code. Windows doesn't launch at all, I will try to launch it in safe mode. I have never seen this error code before

UPDATE: So I was not able to launch windows in normal mode. In Safe mode I disabled verifier. I will remove and update the realtek driver as according to the google results RTKVHD64.SYS is related to realtek. Once done I will enable verifier again...

UPDATE2: I disabled verifier, launched Windows, removed one of the Realtek drivers, restarted the computer, enabled driver verifier again: now it's running, I can surf on the net, no BSODs so far... Fingers crossed...?
My System SpecsSystem Spec
16 Apr 2011   #26
DaTa82

Windows 7 x64
 
 

while gaming I got a new BSOD. file attached
My System SpecsSystem Spec
16 Apr 2011   #27
DaTa82

Windows 7 x64
 
 

I let windows memory diagnostic run - no issues found...
My System SpecsSystem Spec
16 Apr 2011   #28
DaTa82

Windows 7 x64
 
 

maybe these screenshots are also useful
My System SpecsSystem Spec
16 Apr 2011   #29
Dapizz

Windows 7 Home Premium 64bit
 
 

Seeing what you said and reading through recent comments, there's a possibility that your graphics card can't take certain games. You could try going to Can You Run It? and seeing if your system is supposedly up to the games you can't play. It could be that you just can't play them.
My System SpecsSystem Spec
16 Apr 2011   #30
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The CPUZ info is very useful.

Windows memory test is not very good.

Use Memtest86+, follow the tutorial linked below.

When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+

Have you been checking your temperatures?

Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.


Any RAM that says 'Value' on it will likely cause you problems when stressed, like playing games.
My System SpecsSystem Spec
Reply

 all drivers up-to date: still getting BSODs




Thread Tools




Similar help and support threads
Thread Forum
how to Tell If Drivers are up to date
Hello so I bought a 2nd handf laptop reinstalled winxp and drivers I am not sure if I have done this correctly is there a program out there that can tell me all drivers are up to scratch or what else I need to download
Drivers
Slim Drivers says 22 out of date but Manage says 0!
Very recently my Western Digital Hard Disk was found to be failing, and a Samsung equivalent in specification was fitted by the repairer with the contents of the old being cloned to the new. Today I had an APC_INDEX_MISMATCH BSOD (but at this time I do not wish to pursue that). However, some...
Drivers
Random BSODs. Drivers are up to date and Hardware has gotten the A-OK
I reinstalled windows thinking the OS was eaten up by some magical virus. Updated all the drivers. I've Run Windows extended Memory diagnostic and tested the Hard drive both came back clear or errors. I am at my wits end. It is my first build only about 2 months old. BSOD started only this past...
BSOD Help and Support
Isatap adapters = I need up to date drivers
my device manager reports that isatap adapter, isatap adapter#2 and teredo tuneling adapter (Code 10), cant start because the drivers are out of date. Microsoft Support have suggested that I search forums to find out were I can get the required drivers and a method to fit them. Don't...
Drivers
No sound playing, yet all drivers are apparently up to date.
Hey guys. Here's the deal - I went out two weekends ago and got myself a brank spanking new ASUS desktop. It didn't come with an installed OS, so I got my hands on a copy of Windows 7 Build 7048 - the 64 bit version. I was a little worried about using it as my first OS (without installing XP or...
Sound & Audio
Source of up-to-date drivers
Even though Windows Update may fail to find them many newer drivers for Windows 7 are available for manual download at the Microsoft Update Catalog website if you manually search for them. You'll need to use IE to use the site. I found WDDM 1.1 drivers for my Intel G33 graphics that were newer...
Drivers


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:22.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App