Solved all drivers up-to date: still getting BSODs

[CarlTR6]

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.

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.

 

[Dave76]

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.

 

[DaTa82]

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!

 

[DaTa82]

I updated my system specs and will enable driver verifier now. Will keep ya posted and I'm looking forward to hearing from you!

 

[DaTa82]

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...?

 

[DaTa82]

while gaming I got a new BSOD. file attached

 

[DaTa82]

I let windows memory diagnostic run - no issues found...

 

[DaTa82]

maybe these screenshots are also useful

 

[Dapizz]

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.

 

[Dave76]

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.

 

[DaTa82]

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.

Hi Dapizz,

this shouldn't be a problem - see a screenshot below for 1 of the games which use to cause BSODs during every battle

I let my PC build especially for gaming so everything should run smoothly. For working porpuses I have my company laptop, so this PC was meant for gaming

 

[DaTa82]

The CPUZ info is very useful.

Windows memory test is not very good.

Use 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.

Hi Dave!

Thank you for the comment. I ran memtest86+ about 1,5 month ago for a whole night - it didn't detect any issues. But I will give it a try again later on. I will make some photos of my BIOS and upload them soon

 

[DaTa82]

here are the first photos

 

[DaTa82]

and the rest

 

[DaTa82]

can I disable driver verifier already or shall this continue running in the background?

 

[DaTa82]

temperature seems to be also ok

 

[Dave76]

68C is high for an AMD, they usually run cool.

Let Driver Verifier run for a while longer, see if it can force a driver failure.

Running three RAM cards in a four card motherboard is not ideal, at best one of the cards will be in single channel mode.

Is this memory on your motherboard compatibility list?
A 3x2GB RAM set is usually for an Intel x58 motherboard. Sometimes they will run in an AMD board and sometimes will give you errors.
Best to get RAM specifically designed for AMD CPU/motherboards.

Do you have the Geil part number?


In your BIOS check voltages for:
Normal CPU Vcore
CPU NB VID control

It will be the same BIOS page as the first BIOS picture posted above, just scroll down to find this information.

If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.

With 6GB RAM you will need to make a small voltage increase to the CPU integrated memory controller, which is 'CPU NB VID control'.
Let us know the voltage setting and we can try adjusting.

 

[DaTa82]

In your BIOS check voltages for:
Normal CPU Vcore
CPU NB VID control



Thanks Dave! It's on my second screenshot, can you pelase check that?

 

[DaTa82]

Hm, I got fatal error while running prime test

 

[Dave76]

I see it now, it says 'Auto'.

If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.


When running Prime95 did you first go to the Advanced tab and select 'Round off checking'?

Did you check the stress.txt file?