locked
BLUE SCREEN / HANG DURING START UP / STUCK AT LOADin BIOS. RRS feed

  • Question

  • I keep having startup problems. It hangs during loading BIOS.

    Below are the results from Windbg.

    I have the same version of usbuhci.sys referencing to this kb - http://support.microsoft.com/kb/976972

    I'm currently following some steps as described in http://support.microsoft.com/kb/974476/en-us

     

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c000001d, 90755f3f, 807e2b40, 0}

    Probably caused by : usbuhci.sys ( usbuhci!UhciCleanOutIsoch+15 )

    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: 90755f3f, The address that the exception occurred at
    Arg3: 807e2b40, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    usbuhci!UhciCleanOutIsoch+15
    90755f3f f00fc111        lock xadd dword ptr [ecx],edx

    TRAP_FRAME:  807e2b40 -- (.trap 0xffffffff807e2b40)
    ErrCode = 00000000
    eax=0807e003 ebx=807e2d00 ecx=0807e003 edx=0000c885 esi=8605afe0 edi=00000001
    eip=90755f3f esp=807e2bb4 ebp=807e2bb8 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    usbuhci!UhciCleanOutIsoch+0x15:
    90755f3f f00fc111        lock xadd dword ptr [ecx],edx ds:0023:0807e003=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  System

    CURRENT_IRQL:  5

    LAST_CONTROL_TRANSFER:  from 907567d3 to 90755f3f

    FAILED_INSTRUCTION_ADDRESS:
    usbuhci!UhciCleanOutIsoch+15
    90755f3f f00fc111        lock xadd dword ptr [ecx],edx

    STACK_TEXT: 
    807e2bb8 907567d3 8605afe0 00000001 85c98780 usbuhci!UhciCleanOutIsoch+0x15
    807e2bdc 9075e0d0 0105afe0 807e2bfc 9075e012 usbuhci!UhciInterruptService+0x13f
    807e2be8 9075e012 8605a0e0 86110008 807e2d20 USBPORT!MPf_InterruptService+0x1f
    807e2bfc 828837ad 85c98780 8605a028 807e2c28 USBPORT!USBPORT_InterruptService+0x38
    807e2bfc 8cab75d6 85c98780 8605a028 807e2c28 nt!KiInterruptDispatch+0x6d
    807e2c98 828c9695 868983e8 807cb800 807c6000 intelppm!C1Halt+0x4
    807e2d20 828ac00d 00000000 0000000e 00000000 nt!PoIdle+0x538
    807e2d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    usbuhci!UhciCleanOutIsoch+15
    90755f3f f00fc111        lock xadd dword ptr [ecx],edx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  usbuhci!UhciCleanOutIsoch+15

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: usbuhci

    IMAGE_NAME:  usbuhci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc86e

    FAILURE_BUCKET_ID:  0x8E_BAD_IP_usbuhci!UhciCleanOutIsoch+15

    BUCKET_ID:  0x8E_BAD_IP_usbuhci!UhciCleanOutIsoch+15

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

    Wednesday, August 18, 2010 4:09 PM

Answers

  • Couple of things :

    - Please remove any USB attached devices.
    - How many RAM modules are you running ? if more than one, please swap them and also try one module at a time. ~
    - Check for your BIOS update from the hardware vendor. (which is the vendor in your case) ?
    - See if you can disable serial port in BIOS settings and also it is not booting from any USB device in the boot sequence.

    Let me know once you have tried the above steps

    Cheers


    "Do it yourself, before you think someone else will" - Mani Babbar - 18.08.10
    • Marked as answer by Miya Yao Tuesday, August 31, 2010 2:43 AM
    Wednesday, August 18, 2010 9:51 PM

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

    check the RAM too, please.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Miya Yao Tuesday, August 31, 2010 2:43 AM
    Wednesday, August 18, 2010 10:45 PM

All replies

  • Couple of things :

    - Please remove any USB attached devices.
    - How many RAM modules are you running ? if more than one, please swap them and also try one module at a time. ~
    - Check for your BIOS update from the hardware vendor. (which is the vendor in your case) ?
    - See if you can disable serial port in BIOS settings and also it is not booting from any USB device in the boot sequence.

    Let me know once you have tried the above steps

    Cheers


    "Do it yourself, before you think someone else will" - Mani Babbar - 18.08.10
    • Marked as answer by Miya Yao Tuesday, August 31, 2010 2:43 AM
    Wednesday, August 18, 2010 9:51 PM

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

    check the RAM too, please.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Miya Yao Tuesday, August 31, 2010 2:43 AM
    Wednesday, August 18, 2010 10:45 PM
  • Hi,

    I reinstalled it 2 days ago, and it is still doing the crash but this time its only giving blank blue screen with no errors n not creating any dump file. Can you suggest me some ways to check the RAM. The usage of RAM is usually less 800MB if I'd look in task manager. Below are my comp specs.

    BIOS Version/Date American Megatrends Inc. 1402, 6/25/2009
    Installed Physical Memory (RAM) 3.00 GB
    System Type X86-based PC

    OS Name Microsoft Windows 7 Ultimate
    Version 6.1.7600 Build 7600
    Processor Pentium(R) Dual-Core  CPU E5300  @ 2.60GHz, 2600 Mhz, 2 Core(s), 2 Logical Processor(s)

    Motherboard : ASUS P5K SE

     

    THANKS

    Friday, September 3, 2010 11:00 PM