Windows 7: Seemingly Random/Flash Related BSOD - 0x0000000a

hunte922 · 19 Sep 2013

0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff800026e250f)

I am getting constant BlueScreens. It might be related to the Flash Player - if I have it running (such as playing a YouTube video) and try to open any new page in another window, the computer freezes for a fifth of a second before returning to normal.
I do not know where to start debugging. I've already tried disabling hardware acceleration, but that doesn't work.
If it isn't flash related - I am still unable to find any culprit.

The BlueScreens started a month ago, and are progressively getting worse.
If you have any questions, I will answer them whenever I can.

Arc · 19 Sep 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

hunte922 · 19 Sep 2013

Attachment didn't upload correctly. It has been added.

Arc · 20 Sep 2013

Hello hunte922.

Update Etron USB 3.0 Extensible Host Controller drivers. Install the version 1.0.0.0115 dated 2012/09/20 from GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD3H-B3 (rev. 1.0) (Under Support and Download > Drivers > USB 3.0)

Disable Hardware Acceleration. Open a video in YouTube. When it is started, right click on the screen and choose "settings"

In the resulting window, uncheck the option for hardware acceleration, and then close the window.

Also, see these tutorials:

Let us know how it is going.
__________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800026e250f}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+ef )

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

0: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, 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: fffff800026e250f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000290f100
GetUlongFromAddress: unable to read from fffff8000290f1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+ef
fffff800`026e250f 488901          mov     qword ptr [rcx],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF800047DBFB0

TRAP_FRAME:  fffff800047d5960 -- (.trap 0xfffff800047d5960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000331a180923 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800026e250f rsp=fffff800047d5af0 rbp=000000000054e420
 r8=fffffa8012e54b10  r9=00000000000000c0 r10=0000000000000020
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KiTimerExpiration+0xef:
fffff800`026e250f 488901          mov     qword ptr [rcx],rax ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800026d7129 to fffff800026d7b80

STACK_TEXT:  
fffff800`047d5818 fffff800`026d7129 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`047d5820 fffff800`026d5da0 : fffff800`02852e80 fffff780`00000320 00000000`0054e420 000000ca`12daa64e : nt!KiBugCheckDispatch+0x69
fffff800`047d5960 fffff800`026e250f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0001aa49 : nt!KiPageFault+0x260
fffff800`047d5af0 fffff800`026e23c7 : 00000044`e97057c0 00000044`0054e420 00000044`e970571e 00000000`00000020 : nt!KiTimerExpiration+0xef
fffff800`047d5b90 fffff800`026cf88a : fffff800`02852e80 fffff800`02860cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`047d5c40 00000000`00000000 : fffff800`047d6000 fffff800`047d0000 fffff800`047d5c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+ef
fffff800`026e250f 488901          mov     qword ptr [rcx],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+ef

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+ef

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+ef

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

hunte922 · 20 Sep 2013

Updated the drivers and applied the settings. If I still have problems I'll post so; if not, after one whole week, I'll be sure to mark this thread as solved.

Thanks!

hunte922 · 24 Sep 2013

Stuttering is still happening. I should BlueScreen any time now.

hunte922 · 24 Sep 2013

I BlueScreened with the same code (0x0000000a) while running a memory check before booting. After that, Windows would not start without getting the same message. 2 faulty RAM modules were located and removed. After that, I had to use System Restore because one of my drivers had corrupted (it was causing BlueScreens on login). I'll check back in if the problems persist.

Arc · 25 Sep 2013

If you have identified the faulty RAM stick successfully, it is a good job

Let us know how the computer works after removing it

hunte922 · 29 Sep 2013

The RAM modules were all replaced with Corsair Vengeance Pro. Everything's working fine now.

Arc · 29 Sep 2013

Good news