Constant BSOD with all reqd info, i would appreciate some help.

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Michael Cahill, Apr 26, 2013.

  1. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    I have used this computer for a long time, reinstalled win7 several times. I have tooken out the memory and and put different ones in...and i still got the blue screen, so i put the old back in. I only tried moving the memory..i have no leads to think that is the problem but i figured it was worth a shot.

    any help on this issue is appreciated..below i have all the information required to make a bsod post.

    thanks
    cody
     

    Attached Files:

  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    There are enough signs here that that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

    Only 138 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).

    Your USB 3.0 Controller doesn't have drivers installed. Please visit the manufacturer's website to download and install the drivers for this device on your motherboard.

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

    If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.



    Analysis:
    The following is for informational purposes only.
    Code:
    [font=lucida console]**************************Fri Apr 26 17:13:01.324 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-27315-01.dmp]
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    [B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
    Built by: [B]7600[/B].16988.amd64fre.win7_gdr.120401-1505
    System Uptime:[B]0 days 0:03:44.620[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiDispatchException+1b9 )[/B]
    BugCheck [B]1E, {ffffffffc0000005, fffffa8005151bb0, 0, 7efa8000}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffa8005151bb0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000007efa8000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  MMLoadDrv.exe
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!KiDispatchException+1b9[/B]
      BIOS Version                  V17.10
      BIOS Release Date             03/23/2011
      Manufacturer                  MSI
      Product Name                  MS-7599
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Apr 26 17:08:20.654 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-25849-01.dmp]
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    [B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
    Built by: [B]7600[/B].16988.amd64fre.win7_gdr.120401-1505
    System Uptime:[B]0 days 0:02:43.590[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiDispatchException+1b9 )[/B]
    BugCheck [B]1E, {ffffffffc0000005, fffffa80050f2bb0, 0, 7efa8000}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffa80050f2bb0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000007efa8000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  MMLoadDrv.exe
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!KiDispatchException+1b9[/B]
      BIOS Version                  V17.10
      BIOS Release Date             03/23/2011
      Manufacturer                  MSI
      Product Name                  MS-7599
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Apr 26 16:44:04.820 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-24476-01.dmp]
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    [B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
    Built by: [B]7600[/B].16988.amd64fre.win7_gdr.120401-1505
    System Uptime:[B]0 days 0:02:12.802[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )[/B]
    BugCheck [B]1E, {ffffffffc0000096, fffff80002ab3a3a, 0, 0}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
    Arguments: 
    Arg1: ffffffffc0000096, The exception code that was not handled
    Arg2: fffff80002ab3a3a, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000096
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000096_nt!KeStackAttachProcess+1ba[/B]
      BIOS Version                  V17.10
      BIOS Release Date             03/23/2011
      Manufacturer                  MSI
      Product Name                  MS-7599
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Apr 26 16:41:10.530 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-27658-01.dmp]
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    [B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
    Built by: [B]7600[/B].16988.amd64fre.win7_gdr.120401-1505
    System Uptime:[B]0 days 0:05:05.872[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiDispatchException+1b9 )[/B]
    BugCheck [B]1E, {ffffffffc0000005, fffffa8008306bb0, 0, 7efa8000}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffa8008306bb0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000007efa8000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!KiDispatchException+1b9[/B]
      BIOS Version                  V17.10
      BIOS Release Date             03/23/2011
      Manufacturer                  MSI
      Product Name                  MS-7599
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Apr 26 14:13:27.012 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042613-31886-01.dmp]
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    [B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
    Built by: [B]7600[/B].16988.amd64fre.win7_gdr.120401-1505
    System Uptime:[B]0 days 0:40:35.354[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )[/B]
    BugCheck [B]1E, {ffffffffc0000005, fffff80002aab117, 0, 7efa0000}[/B]
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002aab117, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000007efa0000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f[/B]
      BIOS Version                  V17.10
      BIOS Release Date             03/23/2011
      Manufacturer                  MSI
      Product Name                  MS-7599
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/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]**************************Fri Apr 26 17:13:01.324 2013 (UTC - 4:00)**************************
    amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
    [COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
    AtihdW76.sys                Thu Feb 14 17:11:09 2013 (511D60FD)
    atikmpag.sys                Thu Mar 28 21:09:45 2013 (5154E9D9)
    atikmdag.sys                Thu Mar 28 22:27:04 2013 (5154FBF8)
    [/font]
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
     
  3. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    thanks for all the great information, and ill try all of it. but i am having a problem with the computer blue screenin while im trying to work. can i do all of this in safe mode?
     
  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Start with the AMD OverDrive and graphics drivers in Safe Mode. See if that helps, then move on from there.
     
  5. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    also, i tried updating my PC and a lot of the updates are working...but most are failing and are unable to updating.
     
  6. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Try to do everything that you can, then see if it still has problems.
    Also, try the free diagnostics here: Initial Hardware Diagnostics
    Follow up with these as you're able: Additional Hardware Diagnostics

    If you still have problems, upload another data collection report and a copy of this also:

    Please do the following:
    - open Event Viewer (eventvwr.msc)
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
     
  7. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    >working on pc uninstalling drivers etc
    >this happends right before i blue screen EVERY time. only shows up for a spilt second then shows the bsod
    20130428_093900_43610.
     
    #7 Michael Cahill, Apr 28, 2013
    Last edited: Apr 28, 2013
  8. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    i removed the drivers and installed as instructed..it ran good for 9-10 hours and did the same routine.
     
    #8 Michael Cahill, Apr 28, 2013
    Last edited: Apr 28, 2013
  9. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    This looks (IMO) to be a video problem. As such, try the steps here (even though these aren't your type of BSOD's): Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

    I still need the reports that I requested in my previous post
    Also, please run the hardware diagnostics that I suggested in my previous posts. Start with the video tests in the 2nd link (but do all the tests).
     
  10. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    2nd link where? and also im reading over these diagnostics links it says use at your own risk....what am i risking? and are these hard to set up?...seems a little over my head.
     
    #10 Michael Cahill, Apr 29, 2013
    Last edited: Apr 29, 2013
  11. Michael Cahill

    Michael Cahill New Member

    Joined:
    Apr 26, 2013
    Messages:
    14
    Likes Received:
    0
    event viewer information
     

    Attached Files:

  12. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    2nd link is: Additional Hardware Diagnostics

    The risk is that, if improperly run/paid attention to, your computer can overheat and actually melt into a puddle of molten metal and plastic. While this is extremely unlikely, I sure wouldn't leave the computer alone while they're running.

    Most systems will automatically shut down when the system starts to overheat, but on occasion those safeguards are broken and the system can damage itself.

    If the system starts to do this, the system will display erratic behavior (mostly distorted video). If this happens, just remove the power from the system in order to shut it down. Distorted video during a stress test is a sign of a problem with the system, so the stress test is needed for this.

    With some of the stress tests you can get an idea of the behavior of the system, so you can tell if it's safe to leave it alone for a bit - but each system and each test is different. So it's your choice when/if to attempt this, and the consequences are solely on you.

    As for setting them up, just follow the directions line-by-line and it should work just fine.
     
  13. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    FYI - the Event Viewer zip file only contains a shortcut, not the actual data. Please re-upload the data for us to have a look at.
     

Share This Page

Loading...