Crash dump

This time I selected ALL BUT "LOW RESOURCES SIMULATION" and one of the drivers .sys (NOT ICSAK.SYS). The system rebooted successfully but soon after the reboot, I got BSOD about icsak.sys and even with another driver enabled it's the same, appears to be the cause, but I'm not sure if it's the only one. Icsak.sys points to Zone Alarm, which I have installed, but I didn't have it in my previous installation and I still got the same crash codes.

Problem is that verifier-induced crash haven't left any crash dump file behind.

EasyPC said:

This time I selected ALL BUT "LOW RESOURCES SIMULATION" and one of the drivers .sys (NOT ICSAK.SYS). The system rebooted successfully but soon after the reboot, I got BSOD about icsak.sys and even with another driver enabled it's the same, appears to be the cause, but I'm not sure if it's the only one. Icsak.sys points to Zone Alarm, which I have installed, but I didn't have it in my previous installation and I still got the same crash codes.

Problem is that verifier-induced crash haven't left any crash dump file behind.

unninstall zone alarm and see if you still get the crash ?

best to try changing one thing at a time if possible

I uninstalled Zone Alarm and launched verifier on all drivers without a crash. However, with "LOW RESOURCES SIMULATION" I can't even log in, because I get the msg that there is not enough resources, so I went to safe mode and disabled verifier.

I'd also like to remind, that there wasn't zone alarm in the first installation and the crash dump codes were more or less the same as with the current installation.

Might not be the drivers after all... if that's the case, does it leave me any other option than to try changing CPU, RAM, RAM or MB and see what happens?

EasyPC said:

I uninstalled Zone Alarm and launched verifier on all drivers without a crash. However, with "LOW RESOURCES SIMULATION" I can't even log in, because I get the msg that there is not enough resources, so I went to safe mode and disabled verifier.

I'd also like to remind, that there wasn't zone alarm in the first installation and the crash dump codes were more or less the same as with the current installation.

Might not be the drivers after all... if that's the case, does it leave me any other option than to try changing CPU, RAM, RAM or MB and see what happens?

it might be useful to see another minidump without zone alarm installed

A new dump from recent crash:

EasyPC said:

A new dump from recent crash:

this ones memory corruption and firefox.exe is involved but this can mean everything or nothing

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 4b5f2, 2, 4bab1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000004b5f2, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000004bab1, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8000295632c to fffff800028c7f00

STACK_TEXT:
fffff880`0648ff88 fffff800`0295632c : 00000000`0000004e 00000000`00000099 00000000`0004b5f2 00000000`00000002 : nt!KeBugCheckEx
fffff880`0648ff90 fffff800`0287d545 : 00000000`00000000 fffff680`0039c818 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0648ffd0 fffff800`0289c493 : fffffa80`01f5a590 fffff700`000091d7 0000007f`fffffff8 fffff8a0`023a20e0 : nt! ?? ::FNODOBFM::`string'+0x322ac
fffff880`06490060 fffff800`0289aeee : fffffa80`01f5a590 fffffa80`00000008 fffff880`000078fc fffff800`00000005 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`06490910 fffff800`02baa7af : fffff8a0`018f2060 fffff880`06490c20 00000000`00000000 fffffa80`0312c330 : nt!MmCleanProcessAddressSpace+0x96
fffff880`06490960 fffff800`02b84b3d : 00000000`000000ff 00000000`00000001 00000000`7efaa000 fffffa80`01987b60 : nt!PspExitThread+0x47f
fffff880`06490a30 fffff800`028a4a43 : 00000000`00000100 fffffa80`0312c3f0 00000000`00000001 fffff800`028cf25d : nt!PsExitSpecialApc+0x1d
fffff880`06490a60 fffff800`028a4e80 : 00000000`00000000 fffff880`06490ae0 fffff800`02b85710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`06490ae0 fffff800`028c71f7 : fffffa80`0312c330 00000000`000001dc 00000000`00000000 fffffa80`019c9880 : nt!KiInitiateUserApc+0x70
fffff880`06490c20 00000000`74a62dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02feeca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a62dd9


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`0295632c cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiBadShareCount+4c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

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

