Windows 7: "Random" BSODS after installing new GFX related to ntoskrnl.exe

trickeh2k · 04 Oct 2011

Okey, last BSOD update. At least this is a new crash message.

**yowanvista** · 04 Oct 2011

ntkrnlmp.exe, which is a system file and will Never cause any problems unless it is triggered by an external component such as your Antivirus.

See if you get can an updated version of your BIOS

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff80002c8815e, address which referenced memory

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


WRITE_ADDRESS:  0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiCommitThreadWait+3fe
fffff800`02c8815e 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  fffff88007b0f8b0 -- (.trap 0xfffff88007b0f8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003c81168 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8003c81100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8815e rsp=fffff88007b0fa40 rbp=fffff88007b0fbb8
 r8=fffffa8006778388  r9=fffff88007b0fbb8 r10=fffff88002f63180
r11=fffff88002f63180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KiCommitThreadWait+0x3fe:
fffff800`02c8815e 48894108        mov     qword ptr [rcx+8],rax ds:2ab8:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c821e9 to fffff80002c82c40

STACK_TEXT:  
fffff880`07b0f768 fffff800`02c821e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07b0f770 fffff800`02c80e60 : fffffa80`00100001 00000000`00000000 00000000`00000001 fffffa80`03c81060 : nt!KiBugCheckDispatch+0x69
fffff880`07b0f8b0 fffff800`02c8815e : fffff8a0`00004d60 00000000`00000000 00000000`00f80028 fffffa80`039e0570 : nt!KiPageFault+0x260
fffff880`07b0fa40 fffff800`02c8a74f : 00000000`00000950 00000000`00000000 00000000`000000f9 fffff880`02f63180 : nt!KiCommitThreadWait+0x3fe
fffff880`07b0fad0 fffff800`02f7944e : fffff880`07b0fc00 fffff800`00000006 00000000`00000001 00000000`050ae000 : nt!KeWaitForSingleObject+0x19f
fffff880`07b0fb70 fffff800`02c81ed3 : fffffa80`03c81060 00000000`050ae650 fffff880`07b0fbb8 fffffa80`039f7140 : nt!NtWaitForSingleObject+0xde
fffff880`07b0fbe0 00000000`775f135a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`050ae018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775f135a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiCommitThreadWait+3fe
fffff800`02c8815e 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiCommitThreadWait+3fe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+3fe

BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+3fe

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

trickeh2k · 04 Oct 2011

Only virus scanner i have is Windows Defender and i have hard time thinking that would cause any troubles. Running the system now on the old ram since roughly and hour back. One thing that struck me though was that in the spd tab in cpu-z my old memory shows up in all four timing tables with the last one being 1600mhz although the memory runs at 1333mhz since my cpu doesnt support more. The new memory was the same kind, 1600mhz ddr3 ram running at 1333mhz on 9-9-9-24 timings but did not show anything in the last timing table column, that one was left out blank. Should this mean anything? Then again, for some reason cpu-z only seem to detect ram in slots two and three even though i run a 3x1GB and both bios and windows detects the full 3GB.

**yowanvista** · 05 Oct 2011

Quote: Originally Posted by trickeh2k

Only virus scanner i have is Windows Defender and i have hard time thinking that would cause any troubles. Running the system now on the old ram since roughly and hour back. One thing that struck me though was that in the spd tab in cpu-z my old memory shows up in all four timing tables with the last one being 1600mhz although the memory runs at 1333mhz since my cpu doesnt support more. The new memory was the same kind, 1600mhz ddr3 ram running at 1333mhz on 9-9-9-24 timings but did not show anything in the last timing table column, that one was left out blank. Should this mean anything? Then again, for some reason cpu-z only seem to detect ram in slots two and three even though i run a 3x1GB and both bios and windows detects the full 3GB.

Your RAM should not run at 1600Mhz unless it is being automatically adjusted by your BIOS, lower it back to 1333Mhz in your BIOS
Is your RAM fully compatible with your motherboard?

trickeh2k · 05 Oct 2011

No, it doesnt run at 1600mhz and never has. It runs at 1333mhz. My motherboard (ASUS P5Q3) supports it, but my CPU doesnt. System hasnt given me a BSOD yet, although i've made two reboots, keeping my fingers crossed

trickeh2k · 06 Oct 2011

Pointing towards the ram since the system now hasnt bsoded a single time since replacing the ram. It now has an uptime of 36+ hrs. Before, it had a uptime of 11 hours the most. And i've been using my system as normally as i can, watching youtube, surfing, playing battlefield 3 beta and other games, listening to music etc. Oh, sorted out the problem with youtube vidoes suddenly playing at 10fps tops, just uninstalled flash and voilá, problem solved

**yowanvista** · 06 Oct 2011

Quote: Originally Posted by trickeh2k

Pointing towards the ram since the system now hasnt bsoded a single time since replacing the ram. It now has an uptime of 36+ hrs. Before, it had a uptime of 11 hours the most. And i've been using my system as normally as i can, watching youtube, surfing, playing battlefield 3 beta and other games, listening to music etc. Oh, sorted out the problem with youtube vidoes suddenly playing at 10fps tops, just uninstalled flash and voilá, problem solved

Keep us update if any issues appear

trickeh2k · 06 Oct 2011

Will do sir

Someone suggested to retry the ram that seems to have been causing the bsods in different slots, using 1 & 3 instead of 2 & 4. Current setup is 1, 2, 3 using 3x1GB. New RAM was 2x4GB.

trickeh2k · 07 Oct 2011

Hmm twelve hours now back on the new ram and no bsod yet. Could a not properly fit ram in the slots be a cause for these bsods? Hasnt gone more then half a day but this was about the previous record uptime with the new ram. Anyone who can give some probable cause of the bsods that now (hopefully) magically wanished.

**yowanvista** · 08 Oct 2011

Quote: Originally Posted by trickeh2k

Hmm twelve hours now back on the new ram and no bsod yet. Could a not properly fit ram in the slots be a cause for these bsods? Hasnt gone more then half a day but this was about the previous record uptime with the new ram. Anyone who can give some probable cause of the bsods that now (hopefully) magically wanished.

Yes, unproperly seated RAM sticks can indeed cause issues.

Windows 7: "Random" BSODS after installing new GFX related to ntoskrnl.exe

"Random" BSODS after installing new GFX related to ntoskrnl.exe problems?