Blue Screen (Win7HomePrem64bit) on HP TouchSmart 300-1223 (All-in-one)

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by BarryGreen, Jul 23, 2013.

  1. BarryGreen

    BarryGreen New Member

    Joined:
    Jul 23, 2013
    Messages:
    6
    Likes Received:
    0
    OK I have been having problems trying to get a client's computer fixed. It is an HP TouchSmart 300-1223 which is an all-in-one. First it was viruses. I got rid of 54 of them. Then the hard drive was bad. Just swapped it out and put a brand new install of Windows7 64-bit Home Premium. Did all of the updates. Official drivers. I even put a 4 gig stick of RAM in there instead of the 2 gig stick that ended up in there somehow. RAM was tested and working BTW. Ran like a rocket ship compared to before! Then I was testing to make sure everything was good to go so I could give this guy his computer back and it would be out of my life. Got a bluescreen with the Stop code 0x0000001E so I turned off the computer, unplugged the USB keyboard and mouse, and tried to turn it back on. Fans ran and everything but the screen was not on. I did the same turn everything off, unplug everything procedure as previously mentioned only I removed the stick of RAM, turned it on, and got the beeps saying it had no RAM. I re-seated the stick of RAM, plugged everything back in, and BAM! The screen had color again. No problems with it for a day and a half running it constantly (videos playing, surfing) so I felt confident giving the client his computer back. That was two days ago and he just told me he got the same exact error I just mentioned to you guys. He is going to bring it by again tomorrow morning. Would you guys please help me out in getting this issue resolved so that I can finally get it out of my life? This thing has been at my house on-and-off for a month now. Any help is MUCH and GREATLY appreciated [​IMG]

    (RAM is good, Hard drive is brand new, brand new installation of Windows 7 64-bit Home Premium and has been authenticated, did all possible updates) (I have no idea how to tell but I kind of think this is a video driver or power supply issue. I installed the Windows7 64-bit video driver from HP's site just in case anyone was curious and thinks that could be the issue) CAM00368_zps116fe1eb.

    I have been having problems with an HP TouchSmart 300-1223 First it was viruses. I got rid of 54 of them. Then the hard drive was bad. Just swapped it out and put a brand new install of Windows7 64-bit Home Premium and did all Windows updates and HP drivers. I even put a 4 gig stick of RAM instead of the previous 2 gig module. Both sticks of RAM were tested and working. After that it ran fine. Then I was testing to make sure everything was good to go so I could give this guy his computer back and finally be done with it. Got a bluescreen with the Stop code 0x0000001E so I turned off the computer, unplugged the USB keyboard and mouse, and tried to turn it back on. Fans ran and everything but the screen was not on. I did the same turn everything off, unplug everything procedure as previously mentioned only I removed the stick of RAM, turned it on, and got the beeps saying it had no RAM. I re-seated the stick of RAM, plugged everything back in, and BAM! The screen had color again. No problems with it for a day and a half running it constantly (videos playing, surfing) so I felt confident giving the client his computer back. That was two days ago and he just told me he got the same exact error I just mentioned to you guys. He is going to bring it by again tomorrow morning. Would you guys please help me out in getting this issue resolved so that I can finally get it out of my life? This thing has been at my house on-and-off for a month now. Any help is GREATLY appreciated [​IMG] CAM00368.
     
    #1 BarryGreen, Jul 23, 2013
    Last edited by a moderator: Jul 24, 2013
  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    When you get it back, please provide this information so we can provide a complete analysis: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html

    Info on the STOP 0x1E error here: BSOD Index - STOP 0x1E
    Please note the "Usual causes" section:
    Black screen errors are suggestive of video issues IME. I suggest these hardware diagnostics (they're freeware for personal use - but I'm uncertain of the conditions on them for business use): Hardware Diagnostics
     
  3. BarryGreen

    BarryGreen New Member

    Joined:
    Jul 23, 2013
    Messages:
    6
    Likes Received:
    0
    Attached are dump files and BSOD information taken from this computer -https://skydrive.live.com/redir?resid=D712C47B5CD2926!357&authkey=!AP0Nq70_fWtfsxo
     
    #3 BarryGreen, Jul 24, 2013
    Last edited: Jul 24, 2013
  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Sorry, but the download site wants me to give up personal info in order to download. I won't do that.
    Please upload it to someplace that'll let us download without providing personal info.
     
  5. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Only 124 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    No sign of memory dumps in the WER section of MSINFO32. While this isn't unusual, it is unusual to have memory dumps captured and no record of it in the WER. I'd expect that this behavior is most likely due to hardware issues.

    The memory dump itself looks to be a hardware issue also, but it's not 100% certain with this kind of memory dump (STOP 0x1E).

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :


    AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
    ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
    http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys

    amdsata.sys Fri Jul 17 14:59:51 2009 (4A60CA27)
    AMD AHCI 1.2 Device Driver (AMD chipset drivers) - may be from Windows Update
    http://www.carrona.org/drivers/driver.php?id=amdsata.sys

    amdxata.sys Fri Jul 17 14:59:54 2009 (4A60CA2A)
    AMD storage controller driver - usually from the Windows 7 DVD/may be from Windows Update
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys

    If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: http://www.carrona.org/hwdiag.html. Let us know the results and we can move on from there.



    Analysis:
    The following is for informational purposes only.
    Code:
    [FONT=lucida console]**************************Tue Jul 23 16:46:21.300 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072413-18891-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime:[B]0 days 4:41:41.814[/B]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
    BugCheck [B]1E, {0, 0, 0, 0}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#Example"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
    Arguments: 
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/FONT]
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    [FONT=lucida console]**************************Tue Jul 23 16:46:21.300 2013 (UTC - 4:00)**************************
    [COLOR=RED][B]AtiPcie.sys                 Tue May  5 11:00:22 2009 (4A005486)[/B][/COLOR]
    [COLOR=RED][B]amdsata.sys                 Fri Jul 17 14:59:51 2009 (4A60CA27)[/B][/COLOR]
    [COLOR=RED][B]amdxata.sys                 Fri Jul 17 14:59:54 2009 (4A60CA2A)[/B][/COLOR]
    PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
    amd_sata.sys                Fri Oct 12 05:48:36 2012 (5077E774)
    amd_xata.sys                Fri Oct 12 05:48:39 2012 (5077E777)
    MpFilter.sys                Fri Jun  7 19:01:11 2013 (51B26637)
    [/FONT]
    http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys
    http://www.carrona.org/drivers/driver.php?id=amdsata.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
     

Share This Page

Loading...