Constant Bsod's

Aceshighhhh · 01 Oct 2010

I have been getting blue screens pretty often ever since I first built this pc about a year ago. I've attempted to reinstall my OS and even tried running on Ubuntu for awhile but the bsod/crash returns in some form. It seems to happen more frequently whenever I'm playing any sort of video game e.g. WoW.

OS - Windows 7 Ultimate x64
Board - MSI 790FX-GD70
CPU - AMD Phenom II x4 955 @3.6GHz
RAM - Mushkin HP 8Gb (4 x 2Gb)
Video - SAPPHIRE ATI Radeon HD 4890
Sound - ASUS Xonar D2X
HD - 2x Western Digital VelociRaptor WD3000HLFS
PSU - KINGWIN Mach 1 ABT-700MA1S 700W
This is a full retail and the hardware is about a year old. I reinstalled this OS about 3 months ago

yowanvista · 01 Oct 2010

atikmdag.sys, part of your display driver is causing some BSOD
Update your display driver: ATI Radeon

Aceshighhhh · 01 Oct 2010

yowanvista said:

atikmdag.sys, part of your display driver is causing some BSOD
Update your display driver: ATI Radeon

I'v got that latest driver from the 15th but I still get the atikmdag.sys quite often

CarlTR6 · 01 Oct 2010

You have a fist full of dumps. I looked at six dumps.

All of your dumps point to hardware. They blame atikmdag.sys and Direct X most frequently.

To begin your troubleshooting, uninstall McAfee using this removal tool: Info > Tool. McAfee is known to cause crashes on some Win 7 systems. Down load and install MSE http://www.microsoft.com/security_essentials/ in its place and make sure Windows Firewall is turned on.

Stop error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usual causes are Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Stop error code 3B, SYSTEM_SERVICE_EXCEPTION - usual causes are System service, Device driver, graphics driver, ?memory.

Stop error code 124, WHEA_UNCORRECTABLE_ERROR - usual causes are Hardware, Incompatibility, May be driver corruption.

Normally when I encounter error code 124, I stop right there and list the things to try. However since I see only one error code 124 and all of the 50's, I will approach the other error codes first. In the usual causes for error code 50, you will see Anivirus listed. This is why I suggest you get rid of McAfee ASAP.

Code:

Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50
Debug session time: Fri Oct  1 07:01:05.113 2010 (GMT-4)
System Uptime: 0 days 0:00:19.409
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88008f01c48, 0, fffff88004a5f235, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+24e235 )

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

1: 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.
Arguments:
Arg1: fffff88008f01c48, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004a5f235, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb50e0
 fffff88008f01c48 

FAULTING_IP: 
atikmdag+24e235
fffff880`04a5f235 488b4620        mov     rax,qword ptr [rsi+20h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006abf000 -- (.trap 0xfffff88006abf000)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88006abf62c rbx=0000000000000000 rcx=fffff88006abf6ac
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004a5f235 rsp=fffff88006abf190 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff8a006fa8048
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
atikmdag+0x24e235:
fffff880`04a5f235 488b4620        mov     rax,qword ptr [rsi+20h] ds:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cfcbc2 to fffff80002c7ef00

