BSOD ntoskrnl.exe could use some help plz

RustyNail · 21 Dec 2010

hi nice folks. Been getting bsods for awhile now. mostly this month. I've tried everything I know how and have since learned about to find the culprit and I give up.
win 7 ultimate x64 retail.
new box running with new hardware for a year now.
grphx card is not o/c'd.
no hardware was added recently.

installed windows debugger but having a heck of a time getting it to see the symbols path, either the online way or local dir way. Tried both.
ran memtest86 on all 4 sticks separately and different slots. Resutls were positive.
Of the 43 mini dmp files at least 2 were memory related.
ntoskrnl.exe is usually the gateway to the rest of the kernals and as such it's very generalized, or so it was explained to me recently. So, without a more definitive analysis, I'm stuck for now.
it's a 7f, 08 result code, meaning a double fault. typically mem or cpu but could be anything.
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002CD8DA2
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I'd gladly replace any hardware or .drv or .sys file or delete files/programs or update old drivers. Whatever you nice folks think is needed to get rid of the bsods. Just need to know which one.

attached zip files of forum's stated protocol for bsods help. Thanks much!!!!

Rusty

**Capt.Jack Sparrow** · 21 Dec 2010

Hello and Welcome !

Uninstall Zone Alarm and use the Removal Tool Download from Official Site and Install Microsoft Security Essentials.

Go to Start | CMD | Right Click and Run as administrator | SFC /SCANNOW

Update the Following Drivers:

Code:

uimx64.sys   Fri Sep 26 18:58:33 2008
hotcore3.sys Wed Jul 30 03:28:17 2008
adfs.SYS     Fri Jun 27 02:22:37 2008
000.fcl      Fri Sep 26 18:41:22 2008

Use this link for help in updating drivers: Driver Troubleshooting !! « Captain Debugger

Bugcheck:

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002c8f05f

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c88ca9 to fffff80002c89740

STACK_TEXT:  
fffff880`02f6ace8 fffff800`02c88ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f6acf0 fffff800`02c87172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f6ae30 fffff800`02c8f05f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f86f70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepAccessCheck+0x4f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02c87172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

Hope this helps,
Captain