none
Bugcheck: 0x0000001a (00000000`00041287 00000000`00000000 00000000`00000000 00000000`00000000) RRS feed

  • General discussion

  • Windows 7 Ultimate x64 with all patches.

    The system crashes after being left idle with Outlook 2007 open at random times (see below).  Any suggestions would be appreciated.

    ==================================================
    Dump File         : 092212-13859-01.dmp
    Crash Time        : 9/22/2012 2:58:36 AM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041287
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\092212-13859-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,080
    ==================================================

    ==================================================
    Dump File         : 092012-8796-01.dmp
    Crash Time        : 9/20/2012 8:06:05 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041287
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\092012-8796-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,080
    ==================================================

    ==================================================
    Dump File         : 091912-8953-01.dmp
    Crash Time        : 9/19/2012 9:11:09 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041287
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : atapi.sys
    Caused By Address : atapi.sys+2b7b
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\091912-8953-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,080
    ==================================================

    ==================================================
    Dump File         : 091412-8781-01.dmp
    Crash Time        : 9/14/2012 7:46:00 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041287
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\091412-8781-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,472
    ==================================================

    ==================================================
    Dump File         : 091312-7218-01.dmp
    Crash Time        : 9/13/2012 11:28:48 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00003452
    Parameter 2       : 00000001`3f8a0000
    Parameter 3       : fffff700`01085480
    Parameter 4       : 1ff00000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\091312-7218-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,472
    ==================================================

    ==================================================
    Dump File         : 091312-9031-01.dmp
    Crash Time        : 9/13/2012 8:22:05 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041287
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\091312-9031-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,472
    ==================================================

    ==================================================
    Dump File         : 082612-20046-01.dmp
    Crash Time        : 8/26/2012 3:16:16 PM
    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00003452
    Parameter 2       : 00000001`80000000
    Parameter 3       : fffff700`01087c78
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7f1c0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+7f1c0
    Stack Address 1   :
    Stack Address 2   :
    Stack Address 3   :
    Computer Name     :
    Full Path         : C:\Windows\Minidump\082612-20046-01.dmp
    Processors Count  : 1
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 268,472
    ==================================================

     


    http://www.saberman.com

    Saturday, September 22, 2012 8:13 PM

All replies

  • Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

    Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.

    Saturday, September 22, 2012 11:36 PM
  • >an you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site?

    http://sdrv.ms/NJGHHd


    http://www.saberman.com

    Sunday, September 23, 2012 12:54 AM
  • Sunday, September 23, 2012 1:36 AM
  • I did the search and then righ click on it and slected run as an administartor.

    I first tried all unsigned drivers but there weren't any.

    I then selected all drivers.  When I clicked finished it said Access Denied.  When I closed the dialog box my system rebooted.

    I then tried starting in Safe Mode.  Logged in with an administrator id and started verifier.exe.   Selected all drivers and it said the system would have to reboot.  Press OK and got a BSOD.

    Tried safe mode again.  Logged in with an administator id and started verifier.exe.  Again selected all drivers and at the end of the process again got a BSOD.

    Tried safe mode again. Logged in with an administator id and started verifier.exe.  Selected all drivers.  Instead of pressing the OK button when it said the system had to be rebooted I closed the dialog box.  Then I restarted the system.

    Windows started and brought up the first graphic and stayed there.  It did not switch to the login screen.  Wait a half hour and gave up.  Hit reset and went into safe mode.  Started verifier.exe and checked the setting -- all drivers were selected.  Went back and selected delecte all settings.  Went through the process and got a BSOD.

    Repeated a few times and finally did a shutdown and restarted and was able to boot my system.

    I think verifier needs to be verified.


    http://www.saberman.com


    Do not use verifier without doing a complete backup of your system.
    • Edited by saberman Sunday, September 23, 2012 5:03 AM Verifier is broken
    Sunday, September 23, 2012 5:01 AM
  • Can you provide the minidump files from the BSODs that you experienced using the Driver Verifier?

    Also, can you provide following file which should contain more information on the crash:

    C:\Windows\MEMORY.DMP

    The memory.dmp file will be quite large so to upload it to Windows Live SkyDrive you may have to zip and compress the file with a third party application such as 7-Zip or WinRAR.

    Sunday, September 23, 2012 2:56 PM
  • The link below is to a zip archive that contains both the mini dumps and MEMORY.DMP from the last crash.

    http://sdrv.ms/NL5GK8

    However, I am more interested in researching the problem with my system without verifier.  Verifier appears to be fairly dangerous.


    http://www.saberman.com

    Sunday, September 23, 2012 7:56 PM
  • The Diver Verifier can be useful but can also, by itself, cause issues.

    The minidump files with the Driver Verifier enabled showed the same MEMORY_MANAGEMENT (1a) stop error with verifier.exe as the process that crashed.

    No third party driver appeared to be involved in the crash.

    I could not locate the memory.dmp file.

    Can you upload the memory.dmp file again?

    One thing I might suggest, if you have not already, is to check the physical RAM with a memory tester such as Windows Memory Diagnostic and/or Memtest86+.

    Also, when did the crashes start and did the start of the crashes coincide with any software or hardware change. 

    Sunday, September 23, 2012 9:09 PM
  • Sorry about that.  The zip archive is around 80 MB.

    http://sdrv.ms/OTJv0t


    http://www.saberman.com

    Sunday, September 23, 2012 10:09 PM
  • Hi,

    Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).

    The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    Microsoft - Help and Support

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

    If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.

    http://www.microsoft.com/worldwide/

    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.


    Juke Chou

    TechNet Community Support

    Monday, September 24, 2012 10:02 AM
    Moderator
  • Hi,

    How’s everything going? Please feel free to give me any update.

    Thank you for your cooperation.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang

    TechNet Community Support

    Tuesday, October 9, 2012 6:44 AM
    Moderator
  • >Please be advised that contacting phone support will be a charged call.

    So because the BSOD dump process is poorly written I have to pay Microsoft to identify what process was in control when the error orccurred.  I assume that if it turns out to be a Microsoft component Microsoft will pay me for the time I spent documenting the problem and working with their technicians.  Is that correct?


    http://www.saberman.com

    Wednesday, October 10, 2012 4:27 AM