TechSpot

Seeing BSOD every time I run computer

By n3demonic
Dec 24, 2008
Topic Status:
Not open for further replies.
  1. I am receiving BSOD's on my laptop all over the place. This has been going on ever since I got the computer. I've sent it into Gateway and supposedly got it back fixed (after three months) yet still is having the same problems. Here is my minidump file that I sent into windbg.

    Computer is a P6831FX with 3 gig of ram running intel core 2 duo T5450 @ 1.66 ghz / 32 bit OS Vista Service pack 1 Home premium

    I've put in 2 PNY 1gb ddr2 pc2-5300 stick in and still receive BSOD's. These two sticks work on my other laptop at the moment.

    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\n3demonic\Desktop\Mini122308-10.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*The symbols url that i can't add
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81c06000 PsLoadedModuleList = 0x81d1dc70
    Debug session time: Tue Dec 23 23:25:05.618 2008 (GMT-5)
    System Uptime: 0 days 0:02:05.538
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 81c7b005, 8ec8f6cc, 0}

    Probably caused by : memory_corruption ( nt!MiDeferredUnlockPages+26 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 81c7b005, The address that the exception occurred at
    Arg3: 8ec8f6cc, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    nt!MiDeferredUnlockPages+26
    81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016)

    TRAP_FRAME: 8ec8f6cc -- (.trap 0xffffffff8ec8f6cc)
    ErrCode = 00000000
    eax=00000002 ebx=00000000 ecx=00000000 edx=00000001 esi=00000000 edi=00000000
    eip=81c7b005 esp=8ec8f740 ebp=8ec8f79c iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!MiDeferredUnlockPages+0x26:
    81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016) [br=0]
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 10

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: svchost.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 81cf587d to 81c7b005

    STACK_TEXT:
    8ec8f79c 81cf587d 00000000 00000000 00001068 nt!MiDeferredUnlockPages+0x26
    8ec8f87c 81cf429c 9a71b000 9a71b000 8ec8f964 nt!MiFreePoolPages+0x10c
    8ec8f8e4 81e18c14 9a71b000 00000000 bbd7a941 nt!ExFreePoolWithTag+0x40e
    8ec8f930 81e33c4a 81c4ca01 bbd7a9d1 00000014 nt!PfpPfnPrioRequest+0x15b
    8ec8f9a0 81e3f1c9 00000000 81c4ca01 8ec8fd30 nt!PfQuerySuperfetchInformation+0xea
    8ec8fd4c 81c5da1a 0000004f 01e6f44c 00000014 nt!NtQuerySystemInformation+0x2201
    8ec8fd4c 77289a94 0000004f 01e6f44c 00000014 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    01e6f418 00000000 00000000 00000000 00000000 0x77289a94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiDeferredUnlockPages+26
    81c7b005 750f jne nt!MiDeferredUnlockPages+0x37 (81c7b016)

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiDeferredUnlockPages+26

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x8E_nt!MiDeferredUnlockPages+26

    BUCKET_ID: 0x8E_nt!MiDeferredUnlockPages+26

    Followup: MachineOwner
     
  2. n3demonic

    n3demonic TS Rookie Topic Starter

    Another dump file in windbg


    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\GW\Desktop\Mini122308-11.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*aurlican'tuse
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81c40000 PsLoadedModuleList = 0x81d57c70
    Debug session time: Tue Dec 23 23:33:06.095 2008 (GMT-5)
    System Uptime: 0 days 0:02:06.986
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c000001d, 81ce2b06, 9c94e7fc, 0}

    Unable to load image \SystemRoot\system32\DRIVERS\SiWinAcc.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SiWinAcc.sys
    *** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
    Probably caused by : SiWinAcc.sys ( SiWinAcc+1292 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c000001d, The exception code that was not handled
    Arg2: 81ce2b06, The address that the exception occurred at
    Arg3: 9c94e7fc, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

    FAULTING_IP:
    nt!MiRemoveAnyPage+3f
    81ce2b06 c744241801000000 mov dword ptr [esp+18h],1

    TRAP_FRAME: 9c94e7fc -- (.trap 0xffffffff9c94e7fc)
    ErrCode = 00000000
    eax=00000039 ebx=90e00000 ecx=40000039 edx=00000000 esi=993fc948 edi=ffffffff
    eip=81ce2b06 esp=9c94e870 ebp=9c94e8a0 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!MiRemoveAnyPage+0x3f:
    81ce2b06 c744241801000000 mov dword ptr [esp+18h],1 ss:0010:9c94e888={nt!CcMasterSpinLock (81d78000)}
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 11

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: WerFault.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 81ca6bc0 to 81ce2b06

    FAILED_INSTRUCTION_ADDRESS:
    nt!MiRemoveAnyPage+3f
    81ce2b06 c744241801000000 mov dword ptr [esp+18h],1

    STACK_TEXT:
    9c94e8a0 81ca6bc0 00000039 7837aa8d 993abdb8 nt!MiRemoveAnyPage+0x3f
    9c94e950 81c8cf5b a0bc0000 01a09a71 00000000 nt!MmCopyToCachedPage+0x2f7
    9c94e9e8 81c67786 993abdb8 01a09a71 9c94ea20 nt!CcMapAndCopy+0x210
    9c94ea70 8a289191 00000006 003774f7 00010000 nt!CcFastCopyWrite+0x283
    9c94eb94 82359adc 99375d70 013ff0ac 00010000 Ntfs!NtfsCopyWriteA+0x23e
    9c94ebc8 82359cab 00000004 00000000 993ff0a4 fltmgr!FltpPerformFastIoCall+0x22e
    9c94ebf4 8236bc30 0094ec18 99375d9c 82398b74 fltmgr!FltpPassThroughFastIo+0x7d
    9c94ec38 82398292 99375d70 9c94ece4 00010000 fltmgr!FltpFastIoWrite+0x146
    WARNING: Stack unwind information not available. Following frames may be wrong.
    9c94ec60 9c27c321 99375d70 9c94ece4 00010000 SiWinAcc+0x1292
    9c94ec9c 81e6754a 99375d70 9c94ece4 00010000 mfehidk+0x15321
    9c94ed38 81c97a1a 895af6f0 00000000 00000000 nt!NtWriteFile+0x34c
    9c94ed38 77159a94 895af6f0 00000000 00000000 nt!KiFastCallEntry+0x12a
    0008d1a4 00000000 00000000 00000000 00000000 0x77159a94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    SiWinAcc+1292
    82398292 ?? ???

    SYMBOL_STACK_INDEX: 8

    SYMBOL_NAME: SiWinAcc+1292

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: SiWinAcc

    IMAGE_NAME: SiWinAcc.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41868cbb

    FAILURE_BUCKET_ID: 0x8E_BAD_IP_SiWinAcc+1292

    BUCKET_ID: 0x8E_BAD_IP_SiWinAcc+1292

    Followup: MachineOwner
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.