STACK_TEXT:  
fffff880`06abee98 fffff800`02cfcbc2 : 00000000`00000050 fffff880`08f01c48 00000000`00000000 fffff880`06abf000 : nt!KeBugCheckEx
fffff880`06abeea0 fffff800`02c7cfee : 00000000`00000000 fffff880`06abf62c ffffd319`2b744d00 fffff880`06abf654 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`06abf000 fffff880`04a5f235 : fffff880`06abf62c 00000000`00000000 fffffa80`08f01c28 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`06abf190 fffff880`06abf62c : 00000000`00000000 fffffa80`08f01c28 00000000`00000001 fffff880`06abf680 : atikmdag+0x24e235
fffff880`06abf198 00000000`00000000 : fffffa80`08f01c28 00000000`00000001 fffff880`06abf680 fffff880`06abf690 : 0xfffff880`06abf62c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+24e235
fffff880`04a5f235 488b4620        mov     rax,qword ptr [rsi+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+24e235

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c75c7aa

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+24e235

BUCKET_ID:  X64_0x50_atikmdag+24e235

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

Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Fri Oct  1 00:15:30.014 2010 (GMT-4)
System Uptime: 0 days 1:03:41.700
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007dd3028, b669c000, 135}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007dd3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b669c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02d6ca88 fffff800`0320c903 : 00000000`00000124 00000000`00000000 fffffa80`07dd3028 00000000`b669c000 : nt!KeBugCheckEx
fffff880`02d6ca90 fffff800`02da3513 : 00000000`00000001 fffffa80`07e07ea0 00000000`00000000 fffffa80`07e07ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02d6cad0 fffff800`0320c5c8 : 00000000`00000728 fffffa80`07e07ea0 fffff880`02d6ce30 00000000`00822b00 : nt!WheaReportHwError+0x263
fffff880`02d6cb30 fffff800`0320bf1a : fffffa80`07e07ea0 fffff880`02d6ce30 fffffa80`07e07ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02d6cc80 fffff800`031ffe8f : 00000000`00358ae8 00000000`00000001 fffff880`02d6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02d6ccc0 fffff800`02c8d7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02d6ccf0 fffff800`02c8d613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02d6ce30 000007fe`fa967ce8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0264fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fa967ce8


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Fri Oct  1 03:40:55.682 2010 (GMT-4)
System Uptime: 0 days 0:08:36.367
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800403d38a, fffff8800a93e930, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchSubmitCommand+3a )

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

1: 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: fffff8800403d38a, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a93e930, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VidSchSubmitCommand+3a
fffff880`0403d38a 4c8b7e20        mov     r15,qword ptr [rsi+20h]

CONTEXT:  fffff8800a93e930 -- (.cxr 0xfffff8800a93e930)
rax=fffffa800796bd70 rbx=0000000000000200 rcx=fffff88008e0b210
rdx=fffff8800a93f500 rsi=00eef3fa00eef3fa rdi=0000000000000000
rip=fffff8800403d38a rsp=fffff8800a93f310 rbp=fffff8800a93f500
 r8=fffff880040116d0  r9=0000000000000000 r10=0000000000000000
r11=fffff88002b68120 r12=fffff88008e0b210 r13=0000000000000000
r14=ffffffffc000000d r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VidSchSubmitCommand+0x3a:
fffff880`0403d38a 4c8b7e20        mov     r15,qword ptr [rsi+20h] ds:002b:00eef3fa`00eef41a=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800403d38a

STACK_TEXT:  
fffff880`0a93f310 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x3a


FOLLOWUP_IP: 
dxgmms1!VidSchSubmitCommand+3a
fffff880`0403d38a 4c8b7e20        mov     r15,qword ptr [rsi+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchSubmitCommand+3a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff8800a93e930 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidSchSubmitCommand+3a

BUCKET_ID:  X64_0x3B_dxgmms1!VidSchSubmitCommand+3a

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

Older third party drivers can create problems with Win 7. I find two on your system that are slightly out of date. Update these drivers.

LGPBTDD.sys Wed Jul 01 14:47:52 2009 - LGPBTDD Driver is a driver file from Logitech Inc. belonging to Logitech GamePanel Software. Downloads. This driver was indicated in two dumps I looked at.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver for Realtek 8101E/8168/8169 PCI/PCIe Adapters. Realtek

If, after updating your drivers and uninstalling McAfee, you are still getting BSOD's, read the following on the 124 error. Upload any new dumps and we will begin checking hardware.

[2-Int] Stop 0x124 - what it means and what to try

CarlTR6 · 01 Oct 2010

Refresh your page. I have edited the post above.

Aceshighhhh · 01 Oct 2010

I've deleted the Mcafee anitvirus and Installed the latest driver for the Logitech GamePanel software. Although I'm a bit confused as to which driver I need to install as far as Realtek goes

CarlTR6 · 01 Oct 2010

Very good on uninstalling McAfee. I hope you used the uninstall tool; if not, you need to download it and run it to remove all traces McAfee. The driver you need to update is Rt64win7.sys. It is a network adapter driver. There is an updated version available. If you need help with it, let us know.