The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    BLUE SCREEN on Media Center , help me ?

    Discussion in 'HP' started by tinto101, Oct 29, 2008.

  1. tinto101

    tinto101 Notebook Enthusiast

    Reputations:
    0
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    pavilion HP dv-6141 amd turion


    hi at all....

    after buy my portable pc HP, sometimes when i RECORD a tv movie
    with the windows XP media center, in random mode and random time
    it crash and BLUE SCREEN appars with this error:

    DRIVER_IRQL_LESS_OR_NOT

    stop: *** USBEHCI.SYS



    This error is frequently read in some FORUM on the web for more and
    more peolpe that have the Media Center of XP !

    i contact microsoft but it say to contact HP, hp say to me this act:



    - Update BIOS with the new F3.D

    - Update Media center with the rollup2

    - Update the Yuan Ec-300 tv tuner card HP with the new update

    - the KB918005 microsoft patch with the new driver EHCI.SYS


    i have to do this ....but NOTHING !!!!



    It crash in random mode when i record a tv movie always !!!

    Please help me... i am very disappoint to HP pc computer!

    best and i attend a solution for this big problem.
     
  2. S_P_Q_R

    S_P_Q_R Notebook Evangelist

    Reputations:
    43
    Messages:
    491
    Likes Received:
    0
    Trophy Points:
    30
    I've read on other sites this problem might be due to over heating, try lifting the back up so to get better ventilation or a Laptop cooler, if this works come back and post it so others will know how to fix this problem it in the future.
     
  3. tinto101

    tinto101 Notebook Enthusiast

    Reputations:
    0
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    great that correct!

    when the record stop ok the CPU is at 28 C

    and when the record CRASH the cpu is
    at 40 C !!!

    why ??? i have clear the fan ! all ok....
     
  4. tinto101

    tinto101 Notebook Enthusiast

    Reputations:
    0
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    but the minidump log say the is an problem
    to the driver USBEHCI.SYS ....

    but i have not preiferical or device USB !!!
    none !

    what is the problem ? help me....
     
  5. S_P_Q_R

    S_P_Q_R Notebook Evangelist

    Reputations:
    43
    Messages:
    491
    Likes Received:
    0
    Trophy Points:
    30
    Turn On Minidumps

    If you havn't already turned on minidumps, go to the Control Panel and follow this steps:
    System Icon
    Advanced Tab
    Startup and Recovery -> Settings
    Enable Write an Event to the system log
    Disable Automatically Restart
    Select the following debugging information:
    Small memory dump (64 Kb)
    Small Dump Directory : %SystemRoot%\Minidump
    Confirm all and restart the computer.
    Crash It

    Do whatever to make it crash. In my case it was leave the video encoding running overnight.
    Install Tools

    If you havn't got the windows debugging tools installed, then install the Microsoft Debugging Tools (Direct Link)
    Analyse The MiniDump

    To extract useful information out of the minidump file created:
    Open a command prompt (Start -> Run -> "cmd")
    cd \program files\debugging tools (Or wherever they are installed to)
    kd -z C:\WINDOWS\Minidump\Mini???????-??.dmp
    kd> .logopen c:\debuglog.txt
    kd> .sympath srv*c:\symbols* http://msdl.microsoft.com/download/symbols
    kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    You now have a debuglog.txt in c:\, open it in a text edit (Notepad?).
    Post Mortem

    Look for the MODULE_NAME and IMAGE_NAME headings. This is the program that caused the error. Sometimes when it's a device driver it means that that device is causing the BSOD and by disabling it or updating the driver your system will run stable. If you don't know what device that name relates to then Google it.
    (Under no circumstance ask me about your crash. I provide this information for free without any support.)

    If you can get anything useful out of that, it's all yours!
     
  6. tinto101

    tinto101 Notebook Enthusiast

    Reputations:
    0
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15
    please, if i send the minidump you read for me ?
     
  7. tinto101

    tinto101 Notebook Enthusiast

    Reputations:
    0
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    15