BSOD on Windows 8 developer Preview RRS feed

  • Question

  • Hi!

    I am using Windows 8 developer preview on my old LENOVO 3000 Y100 laptop. Suddenly it got BSOD. I have tried to analysis the minidump with Windbg.exe and it give the following result. Saying that Hardware problem. But I am not able to figure out the porblemetic hardware. Pls. help me to identify the problem.

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

    Loading Dump File [C:\Users\Samui\Desktop\111111-19671-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 8102 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 8102.109.x86fre.winmain_win8m3.110912-1733
    Machine Name:
    Kernel base = 0x810c3000 PsLoadedModuleList = 0x81256e38
    Debug session time: Fri Nov 11 22:51:44.184 2011 (UTC + 5:30)
    System Uptime: 0 days 0:17:45.613
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {ac9a2197, ff, 1, 811c120d}

    Probably caused by : hardware ( nt!KiDispatchInterrupt+7d )

    Followup: MachineOwner

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

    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: ac9a2197, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 811c120d, address which referenced memory

    Debugging Details:

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8126e484
    Unable to read MiSystemVaType memory at 81256060


    811c120d 83183c          sbb     dword ptr [eax],3Ch




    PROCESS_NAME:  System

    TRAP_FRAME:  85f86b80 -- (.trap 0xffffffff85f86b80)
    ErrCode = 00000002
    eax=ac9a2197 ebx=81241000 ecx=8293bd40 edx=000000d7 esi=00000000 edi=8293bd40
    eip=811c120d esp=85f86bf4 ebp=85f86c14 iopl=0         nv up di pl nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010006
    811c120d 83183c          sbb     dword ptr [eax],3Ch  ds:0023:ac9a2197=????????
    Resetting default scope

    811c120d 83183c          sbb     dword ptr [eax],3Ch

    LAST_CONTROL_TRANSFER:  from 811c01d0 to 811ab178

    85f86b60 811c01d0 0000000a ac9a2197 000000ff nt!KiBugCheck2
    85f86b60 811c120d 0000000a ac9a2197 000000ff nt!KiTrap0E+0x2c8
    85f86c00 8107f3fd 00000000 00000100 00000002 nt!KiDispatchInterrupt+0x7d
    85f86c14 8107f32c 00000000 85f86c50 85f86c50 hal!HalpDispatchSoftwareInterrupt+0x4f
    85f86c28 8107f5d5 85f86c50 dbb1daa2 05d7f6d6 hal!HalpInterruptCheckForSoftwareInterrupt+0x30
    85f86c40 8109cdb0 8107f11c 0000001c 85f86ce4 hal!HalEndSystemInterrupt+0xbb
    85f86c40 811ac251 8107f11c 0000001c 85f86ce4 hal!HalpTimerClockInterrupt+0x278
    85f86d6c 8138cc70 80023d60 25a28758 00000000 nt!KiXMMIZeroPagesNoSave+0x9
    85f86db0 811c19c1 8126f00a 80023d60 00000000 nt!PspSystemThreadStartup+0xa1
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    811c120d 83183c          sbb     dword ptr [eax],3Ch


    SYMBOL_NAME:  nt!KiDispatchInterrupt+7d

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  hardware


    MODULE_NAME: hardware



    Followup: MachineOwner




    Saturday, November 12, 2011 10:09 AM


  • Hey Utpal Samui,


    This problem shown above could be caused by one of the drivers that is being used or by a piece of hardware. Try visiting the site below to locate and download the latest drivers for your computer from Lenovo.
    Lenovo Support - Download Drivers and Software


    If a driver isn't able to install successfully, try using the compatibility troubleshooter to see if it can help the driver to install properly. The compatibility troubleshooter can be opened by:

    • Enter the Start screen
    • Move your mouse to the bottom left of the screen to expand the Charms section
    • Select Search
    • Type Compatibility
    • Click Settings in the right column
    • Click Run programs made for previous versions of Windows


    Then follow the prompts and direct the troubleshooter to the installer for your computer's driver. You will likely want to choose the choice for This program worked in earlier versions of Windows but won't install or run now when it is given if the latest driver is only applicable to a different version of Windows.



    If installing the latest drivers doesn't resolve this problem, try checking to see if a more recent version of your motherboard's BIOS is available from the link above. Instructions for how to update your motherboard's BIOS should be available in your user manual or on your computer's website.


    Modifying BIOS/ complementary metal oxide semiconductor (CMOS) or Unified Extensible Firmware Interface (UEFI) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS/UEFI settings can be solved. Modifications of the settings are at your own risk.


    Look forward to hearing back from you.

    Monday, November 14, 2011 10:20 PM