UNEXPECTED_KERNEL_MODE_TRAP (7f) nightmare

  • Thread starter Thread starter Giovanni
  • Start date Start date
G

Giovanni

Recently, my pc (SO win 2k, cpu Athlon Xp 1500+) suddenly restarts (like if
I push reset button),
also 2-3 times in hour.
Analysing .dmp file in \WINNT\Minidump\ directory, with WinDbg, I obtain
the follow informations:


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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 0, 0, 0}
[...]
Probably caused by : ntoskrnl.exe ( nt+6a0a9 )

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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
[...]
MODULE_NAME: nt
FAULTING_MODULE: 80400000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45ec3c9d
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 00000000 to 8046a0a9
STACK_TEXT:
804720b4 00000000 00000008 00000000 00000000 nt+0x6a0a9

STACK_COMMAND: kb
FOLLOWUP_IP:
nt+6a0a9
8046a0a9 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+6a0a9
FOLLOWUP_NAME: MachineOwner
MAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
-----------------------------------

Someone know where is the problem?

Thank you in advice for any ideas
Giovanni
 
Hi,

My first reaction - ASSUMING that absolutely NOTHING has been recently
changed software-wise on this machine - would be to be cast suspicion on
a hardware fault - RAM or processor/motherboard overheating being the
most likely culprits.

Have you run any SERIOUS hardware tests through this machine ?

Might I suggest you start with MemTest86 and do a thorough examination
of the RAM. This also gives you an opportunity to prove out whether the
problems are software related, since the normal OS is not in use
(MemTest86 uses a cut-down Linux kernel as it's environment)

Get back to us with more details,

Calvin.

http://nt4ref.zcm.com.au
 
would be to be cast suspicion on
a hardware fault - RAM or processor/motherboard overheating being the
most likely culprits.
Click to expand...

I reloaded motherboard BIOS, but nothing.
I tried to split my RAM banks, to use them one at time,
but the pc doesn't work well.

Microsft says about my error:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
BugCheck 7F, {8, 0, 0, 0}

that the probable causes are:
- cpu or ram or MB failure or kernel-driver problem.

Because the problem appeared for firs time after that I used Panda
Antirootkit utility,
I suppose that my problem is a kernel-driver.
(after runned Panda Antirootkit, my pc restarted and went ever on BSOD
(PAGE_FAULT_IN_NONPAGED_AREA
..... ntoskrnl.exe) before of the login window.
To overcome this issue I pushed F8 during pc
start up and choosed "last known good configuration" option.
In this way I was able to log into my account,
but the pc is became instable).

Do you know a way to test kernel-driver
and eventually identify a fault one?
I know only "verifier.exe" but I still didn't try it.
Have you run any SERIOUS hardware tests through this machine ?
Click to expand...

Not yet.
Might I suggest you start with MemTest86 and do a thorough examination
of the RAM. This also gives you an opportunity to prove out whether the
problems are software related, since the normal OS is not in use
(MemTest86 uses a cut-down Linux kernel as it's environment)
Click to expand...

Ok, I'll try with MemTest86.
Get back to us with more details,
Click to expand...

Thank you for all.
Giovanni
 
Giovanni said:
Recently, my pc (SO win 2k, cpu Athlon Xp 1500+) suddenly restarts (like if
I push reset button),
also 2-3 times in hour.
Analysing .dmp file in \WINNT\Minidump\ directory, with WinDbg, I obtain
the follow informations:


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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 0, 0, 0}
[...]
Probably caused by : ntoskrnl.exe ( nt+6a0a9 )

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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
[...]
MODULE_NAME: nt
FAULTING_MODULE: 80400000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45ec3c9d
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 00000000 to 8046a0a9
STACK_TEXT:
804720b4 00000000 00000008 00000000 00000000 nt+0x6a0a9

STACK_COMMAND: kb
FOLLOWUP_IP:
nt+6a0a9
8046a0a9 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+6a0a9
FOLLOWUP_NAME: MachineOwner
MAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
-----------------------------------

Someone know where is the problem?

Thank you in advice for any ideas
Giovanni
Click to expand...
1) Does this occur while the pc is booting up from cold?
2) Does this occur once the pc is booted?
3) If 2) does this occur only when the pc has been running for some time?
 
Back
Top