BSOD issue, seemingly random, error 0x0000000a

okamichan13 · 18 Aug 2015

Having increasing issues with BSODs, seemingly random, sometimes right after windows 7 loads, sometimes it takes a while. It doesn't seem to be connected to be happening while using any particular application far as I can tell as it happens even while the computer is idling. Usually it doesn't happen again after a restart.

Error on the blue screen is this - IRQL_NOT_LESS_OR_EQUAL but unsure what driver issue might be causing it. I do have a dump copy and following the instructions attached the dm log zipped. My first time posting here, though I've been a lurker for a while.

Any suggestions? This is a custom computer, about 2 years old that hasn't had any other issues other than a faulty hard drive about a year ago.

koolkat77 · 22 Aug 2015

Please remove McAfee and replace with MSE.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Clean boot

Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yussi\Downloads\JOSHEMILUKEMIKA-Tue_08_18_2015_235412_59\081815-16972-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`03c57000 PsLoadedModuleList = 0xfffff800`03e9c890
Debug session time: Wed Aug 19 09:28:41.398 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:47.271
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 1, fffff80003cd5096}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+c6 )

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: 0000000000000008, 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: fffff80003cd5096, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003f06100
GetUlongFromAddress: unable to read from fffff80003f061c0
 0000000000000008 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+c6
fffff800`03cd5096 4c894008        mov     qword ptr [rax+8],r8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff8800479f7c0 -- (.trap 0xfffff8800479f7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000001117c
rdx=fffffa8009cdf120 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003cd5096 rsp=fffff8800479f950 rbp=fffffa8009c9f120
 r8=fffffa800a24c7f0  r9=00000000000000d6 r10=fffff880009c0180
r11=00000000002f4a00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiInsertTimerTable+0xc6:
fffff800`03cd5096 4c894008        mov     qword ptr [rax+8],r8 ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003cc8fe9 to fffff80003cc9a40

STACK_TEXT:  
fffff880`0479f678 fffff800`03cc8fe9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0479f680 fffff800`03cc7c60 : fffffa80`06da2b00 fffff800`03dd7c5e fffff880`009cb040 fffffa80`0a24c7d0 : nt!KiBugCheckDispatch+0x69
fffff880`0479f7c0 fffff800`03cd5096 : 00000000`001cd010 fffff880`0479f9d0 0000000c`00000005 fffff880`030a5180 : nt!KiPageFault+0x260
fffff880`0479f950 fffff800`03ccd962 : fffffa80`0a24c710 fffffa80`0a24c710 00000000`00000000 00000000`00000001 : nt!KiInsertTimerTable+0xc6
fffff880`0479f9b0 fffff800`03ccfc12 : ffff0000`051e4b9d 00000000`000186a0 fffff880`000000d6 fffff880`11f37298 : nt!KiCommitThreadWait+0x332
fffff880`0479fa40 fffff800`03fbf23e : fffffa80`0a24c710 fffff800`03cc8d0a 00000000`00000000 00000000`000000d6 : nt!KeDelayExecutionThread+0x186
fffff880`0479fab0 fffff800`03cc8cd3 : 00000000`00000000 fffff880`0479fb60 ffffffff`fffe7960 000007fe`fb270b48 : nt!NtDelayExecution+0x59
fffff880`0479fae0 00000000`773edf1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00eaf698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773edf1a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+c6
fffff800`03cd5096 4c894008        mov     qword ptr [rax+8],r8

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5507a73c

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+c6

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+c6

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