BSOD , mostly using chrome or gaming

[Bartus49]

Hm I got no bsods till now I will send the next dmp here if one appears.

A big thanks )

 

[Bartus49]

So...here we go again


I had several BSODs, the dmp files are attached.

Some notes:
1) I shouldn't use Chrome, I'm using IE instead. Chrome appears to cause BSODs
2) I cant set the dmp-files to 64kb, there are 256kb instead. Thats why the dmpfiles are not the ones you asked for
3) I had an issue with that "watchdog.sys" when I was gaming. I tried to "repair" that by editing the time watchdog waits for the gpu-Drivers to respond, but I cant find the registryentry for that -.-
4) I had verifier enabled for at least 2 days, no BSOD appeared. So I disabled it.

Please help me

 

[Anshad Edavana]

Hi

The last couple of crashes clearly blames AMD video driver.

BugCheck FC, {ffffe00004047000, 8000000244e009e3, fffff80291eba1d0, 3}


*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][B]atikmdag.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchUnwaitFlipQueue+219 )

BugCheck 119, {7000000, ffffe0000421c000, ffffe00005fef8b0, ffffe000062a4010}


*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][B]atikmdag.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+e4b5 )

Please try the below steps.

1. Uninstall AMD video driver and related components in the proper way.

How-To Uninstall AMD Catalyst Drivers From A Windows Based System

2. Clean install latest WHQL version of the video driver.

Download this specific version - http://www2.ati.com/drivers/13-12_win7_win8_64_dd_ccc_whql.exe

While installing, choose custom and deselect everything except the AMD Display Driver. This is to avoid all other bloatwares like AMD catalyst Control Center etc which is sometime problematic.

View attachment 33627

 

[Bartus49]

Okay I'll try that

 

[Bartus49]

So I uninstalled the amd-stuff, only installed the Display Driver.
I had two BSODs since then. (Both when I was playing Hearthstone beta). F
Funny: On both I couldn't read the Infos on the blue Screen because they weren't readable. And only the second one created a dmp, saying something of DirectX?

If it's necessary to know for you: Those unreadable BSODs appear together with an awful Sound coming out of my Speakers.

 

[Bartus49]

And I wonder: Look at the attached pic. Is it normal to have those various Versions of that C++ stuff from Microsoft installed at the same time??

Further: There is an Intel Displaydriver installed...maybe this one collides with the AMD Driver? Is that possible? ^^

 

[Anshad Edavana]

New dump is also video related.

BugCheck 119, {800, 7, ffffe000038ec5f8, ffffe000038ed230}


Probably caused by : [B]dxgmms1.sys[/B] ( dxgmms1!VidSchiSendToExecutionQueue+c73b )



[B]VIDEO_SCHEDULER_INTERNAL_ERROR (119)[/B]
[B]The video scheduler has detected that fatal violation has occurred. This resulted[/B]
[B]in a condition that video scheduler can no longer progress. Any other values after[/B]
[B]parameter 1 must be individually examined according to the subtype.[/B]
Arguments:
Arg1: 0000000000000800, The subtype of the bugcheck:
Arg2: 0000000000000007
Arg3: ffffe000038ec5f8
Arg4: ffffe000038ed230

Since all the last crash dumps are directly related to the graphic subsystem, there is either a software or (more probably) a hardware error with the graphic part of your system. There is only a couple of third party drivers in the system and all of them, including the display driver is up to dated.

Please try the below steps.

1. Uninstall Intel Display driver to avoid possible conflicts.

2. Play different games and observe whether the issue only happens with a specific game. If that is the case, the problem should be with the game itself.

3. If the BSOD happens with all games or general usage (ie, chrome), switch the PCI-E slot.

4. If nothing helps, unplug the card and use on board VGA as a test. Stress the system by running apps which usually leads to the BSOD. I would recommend playing some HD videos and using Google Chrome and observe how the system works.

 

[Bartus49]

Okay I'll try that. Will take a while, I'll report results then

 

[Bartus49]

Hm okay...it seems to be Hearthstone!
Battlefield4, Assasins Creed 4, Diablo III, all running without Problems.
The BSODs appear with Chrome and Hearthstone. Hearthstone is beta, Google found a lot of People having similar issues, so I guess there is a Problem with that Battlenet launcher (beta, too) or/and Hearthstone. That's clearly something I/you/we cannot solve ^^

Thank you for your Patience


I don't know if you call yourself a member of a Religion that celebrates Christmas, but If it's the case: Merry Christmas!

 

[Bartus49]

I had the time to look deeper into the last dmp:




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: fffffffffff41324, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8030850333b, address which referenced memory
Debugging Details:
------------------

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff803087bd150
GetUlongFromAddress: unable to read from fffff803087bd208
fffffffffff41324
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimer2WithCollectionLockHeld+b7
fffff803`0850333b 498b13 mov rdx,qword ptr [r11]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: AV
PROCESS_NAME: Hearthstone.ex
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: ffffd00028727830 -- (.trap 0xffffd00028727830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8030850333b rsp=ffffd000287279c0 rbp=ffffe00005e73ce0
r8=ffffd00028727a88 r9=ffffd00028727ac8 r10=000000000000049c
r11=fffffffffff41324 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiInsertTimer2WithCollectionLockHeld+0xb7:
fffff803`0850333b 498b13 mov rdx,qword ptr [r11] ds:ffffffff`fff41324=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff803085c97e9 to fffff803085bdca0
STACK_TEXT:
ffffd000`287276e8 fffff803`085c97e9 : 00000000`0000000a ffffffff`fff41324 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`287276f0 fffff803`085c803a : 00000000`00000000 fffff803`0873be48 00000000`00000000 ffffd000`28727830 : nt!KiBugCheckDispatch+0x69
ffffd000`28727830 fffff803`0850333b : e00005e7`3cb0b26f 00000011`00100002 e00005e7`3cb0b26d ffffd000`28727a48 : nt!KiPageFault+0x23a
ffffd000`287279c0 fffff803`08502fe1 : ffffe000`05e73ce0 00000000`00000000 00000000`00000001 fffff803`0881a5d5 : nt!KiInsertTimer2WithCollectionLockHeld+0xb7
ffffd000`28727a10 fffff803`08502e32 : ffffe000`05e46800 fffff803`085c9400 00000000`00000000 ffffe000`05e73ce0 : nt!KeSetTimer2+0x175
ffffd000`28727a80 fffff803`085c94b3 : 00000000`00000008 00000000`010e1cf0 00000000`00000001 ffffd000`28727b00 : nt!ExpSetTimer2+0xfa
ffffd000`28727b00 00007ffa`ef197e2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04cde818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`ef197e2a

STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80308503333-fffff8030850333b)
fffff80308503330 c9 0f 84 *cf 00 00 00 ff c9 75 35 *49 8b 13 45 32 .........u5I..E2
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_stride
FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}




So it WAS Hearthstone. But I wonder, the dmp states a corruption of Memory? Is that a clue that my Memory is damaged (since I ran Memtest without Errors I dont think thats the case) or is it a failure from hearthstone.exe?

Again, I ran other games for a Long time, didnt cause any BSOD...

 

[Anshad Edavana]

Hi

memory_corruption simply means the code stored in an area of memory is altered or got corrupted. This can be caused either by a failing memory module or a bug in the code itself. In your case, only a specific game is causing issues so clearly it is a problem with the code. You can report about this bug to the developers and they may patch it in the next update.