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:16 AM

Answers

  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Friday, August 20, 2010 9:55 AM
    Wednesday, August 18, 2010 7:09 AM

All replies

  • 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/
    Saturday, August 14, 2010 4:08 PM
  • Also, can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

    Sunday, August 15, 2010 12:21 PM
  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Friday, August 20, 2010 9:55 AM
    Wednesday, August 18, 2010 7:09 AM