BSOD after logging in after restarting.


  1. Posts : 3
    Windows 7 Pro 64 bit
       #1

    BSOD after logging in after restarting.


    Hi there. I've been having a problem with my computer for a while now. 4 times ouf of 5 after putting in my login password after restarting it will BSOD at the desktop with the STOP error 0x0000001e. If anyone could tell me with this it would be greatly appreciated. (:
    Last edited by xjermariox; 01 May 2013 at 19:19.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Security App

    Crashes indicate AVG being a possible cause. Remove AVG and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

    Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

    Microsoft Security Essentials, Free antivirus for windows

    Malwarebytes Anti-Malware Free


       Information
    DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.


    This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

    BIOS64.sys Sun Jun 8 06:12:00 2003 (3EE27F50)
    This is probably aBIOSTAR I/O driver file
    http://www.carrona.org/drivers/driver.php?id=BIOS64.sys

    BS_I2c64.sys Mon Jun 16 12:45:18 2008 (48560BFE)
    Found in BIOSTAR BIOS Flash Utility
    http://www.carrona.org/drivers/driver.php?id=BS_I2c64.sys

    xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
    XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
    http://www.carrona.org/drivers/driver.php?id=xusb21.sys

    AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    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 Win7 systems.
    Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's.

    Please run these tests and report back the results

    1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
    2. Disk check for errors on the hard drive - Disk Check
    3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
    4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
    5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

    The below is for information purposes only. Contains relevant information from the blue screen analysis:
    Code:
    Debug session time: Thu May  2 05:43:29.919 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-52431-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:02:39.121
    Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
    BugCheck 1E, {ffffffffc0000005, fffff8000327e66b, 0, 7efa0000}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8000327e66b, 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:  avgwdsvc.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Thu May  2 05:39:27.705 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-50201-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:01:50.297
    Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
    BugCheck 1E, {ffffffffc0000005, fffff8000330c0c5, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8000330c0c5, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!KeStackAttachProcess+115
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Thu May  2 05:10:37.305 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-82945-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:08:45.897
    Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
    BugCheck 1E, {ffffffffc0000005, fffff800032d34e3, 0, 2e0}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800032d34e3, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 00000000000002e0, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!output_l+31b
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Thu May  2 04:55:23.858 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-61713-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:04:25.060
    Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
    BugCheck 1E, {ffffffffc0000005, fffff800032da4e3, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800032da4e3, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!output_l+31b
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Thu May  2 04:50:06.491 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-62728-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:08:57.083
    Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
    BugCheck 1E, {ffffffffc0000005, fffff800032c14e3, 0, 560}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800032c14e3, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000560, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!output_l+31b
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Thu May  2 04:40:29.085 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-51807-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:01:57.287
    Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
    BugCheck 1E, {ffffffffc0000005, fffff800032c14e3, 0, 87af}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Bugcheck code 0000001E
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800032c14e3, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 00000000000087af, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!output_l+31b
    BiosVersion = 080014 
    BiosReleaseDate = 09/02/2010
    SystemManufacturer = BIOSTAR Group
    SystemProductName = A770E3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  3. Posts : 3
    Windows 7 Pro 64 bit
    Thread Starter
       #3

    First off I would like to say thank you so much for you time it is greatly appreciated!

    After removing AVG I've restarted my computer about 3 times or so and haven't had it BSOD which is good news. I'm going to take the time now to update those drivers you post and run those scans as well. Also here is the msinfo file. Once again thank you for your time!
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Okay, please remove these tools as well:
    Code:
    Start Menu\Programs\Advanced SystemCare 6	Public:Start Menu\Programs\Advanced SystemCare 6	Public
    Start Menu\Programs\IObit Malware Fighter	Public:Start Menu\Programs\IObit Malware Fighter	Public
    Start Menu\Programs\WinZip Registry Optimizer	Public:Start Menu\Programs\WinZip Registry Optimizer	Public
    Revo Uninstaller

    Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

    Keep us posted, good luck.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    How are things?
      My Computer


  6. Posts : 3
    Windows 7 Pro 64 bit
    Thread Starter
       #6

    Things have been great. No more BSOD since following your steps! Thanks a bunch!

    I ran those scans you mentioned above, but I couldn't find any saved logs from the test.

    1. SFC /scannow - This finished saying " Windows Resource Protection did not find any integrity violations"
    2. Disk check - Went through and fixed whatever.
    3. Troubleshoot applications by a clean boot - I used the Microsoft fix it app. And it didn't find any errors.
    4. Memtest86+- This hour long scan ended saying there wasn't any problems
    5. Hard drive test- I couldn't get this to work right. Maybe I burned the CD wrong or something. I'll have to try again once I get more blanks.

    Thanks again for you help!
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7

    xjermariox said:
    Things have been great. No more BSOD since following your steps! Thanks a bunch!

    I ran those scans you mentioned above, but I couldn't find any saved logs from the test.

    1. SFC /scannow - This finished saying " Windows Resource Protection did not find any integrity violations"
    2. Disk check - Went through and fixed whatever.
    3. Troubleshoot applications by a clean boot - I used the Microsoft fix it app. And it didn't find any errors.
    4. Memtest86+- This hour long scan ended saying there wasn't any problems
    5. Hard drive test- I couldn't get this to work right. Maybe I burned the CD wrong or something. I'll have to try again once I get more blanks.

    Thanks again for you help!
    You're welcome and thanks for the feedback.

    Wait for a week or longer before marking the thread as solved.
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    If you have BSOD issues again please post here :)
       Tip

    If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 03:28.
Find Us