locked
Windows 7 Blue screen issue.0x0000001A RRS feed

  • Question

  • I got a BSOD with the error message 0x0000001A. below is the Dump file debug by winDbg. seemed it is cause by iexplore.exe.

    However, I can't quite understand what it says and how to fix it

    I uploaded memory.dmp file on https://1drv.ms/u/s!Ano3_c6eO3higQmk-9OkfQx5qa-z

    I tried below, but not fix the issue.
    I ran sfc/scannow but there were no integrity violations.

    run scandisk for full disk repair

    I also ran my virus scan AV but it detected no severe viruses.

    ----------------------------------------------------------------------------------------------------------------------------------------------
    Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\temp\MEMORY.DMP]
    Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
    Machine Name:
    Kernel base = 0xfffff800`0361e000 PsLoadedModuleList = 0xfffff800`03860750
    Debug session time: Mon Aug 21 14:00:02.575 2017 (UTC - 7:00)
    System Uptime: 0 days 20:13:33.130
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {5003, fffff70001080000, 1f44d, 1f44f0003e09a}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3cb9d )

    Followup:     MachineOwner
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 000000000001f44d
    Arg4: 0001f44f0003e09a

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING:  7601.23864.amd64fre.win7sp1_ldr.170707-0600

    SYSTEM_MANUFACTURER:  LENOVO

    SYSTEM_PRODUCT_NAME:  3209DV1

    SYSTEM_SKU:  LENOVO_MT_3209

    SYSTEM_VERSION:  ThinkCentre M92p

    BIOS_VENDOR:  LENOVO

    BIOS_VERSION:  9SKT75AUS

    BIOS_DATE:  09/17/2013

    BASEBOARD_MANUFACTURER:  LENOVO

    BASEBOARD_PRODUCT:  MAHOBAY

    BASEBOARD_VERSION:  NOK

    DUMP_TYPE:  1

    BUGCHECK_P1: 5003

    BUGCHECK_P2: fffff70001080000

    BUGCHECK_P3: 1f44d

    BUGCHECK_P4: 1f44f0003e09a

    BUGCHECK_STR:  0x1a_5003

    CPU_COUNT: 4

    CPU_MHZ: cdc

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3a

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  iexplore.exe

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  TER20779

    ANALYSIS_SESSION_TIME:  08-24-2017 09:12:58.0800

    ANALYSIS_VERSION: 10.0.15063.468 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff8000362d7fc to fffff8000368d980

    STACK_TEXT: 
    fffff880`06394978 fffff800`0362d7fc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0001f44d : nt!KeBugCheckEx
    fffff880`06394980 fffff800`0368baae : 00000000`00000001 00000000`206cb000 00000000`62c8da01 00000000`206cb000 : nt! ?? ::FNODOBFM::`string'+0x3cb9d
    fffff880`06394ae0 00000000`634e67e3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`1ae081c4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x634e67e3


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  8c85ee1ecbaa5a5b47433ed1b6fe29d836c4f8ec

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fa31c96ddc3ea03692b6a593a7e0af5cd0f3939f

    THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+3cb9d
    fffff800`0362d7fc cc              int     3

    FAULT_INSTR_CODE:  c18b48cc

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3cb9d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  595fa11a

    IMAGE_VERSION:  6.1.7601.23864

    FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+3cb9d

    BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+3cb9d

    PRIMARY_PROBLEM_CLASS:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+3cb9d

    TARGET_TIME:  2017-08-21T21:00:02.000Z

    OSBUILD:  7601

    OSSERVICEPACK:  1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 7

    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE: 

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2017-07-07 07:56:26

    BUILDDATESTAMP_STR:  170707-0600

    BUILDLAB_STR:  win7sp1_ldr

    BUILDOSVER_STR:  6.1.7601.23864.amd64fre.win7sp1_ldr.170707-0600

    ANALYSIS_SESSION_ELAPSED_TIME:  627

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x1a_5003_nt!_??_::fnodobfm::_string_+3cb9d

    FAILURE_ID_HASH:  {6e14d092-f74b-68cd-2624-00116df408ca}

    Followup:     MachineOwner

    ----------------------------------------------------------------------------------------------------------------------------------------------


    • Edited by 正心 Thursday, August 24, 2017 8:36 PM
    Thursday, August 24, 2017 4:47 PM

Answers

  • The Msinfo32 was able to used in the troubleshooting.

    The dxdiag had not finished loading before it was saved.  So the troubleshooting information was missing.

    That was one of the toughest debugging in a long time.

    There were 32 mini dump files debugged

    There was 1 memory dump file debugged

    There were a total of 4 misbehaving drivers.

    There were 3 misbehaving hardware drivers identified.

    And there was 1 misbehaving software driver idntified.

    1) atikmdag.sys (this driver I had already given you the method to fix)

    It has not appeared as a recurrent bsod since you uninstalled and reinstalled it.



    2) e1c62x64.sys
    Intel(R) 82579V Gigabit Network Connection driver
    http://downloadcenter.intel.com/

    c:\windows\system32\drivers\e1c62x64.sys 

    a) First identify the availability of this driver on the Lenovo website.

    b) if it is not listed then download from the intel website

    c) download the driver to the desktop

    d) use device manager to uninstall the driver and then re-install from the desktop



    3) iusb3xhc.sys

    Intel(R) USB 3.0 eXtensible Host Controller Driver
    http://downloadcenter.intel.com/

    c:\windows\system32\drivers\iusb3xhc.sys

    a) Same method for replacement:  Identify the driver first on the Lenovo website 

    b) Uninstall using device manager

    c) re-install by direct download from the Lenovo website

    d) in case there is not a suitable driver on the Lenovo website use the Intel website.

    4) This is the application with the misbehaving software driver.

    If you no longer use this application you can completely uninstall it.

    If you still use this application please uninstall and reinstall it.

    ininqos.sys:  Interactive Intelligence 

    c:\windows\system32\drivers\ininqos.sys



    <Name><![CDATA[ininqos]]></Name>
    <Description><![CDATA[Interactive Intelligence QoS]]></Description>
    <File><![CDATA[c:\windows\system32\drivers\ininqos.sys]]></File>
    <Type><![CDATA[Kernel Driver]]></Type>
    <Started><![CDATA[Yes]]></Started>
    <Start_Mode><![CDATA[System]]></Start_Mode>
    <State><![CDATA[Running]]></State>
    <Status><![CDATA[OK]]></Status>
    <Error_Control><![CDATA[Normal]]></Error_Control>
    <Accept_Pause><![CDATA[No]]></Accept_Pause>
    <Accept_Stop><![CDATA[Yes]]></Accept_Stop>
    </Data>
    <Data>








    http://interactiveconnect.com/can-i-update-my-cic-server-windows-operating-system/
    https://www.reasoncoresecurity.com/ininqos.sys-c9ad3ef86ad391d7cbb45551082b9d9773fd986c.aspx

    These 4 misbehaving drivers when uninstalled and replaced with good drivers should fix the BSODs!!!!





    Tuesday, August 29, 2017 6:48 PM
  • Hi,

    Did you recently change the hardware?

    From the dump file, I found these error message:

    The Bug Check 0x50 :mainly caused by defective RAM ,main memory , installation of  fault drive or system services

    BugCheck 1A, {5003}: caused by hardware

    BugCheck 1A, {41284}:  A PTE or the working set list is corrupted.

    dxgmms1.sys: caused by Microsoft DirectX Graphics MMS system driver file.

    Netio.sys Errors: caused by a variety of hardware, firmware, driver, or software issues

    As there are too many system files, drivers corrupted, I suggest you can perform a clean install after you backup all the files you needed.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 30, 2017 9:41 AM

All replies

  • With all the errors shown,my 1st guess would be a faulty MB battery,desktop,or if laptop,the battery charger

    must be installed 100% of pc operation.

    Thursday, August 24, 2017 10:58 PM
  • Hi,

    These crashes were related to memory corruption (probably caused by a driver). The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred. Have you recently installed some driver before the BSOD occurs? When did the BSOD happen?

     

    Please run Driver verifier to verify your memory and find which driver is causing the problem. You can also keep all your drivers up-to-date, especially the chipset and video drivers. Older drivers are a common contributor to BSOD issues.

    https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva

     

    Also, please run Memory diagnostic tool to check the RAM issue.

    If the BSOD occurs after you installed some driver, you can reinstall them to avoid the conflict.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 25, 2017 8:55 AM
  • The BSOD  memory dump file was debugged.

    There was 1 misbehaving driver:

    ATIKMDAG.SYS

    Perform the following steps:

    1) Uninstall everything AMD using Display driver uninstaller and install new drivers from the Lenovo or the AMD website.

    2) The Lenovo web site is preferred.  

    3) Enter the computer's serial or product number and the operating system to view available drivers.

    4) If you use the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

    https://www.wagnardsoft.com/

    Display Driver Uninstaller Download version 17.0.7.2

    https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

    http://support.amd.com/en-us


    Friday, August 25, 2017 2:35 PM
  • this is a desktop. don't understand what is MB battery mean? how to check it?

    thanks

    Friday, August 25, 2017 4:19 PM
  • this BSOD start from May. below is blue screen view info:

    Friday, August 25, 2017 4:20 PM
  • Hi,

    From the screenshot, the bsod usually caused by ntoskrl.exe or some .sys files. And for further research, we need to collect the dump file , you can post them on the network drive and share the link here.

     

    Ntoskrnl.exe is the kernel of the operating system. It might be related to memory corruption, CPU issues, overclocking drivers, outdated device drivers or even conflicted device drivers.

    .sys files like Dxgmms1.sys blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues. 

    Follow these steps to help you narrow down the issue firstly:

    1.Run Driver verifier to verify your memory and find which driver is causing the problem.  

    2.Run Memory diagnostic tool to check the RAM issue.

    3.Run sfc /scannow in CMD as administrator to scan and repair the corrupted files.

    4.Reinstall the drivers before the BSOD occurs


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 28, 2017 5:52 AM
  • Let us know your progress with uninstalling and reinstall the graphics driver.

    If you have any more bsod you should post the following into the the thread:

    1) one drive or drop box share link with msinfo32

    2) one drive or drop box share link with dxdiag

    3) one drive or drop box share link with the mini dump files (c:\windows\minidump)

    Monday, August 28, 2017 6:47 AM
  • hi

    also try to below options

    How To Disable the Automatic Restart on System Failure

    1. Click on the Start button and then on Control Panel.

      Tip: In a hurry? Type system in the search box after clicking Start. Choose System under the Control Panel heading in the list of results and then skip to Step 4.

    2. Click on the System and Security link.

      Note: If you're viewing the Small icons or Large icons view of Control Panel, you won't see this link. Simply double-click on the System icon and proceed to Step 4.

    3. Click on the System link.

    4. In the task pane on the left, click the Advanced system settings link.

    5. Locate the Startup and Recovery section near the bottom of the window and click on the Settings button.

    6. In the Startup and Recovery window, locate and uncheck the check box next to Automatically restart.

    7. Click OK in the Startup and Recovery window.

    8. Click OK in the System Properties window.

                
    1. You can now close the System window.

    2. From now on, when a problem causes a BSOD or another major error that halts the system, Windows 7 will not force a reboot. You'll have to reboot manually when an error appears.

    Monday, August 28, 2017 6:54 AM
  • I completely reinstall ATI driver on 25, Aug, now the ATIKMDAG.SYS is the newest version(see below). but it is happen again on 27, Aug. sfc /scannow not working, run RAM test but no error found.what else I need to do? thanks

    msinfo32,dxdiag,Mini DMP file is uploaded again on https://1drv.ms/f/s!Ano3_c6eO3higQ0V9GyGGQz4Fs7i

    Monday, August 28, 2017 6:01 PM
  • This link did not have msinfo32 nor dxdiag.

    https://1drv.ms/f/s!Ano3_c6eO3higQ0V9GyGGQz4Fs7i

    The link had 31 mini dumps 

    and 1 memory dump

    Can you post msinfo32 and dxdiag with a share link?

    In the left lower corner search type:  MSINFO32 > wait a few minutes for it to load > save to desktop > post in one drive or drop box share link

    In the left lower corner search type:  DXDIAG > wait a few minutes for it to load > save to desktop > post in one drive or drop box as a share link



    Tuesday, August 29, 2017 6:34 AM
  • From the dump file and the Application Error, I found that you used Microsoft Security Essentials to scan and resulted in a bsod.

    You should firstly boot into Safe Mode with Networking and check the possible malicious process by Windows Defender.

    Then perform a clean boot and  reinstall the MSE by going to Microsoft Security Essentials Download Site https://www.microsoft.com/en-US/download/details.aspx?id=5201 In addition , make sure other antivirus software are uninstalled on your PC.

    Also, the system driver or .dll files may also cause the bsod. I suggest you update the driver and make sure the latest Lenovo System Update is installed.

    http://pcsupport.lenovo.com/ec/th/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thinkcentre-m92p/3209/3209dv1?linkTrack=Homepage%3ABody_Search+Products&searchType=5&keyWordSearch=3209DV1

     


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 29, 2017 7:12 AM
  • Other misbehaving drivers were identified viewing the 31 mini dump files.

    One of the misbehaving drivers is not on my list of drivers.

    So having the msinfo32 and dxdiag will be useful in finding the information about the misbehaving drivers.


    Tuesday, August 29, 2017 8:46 AM
  • msinfo32 and dxdiag  is included in dumpinfo.rar

    anyway, I share it again herehttps://1drv.ms/f/s!Ano3_c6eO3higRHoMx7-X-9SbFHZ

    Tuesday, August 29, 2017 3:35 PM
  • I saw MSE is installed on Aug 24, 2017. but the BSOD is start from June. the driver is all updated from Lenovo wen site.

    Tuesday, August 29, 2017 5:50 PM
  • The Msinfo32 was able to used in the troubleshooting.

    The dxdiag had not finished loading before it was saved.  So the troubleshooting information was missing.

    That was one of the toughest debugging in a long time.

    There were 32 mini dump files debugged

    There was 1 memory dump file debugged

    There were a total of 4 misbehaving drivers.

    There were 3 misbehaving hardware drivers identified.

    And there was 1 misbehaving software driver idntified.

    1) atikmdag.sys (this driver I had already given you the method to fix)

    It has not appeared as a recurrent bsod since you uninstalled and reinstalled it.



    2) e1c62x64.sys
    Intel(R) 82579V Gigabit Network Connection driver
    http://downloadcenter.intel.com/

    c:\windows\system32\drivers\e1c62x64.sys 

    a) First identify the availability of this driver on the Lenovo website.

    b) if it is not listed then download from the intel website

    c) download the driver to the desktop

    d) use device manager to uninstall the driver and then re-install from the desktop



    3) iusb3xhc.sys

    Intel(R) USB 3.0 eXtensible Host Controller Driver
    http://downloadcenter.intel.com/

    c:\windows\system32\drivers\iusb3xhc.sys

    a) Same method for replacement:  Identify the driver first on the Lenovo website 

    b) Uninstall using device manager

    c) re-install by direct download from the Lenovo website

    d) in case there is not a suitable driver on the Lenovo website use the Intel website.

    4) This is the application with the misbehaving software driver.

    If you no longer use this application you can completely uninstall it.

    If you still use this application please uninstall and reinstall it.

    ininqos.sys:  Interactive Intelligence 

    c:\windows\system32\drivers\ininqos.sys



    <Name><![CDATA[ininqos]]></Name>
    <Description><![CDATA[Interactive Intelligence QoS]]></Description>
    <File><![CDATA[c:\windows\system32\drivers\ininqos.sys]]></File>
    <Type><![CDATA[Kernel Driver]]></Type>
    <Started><![CDATA[Yes]]></Started>
    <Start_Mode><![CDATA[System]]></Start_Mode>
    <State><![CDATA[Running]]></State>
    <Status><![CDATA[OK]]></Status>
    <Error_Control><![CDATA[Normal]]></Error_Control>
    <Accept_Pause><![CDATA[No]]></Accept_Pause>
    <Accept_Stop><![CDATA[Yes]]></Accept_Stop>
    </Data>
    <Data>








    http://interactiveconnect.com/can-i-update-my-cic-server-windows-operating-system/
    https://www.reasoncoresecurity.com/ininqos.sys-c9ad3ef86ad391d7cbb45551082b9d9773fd986c.aspx

    These 4 misbehaving drivers when uninstalled and replaced with good drivers should fix the BSODs!!!!





    Tuesday, August 29, 2017 6:48 PM
  • Hi,

    Did you recently change the hardware?

    From the dump file, I found these error message:

    The Bug Check 0x50 :mainly caused by defective RAM ,main memory , installation of  fault drive or system services

    BugCheck 1A, {5003}: caused by hardware

    BugCheck 1A, {41284}:  A PTE or the working set list is corrupted.

    dxgmms1.sys: caused by Microsoft DirectX Graphics MMS system driver file.

    Netio.sys Errors: caused by a variety of hardware, firmware, driver, or software issues

    As there are too many system files, drivers corrupted, I suggest you can perform a clean install after you backup all the files you needed.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 30, 2017 9:41 AM
  • thanks all for the support. Two many error on system. I reimaged this computer. everything is fine now.

    Thursday, August 31, 2017 8:05 PM