maybe someone can spot something here I've missed but I am not convinced your last memtest used the right version so could you humor me and burn to CD and run from boot memtest86+ for at least 3 passes , I trust this version of memtest to give a true result :)

26 passes completed with no errors (memtest86+)

New crash dump included from January 31th. The computer crashed while I was listening to flash radio stream (using firefox).

EasyPC said:

26 passes completed with no errors (memtest86+)

New crash dump included from January 31th. The computer crashed while I was listening to flash radio stream (using firefox).

a different error this time

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004239624, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800205f820, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgkrnl+d624
fffff880`04239624 48895808 mov qword ptr [rax+8],rbx

CONTEXT: fffff8800205f820 -- (.cxr 0xfffff8800205f820)
rax=0000000000000000 rbx=fffff8a0021b53b0 rcx=fffff8a0000c28c0
rdx=fffff880009e8180 rsi=fffff880042453f8 rdi=fffff8a0021b53a0
rip=fffff88004239624 rsp=fffff88002060200 rbp=fffff880042453f8
r8=0000000000000004 r9=0000000000000080 r10=fffff8000284b000
r11=000000000000079c r12=0000000000000005 r13=0000000000000001
r14=0000000000000050 r15=fffff88002060658
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
dxgkrnl+0xd624:
fffff880`04239624 48895808 mov qword ptr [rax+8],rbx ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 00000000000007ff to fffff88004239624

STACK_TEXT:
fffff880`02060200 00000000`000007ff : 00000000`000000b0 fffff8a0`01be40b0 00000000`00000018 fffff8a0`021b5380 : dxgkrnl+0xd624
fffff880`02060208 00000000`000000b0 : fffff8a0`01be40b0 00000000`00000018 fffff8a0`021b5380 fffff880`042397c7 : 0x7ff
fffff880`02060210 fffff8a0`01be40b0 : 00000000`00000018 fffff8a0`021b5380 fffff880`042397c7 00000000`000007ff : 0xb0
fffff880`02060218 00000000`00000018 : fffff8a0`021b5380 fffff880`042397c7 00000000`000007ff fffff8a0`021b5380 : 0xfffff8a0`01be40b0
fffff880`02060220 fffff8a0`021b5380 : fffff880`042397c7 00000000`000007ff fffff8a0`021b5380 fffff8a0`021d3810 : 0x18
fffff880`02060228 fffff880`042397c7 : 00000000`000007ff fffff8a0`021b5380 fffff8a0`021d3810 00000000`00000000 : 0xfffff8a0`021b5380
fffff880`02060230 00000000`000007ff : fffff8a0`021b5380 fffff8a0`021d3810 00000000`00000000 00000000`00000001 : dxgkrnl+0xd7c7
fffff880`02060238 fffff8a0`021b5380 : fffff8a0`021d3810 00000000`00000000 00000000`00000001 fffff880`042396dc : 0x7ff
fffff880`02060240 fffff8a0`021d3810 : 00000000`00000000 00000000`00000001 fffff880`042396dc 00000000`00000001 : 0xfffff8a0`021b5380
fffff880`02060248 00000000`00000000 : 00000000`00000001 fffff880`042396dc 00000000`00000001 fffff8a0`021d37e0 : 0xfffff8a0`021d3810


FOLLOWUP_IP:
dxgkrnl+d624
fffff880`04239624 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgkrnl+d624

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e

STACK_COMMAND: .cxr 0xfffff8800205f820 ; kb

FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl+d624

BUCKET_ID: X64_0x3B_dxgkrnl+d624

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

can you run cpuz and check your timings are correct for all your ram ?

are you confident all your temperatures are within tolerances ?

you seem to have tried everything else and all your drivers are up to date my only idea at this moment is your suspicions may be correct and if it's possible you could try and get hold of another CPU just to try for a short time ?