locked
bugcheck code help RRS feed

  • Question

  • hello i been geting this bug check code from my hp dv 6 2190

    OS Name Microsoft Windows 7 Home Premium
    Version 6.1.7600 Build 7600
    System Manufacturer Hewlett-Packard
    System Model HP Pavilion dv6 Notebook PC
    System Type x64-based PC
    Processor Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz, 1600 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date Hewlett-Packard F.1C, 5/17/2010
    SMBIOS Version 2.6
    Windows Directory C:\Windows
    System Directory C:\Windows\system32
    Boot Device \Device\HarddiskVolume1
    Locale United States
    Hardware Abstraction Layer Version = "6.1.7600.16385"
    Installed Physical Memory (RAM) 4.00 GB
    Total Physical Memory 3.99 GB
    Available Physical Memory 2.18 GB
    Total Virtual Memory 7.98 GB
    Available Virtual Memory 5.68 GB
    Page File Space 3.99 GB
    Page File C:\pagefile.sys

    here is the bsod dump

     

    + System

      - Provider

       [ Name]  Microsoft-Windows-Kernel-Power
       [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
     
       EventID 41
     
       Version 2
     
       Level 1
     
       Task 63
     
       Opcode 0
     
       Keywords 0x8000000000000002
     
      - TimeCreated

       [ SystemTime]  2010-08-04T23:55:52.186018800Z
     
       EventRecordID 11922
     
       Correlation
     
      - Execution

       [ ProcessID]  4
       [ ThreadID]  8
     
       Channel System
     
       Computer gezzey-PC
     
      - Security

       [ UserID]  S-1-5-18
     

    - EventData

      BugcheckCode 254
      BugcheckParameter1 0x8
      BugcheckParameter2 0x6
      BugcheckParameter3 0x5
      BugcheckParameter4 0xfffffa80074aac80
      SleepInProgress false
      PowerButtonTimestamp 0

    Saturday, August 14, 2010 6:19 AM

Answers

  • 254 = 0xFE = Bug Check 0xFE: BUGCODE_USB_DRIVER

    0x8 = Timeout issue with the USBport. Plug the USb device into an other usbport.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Leo Huang Monday, August 23, 2010 1:22 AM
    Saturday, August 14, 2010 4:08 PM
  • Hi, , I suggest you to test this issue in , Clean Boot, Safe Mode and Device Clean Boot to determine the possible cause.

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    As you have get the dump file, you can also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Support Service (CSS)

    via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

    • Marked as answer by Leo Huang Monday, August 23, 2010 1:22 AM
    Monday, August 16, 2010 8:10 AM

All replies

  • The computer has rebooted from a bugcheck. The bugcheck was: 0x000000fe (0x0000000000000008, 0x0000000000000006, 0x0000000000000005, 0xfffffa800709ac80). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080210-45770-01.

    Saturday, August 14, 2010 6:43 AM
  • 254 = 0xFE = Bug Check 0xFE: BUGCODE_USB_DRIVER

    0x8 = Timeout issue with the USBport. Plug the USb device into an other usbport.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Leo Huang Monday, August 23, 2010 1:22 AM
    Saturday, August 14, 2010 4:08 PM
  • Hi, , I suggest you to test this issue in , Clean Boot, Safe Mode and Device Clean Boot to determine the possible cause.

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    As you have get the dump file, you can also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Support Service (CSS)

    via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

    • Marked as answer by Leo Huang Monday, August 23, 2010 1:22 AM
    Monday, August 16, 2010 8:10 AM