non-stop BSOD (likely triggered by playing Steam games?)

mintygoodness · Mar 29, 2014

Hi all,
I've been getting pretty frequent BSODs ever since updating to win 8.1.

As far as I can recall, they seem to have been triggered by playing Steam games (CounterStrike, to be precise). From then on, the BSODs will pop up even when I'm not in a game (and without Steam running in the background).

The BSODs are (sequentially):

1) DRIVER_VERIFIED_DETECTED_VIOLATION
2) IRQL_NOT_LESS_OR_EQUAL
3) A completely blue screen with little white squares
4) KERNEL_SECURITY_CHECK_FAILURE
5) IRQL_NOT_LESS_OR_EQUAL (frequent appearance)
6) DRIVER_IRQL_NOT_LESS_OR_EQUAL (avgloga.sys)
7) DRIVER_IRQL_NOT_LESS_OR_EQUAL (dxgmms1.sys)
8) NTSC_FILE_SYSTEM (Ntfs.sys)
9) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
10) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (dxgkrnl.sys)

I've removed AVG antivirus after BSOD #6, but they still keep coming.

So I did a clean install of 8.1, installed all the latest drivers (from the ASRock and AMD website) and hoped for the best.

It ran smoothly for a day or two, and that was when I thought I'd fire up Steam and give it a try.

Barely 10 secs into a game and the BSOD appeared:

'irql_not_less_or_equal'

I rebooted it and an hour later this guy came up:

'attempted execute of no execute memory'

Then the system ran with no hiccups for the rest of the night.

This morning I got a bit cold turkey, so I went into Steam again for about 30 mins. No BSOD!

I'm wondering, does any of you guys here know what is going on?

By the way, Here's the link to the minidump:

http://rapidshare.com/share/1CA853E4F999F56A3BAE695A8A065E12

I'm pretty sure I'd run into another BSOD again so I really hope I can get this fixed once and for all.

Any input is appreciated! Thanks!

lifetec · Mar 29, 2014

Firts could you upload your dumpfiles according to the instruction here http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html.
Please use option 1, this wil include additional data, like eventapp, msinfo etc.

As a start.

One of your 2 dumpfiles is a BugCheck A, {6, 7, 1, fffff80027b0281a} Probably caused by : atikmdag.sys ( atikmdag+37e8a )

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {6, 7, 1, fffff80027b0281a}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : [COLOR=#ff0000]atikmdag.sys[/COLOR] ( atikmdag+37e8a )
Followup: MachineOwner
---------
1: 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.
Arguments:
Arg1: 0000000000000006, memory referenced
Arg2: 0000000000000007, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80027b0281a, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80027d61150
GetUlongFromAddress: unable to read from fffff80027d61208
 0000000000000006 Nonpaged pool
CURRENT_IRQL:  7
FAULTING_IP: 
nt!ExInterlockedInsertTailList+36
fffff800`27b0281a f0480fba2b00    lock bts qword ptr [rbx],0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME:  ffffd00020dfbaa0 -- (.trap 0xffffd00020dfbaa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd00020dfbc68 rbx=0000000000000000 rcx=ffffe000005a9580
rdx=ffffe000005a3d80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80027b0281a rsp=ffffd00020dfbc30 rbp=0000000000000000
 r8=0000000000000006  r9=fffff800020fd000 r10=ffffe00000489f10
r11=ffffd00020dfbca8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!ExInterlockedInsertTailList+0x36:
fffff800`27b0281a f0480fba2b00    lock bts qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80027b6cbe9 to fffff80027b610a0
STACK_TEXT:  
ffffd000`20dfb958 fffff800`27b6cbe9 : 00000000`0000000a 00000000`00000006 00000000`00000007 00000000`00000001 : nt!KeBugCheckEx
ffffd000`20dfb960 fffff800`27b6b43a : 00000000`00000001 00000000`00000006 ffffd000`20dfbd00 ffffd000`20dfbaa0 : nt!KiBugCheckDispatch+0x69
ffffd000`20dfbaa0 fffff800`27b0281a : 00000000`00140001 00000000`00000000 00000007`00000030 fffff800`00000008 : nt!KiPageFault+0x23a
ffffd000`20dfbc30 fffff800`02134e8a : ffffd000`20dfbc70 ffffe000`0058be50 ffffe000`005a3d80 ffffe000`00463000 : nt!ExInterlockedInsertTailList+0x36
ffffd000`20dfbc70 ffffd000`20dfbc70 : ffffe000`0058be50 ffffe000`005a3d80 ffffe000`00463000 00000000`00000000 : atikmdag+0x37e8a
ffffd000`20dfbc78 ffffe000`0058be50 : ffffe000`005a3d80 ffffe000`00463000 00000000`00000000 00000000`00000000 : 0xffffd000`20dfbc70
ffffd000`20dfbc80 ffffe000`005a3d80 : ffffe000`00463000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe000`0058be50
ffffd000`20dfbc88 ffffe000`00463000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`021847be : 0xffffe000`005a3d80
ffffd000`20dfbc90 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff800`021847be 00000007`00000048 : 0xffffe000`00463000

STACK_COMMAND:  kb
FOLLOWUP_IP: 
atikmdag+37e8a
fffff800`02134e8a ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  atikmdag+37e8a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME:  atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  52a23f6f
FAILURE_BUCKET_ID:  [COLOR=#ff0000]AV_atikmdag+37e8a[/COLOR]
BUCKET_ID:  AV_atikmdag+37e8a
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:av_atikmdag+37e8a
FAILURE_ID_HASH:  {3e0c230b-3fc2-e200-e803-112623008934}
Followup: MachineOwner
---------

info from BSOD Index

IRQL_NOT_LESS_OR_EQUAL (a)

Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

The atikmdag.sys is the driver for your AMD graphic card, your drivers is from atikmdag fffff800`020fd000 fffff800`02ded000 Fri Dec 06 22:19:43 2013 (52a23f6f) 00ca856e None atikmdag.sys

Please update to the latest version

mintygoodness · Mar 29, 2014

Hi, the latest amd driver is a beta driver - should i download that?

Btw, I've just ran the SF Diagnostic Tool and uploaded the file.

Thanks!

lifetec · Mar 29, 2014

Hi, the latest amd driver is a beta driver - should i download that?

\

Yes, i have heard many good responses about the Betadriver.

mintygoodness · Mar 30, 2014

lifetec said:
Hi, the latest amd driver is a beta driver - should i download that?

Click to expand...

\

Yes, i have heard many good responses about the Betadriver.

Cool, I'll give that a try.

Thanks!

non-stop BSOD (likely triggered by playing Steam games?)

mintygoodness

New Member

My Computer

System One

lifetec

New Member

My Computer

System One

mintygoodness

New Member

My Computer

System One

lifetec

New Member

My Computer

System One

mintygoodness

New Member

My Computer

System One