1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

BSOD - Intermittent resetting - 0x7F, 0xD1.

Discussion in 'Windows 7' started by stevelee89, May 11, 2012.

Thread Status:
Not open for further replies.
Advertisement
  1. stevelee89

    stevelee89 Thread Starter

    Joined:
    May 11, 2012
    Messages:
    1
    Hi,

    I have an Advent Roma 2001, Celeron(R) Dual-Core CPU T3100 @ 1.90GHz, 3.00GB Ram. Have had this laptop for 11 months now and has had errors for 10. My mum uses this laptop to work from home. The laptop will reset itself 6/7 times a day for no reason - there is no pattern to what is causing the errors. I have used Win DBG (x86) to read the stop codes and it is throwing up ntkrnlpa.exe, livemouclass.sys and halmacpi.dll as the main culprits. I have also run an over night (8 pass) memory test and it returned with no errors. I have taken it into PC World and they (apparently) ran their tests and said that it wasn't a hardware issue. I have manually checked the drivers to ensure that they are all up to date which I believe that they are. Also tried verifier.exe to assess the situation with regards to the drivers and no crash. I've seemingly tried everything that I can think of ... can anybody help me out? Have Attached pictures of blue screen view and winDBG of latest BSOD is below.

    Cheers,
    Steve




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

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {b, 0, 0, 0}

    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
    Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )

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

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

    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: 0000000b, EXCEPTION_SEGMENT_NOT_PRESENT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

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

    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

    BUGCHECK_STR: 0x7f_b

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 82e8be1a to 82e55d2b

    STACK_TEXT:
    807e0cb4 82e8be1a badb0d00 00000000 00000000 nt!KiSystemFatalException+0xf
    807e0d24 00000000 0000000e 00000000 87111625 nt!KiIdleLoop+0x1a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiSystemFatalException+f
    82e55d2b c3 ret

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiSystemFatalException+f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4f5583be

    FAILURE_BUCKET_ID: 0x7f_b_nt!KiSystemFatalException+f

    BUCKET_ID: 0x7f_b_nt!KiSystemFatalException+f

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

    Attached Files:

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1052816