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

trickeh2k said:

Well, RAM seems to be ok. Ran seven passes with no errors. However, after running the driver verifier you suggested i wasnt even able to boot. I got a BSOD booting and was stuck in an infinate loop. Are theese BSODs logged somewhere so that I can show them? I disabled the verifier and im now back to "regular". Normally, id just do a fresh install of Windows since im quite sure that would do the trick, but when installing the new gfx card and memory i must have disconnected the dvd drive since its no longer recgnozied in windows or seem to be given any power. Im just looking for a solution but it seems that a fresh install is some what unavoidable.

Those dumps can be assessed via safemode

Okey, well this all seems to be too much a hassle. Im gonna do what I've should done from start and do a fresh install. I would like to thank you though for your assistance. I'll comeback in a few days, probably and hopefully to say that the bsods have disappeared. Take care!

Still related to Memory Management, the fault may be incorrect RAM/timings.
Your problem is definitively hardware related

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 000000030a001740
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880086dd470 -- (.trap 0xfffff880086dd470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000030a000000
rdx=0000000000000018 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f7f0d9 rsp=fffff880086dd600 rbp=fffff880086ddc60
 r8=fffff88002fd7f40  r9=fffff880086ddd70 r10=fffff880086dd4c0
r11=fffffa8003d55060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeUserModeCallback+0x109:
fffff800`02f7f0d9 8b9140170000    mov     edx,dword ptr [rcx+1740h] ds:d6d0:00000003`0a001740=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2662e to fffff80002c93640

STACK_TEXT:  
fffff880`086dd308 fffff800`02c2662e : 00000000`0000001a 00000000`00041287 00000003`0a001740 00000000`00000000 : nt!KeBugCheckEx
fffff880`086dd310 fffff800`02c9176e : 00000000`00000000 00000003`0a001740 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x46585
fffff880`086dd470 fffff800`02f7f0d9 : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffffa80`043d76a8 : nt!KiPageFault+0x16e
fffff880`086dd600 fffff960`00155838 : fffff880`0000002f fffff880`086dd6f0 fffff880`086ddb28 fffff900`c08878e0 : nt!KeUserModeCallback+0x109
fffff880`086dd680 fffff960`00121306 : 00000000`00000000 fffff880`086ddb28 fffffa80`05e3d901 fffff900`c08878a0 : win32k!fnHkINLPMSG+0x1c0
fffff880`086dd770 fffff960`0013e6aa : fffff900`c08878a0 fffff900`c08878a0 00000000`00000000 00000000`00000000 : win32k!xxxHkCallHook+0x236
fffff880`086dd800 fffff960`0013e24b : fffff900`c0723a03 fffff900`00000000 00000000`00000001 fffff880`086ddb28 : win32k!xxxCallHook2+0x452
fffff880`086dd970 fffff960`00179c83 : fffff900`c07237f0 fffff880`086ddb28 00000000`00000000 00000000`00000000 : win32k!xxxCallHook+0x37
fffff880`086dd9c0 fffff960`0017a025 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x53f
fffff880`086ddaa0 fffff960`00172ac7 : 00000000`0018ea00 fffffa80`03d55060 fffff880`02f63180 00000000`00000000 : win32k!xxxInternalGetMessage+0x35
fffff880`086ddae0 fffff800`02c928d3 : fffffa80`03d55060 00000000`0018e108 fffff880`086ddb88 00000000`74cd2450 : win32k!NtUserPeekMessage+0x77
fffff880`086ddb70 00000000`74d1fbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018e030 fffff800`02c8ac10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d1fbda
fffffa80`03d55060 00000000`00000006 : fffffa80`03d55068 fffffa80`03d55068 000000c9`12c773d8 000000c9`17a53078 : nt!KiCallUserMode
fffffa80`03d55068 fffffa80`03d55068 : fffffa80`03d55068 000000c9`12c773d8 000000c9`17a53078 fffff880`086ddd70 : 0x6
fffffa80`03d55070 fffffa80`03d55068 : 000000c9`12c773d8 000000c9`17a53078 fffff880`086ddd70 fffff880`086d5000 : 0xfffffa80`03d55068
fffffa80`03d55078 000000c9`12c773d8 : 000000c9`17a53078 fffff880`086ddd70 fffff880`086d5000 fffff880`086dccb0 : 0xfffffa80`03d55068
fffffa80`03d55080 000000c9`17a53078 : fffff880`086ddd70 fffff880`086d5000 fffff880`086dccb0 00000000`00000000 : 0xc9`12c773d8
fffffa80`03d55088 fffff880`086ddd70 : fffff880`086d5000 fffff880`086dccb0 00000000`00000000 00000001`00000101 : 0xc9`17a53078
fffffa80`03d55090 fffff880`086d5000 : fffff880`086dccb0 00000000`00000000 00000001`00000101 fffffa80`03d550b0 : 0xfffff880`086ddd70
fffffa80`03d55098 fffff880`086dccb0 : 00000000`00000000 00000001`00000101 fffffa80`03d550b0 fffffa80`03d550b0 : 0xfffff880`086d5000
fffffa80`03d550a0 00000000`00000000 : 00000001`00000101 fffffa80`03d550b0 fffffa80`03d550b0 fffffa80`03d550c0 : 0xfffff880`086dccb0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!fnHkINLPMSG+1c0
fffff960`00155838 89442438        mov     dword ptr [rsp+38h],eax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!fnHkINLPMSG+1c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79a73

FAILURE_BUCKET_ID:  X64_0x1a_41287_win32k!fnHkINLPMSG+1c0

BUCKET_ID:  X64_0x1a_41287_win32k!fnHkINLPMSG+1c0

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

Okey, how do you suggest i proceed now? I need to identify wich hardware is failing on me before sending in a RMA to my retailer. I ran the memtest for 8+ hours with 7 passes and no errors and stresstested my gfx card for one hour and nothing there either...

trickeh2k said:

Okey, how do you suggest i proceed now? I need to identify wich hardware is failing on me before sending in a RMA to my retailer. I ran the memtest for 8+ hours with 7 passes and no errors and stresstested my gfx card for one hour and nothing there either...

You may send your PC to the retailer for hardware checks

Well, no. If im to make an RMA application i must be sure of wich hardware is causing me bsods, otherwise i will just without a computer for a few weeks and then have to pay for the time they spent error searching plus shipping costs...

And yet another BSOD this night.

trickeh2k said:

Well, no. If im to make an RMA application i must be sure of wich hardware is causing me bsods, otherwise i will just without a computer for a few weeks and then have to pay for the time they spent error searching plus shipping costs...

Not all hardware defects can be detected using software, we are limited to CPU/RAM/GPU/PSU testing only. Other hardware should be tested manually

Thats all the hardware tests we have
Cpu Stress Test Prime95
Ram Test Memtest86
Nvidia Video Card Test OCCT
Video Card Stress Test Furmark
Seagate Hard Disk Check

Latest dumps do not indicate any specific cause

Okey, sad. So the BSODs really are random then? Running a memtest now for the GFX. Later tonight i will replace first the memory, run for at leats 48hrs and then the old gfx card.