Solved

Random BSOD: Memory_Management, DRIVER_CORRUPTED_EXPOOL, Need Help PLEASE

Random BSOD after Reformat and Several Other Changes. PLEASE help

Hello and good evening. This BSOD business has been driving me up a wall for the past 2 weeks. I've been reading post after post and trying so many different things but I haven't been able to shake the issue.

Below are the latest BSOD reports that I got from BlueScreen Viewer but I would like to list out some of the things I have done, in no particular order:

1. ran memtest on ram and it all tested good
2. Purchased NEW ram and threw out the old ram (6 yrs or so)
3. Ran Memtest on new ram for a solid 20 hours (6 passes) - not a single error
4. Replaced video card with new video card. It is compatible w/MoBo, yes. If PC specs are needed please let me know
5. Reformatted PC 3 times, once with a different windows 7 disk.
6. Disc scanned, using windows, all of my HDDs and my SSD that WIndows 7 runs on
7. Flashed BIOS w/latest update

Please note that all of this 'stuff' was done AFTER I started getting BSODs.

Below are my BSODs:

Quote:
==================================================
Dump File : 021414-20997-01.dmp
Crash Time : 2/14/2014 7:53:22 AM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : fffffa80`027c3018
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02fc0127
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021414-20997-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 332,312
Dump File Time : 2/14/2014 1:26:16 PM
==================================================

==================================================
Dump File : 021314-20950-01.dmp
Crash Time : 2/13/2014 8:05:06 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : 00000000`0a925001
Parameter 3 : 00000000`000094ca
Parameter 4 : fffff700`01080000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021314-20950-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,680
Dump File Time : 2/13/2014 8:36:35 PM
==================================================

==================================================
Dump File : 021314-24398-01.dmp
Crash Time : 2/13/2014 7:36:46 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : 00000000`23d55001
Parameter 3 : 00000000`00012f05
Parameter 4 : fffff700`01080000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021314-24398-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,680
Dump File Time : 2/13/2014 7:40:46 PM
==================================================

==================================================
Dump File : 021314-24133-01.dmp
Crash Time : 2/13/2014 8:42:48 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02fe8c21
Parameter 3 : fffff880`077f4020
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021314-24133-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,544
Dump File Time : 2/13/2014 4:47:03 PM
==================================================

==================================================
Dump File : 021214-24585-01.dmp
Crash Time : 2/12/2014 8:19:57 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000403
Parameter 2 : fffff680`00008228
Parameter 3 : b8b00001`fc631025
Parameter 4 : fffff680`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021214-24585-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,736
Dump File Time : 2/12/2014 8:22:24 PM
==================================================

==================================================
Dump File : 021214-25896-01.dmp
Crash Time : 2/12/2014 8:11:49 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : 00000001`23ecf001
Parameter 3 : 00000000`000fa993
Parameter 4 : fffff700`01080000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+80640
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021214-25896-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 271,264
Dump File Time : 2/12/2014 8:14:13 PM
==================================================



Minidump files: https://www.mediafire.com/?ikr86hs0srt20tu

I am at a loss. I've spent so much $$ on replacing items and it just never stops. I appreciate any all help. THank you to any/everyone in advance.

Lane
10 answers Last reply Best Answer
More about random bsod memory management driver corrupted expool
  1. Best answer
    95% of the time the term memory corruption does not mean that your RAM is broken. It means that the software had detected the wrong data stored at a particular place in the RAM on the machine. It is like a wallet, I put in a $50 bill, close it and later open it but it is now $3 one dollar bills. It can be a problem with the wallet but more likely something else happened and it is not the wallets fault (95% of the time)


    anyway back to the problem: the file 021414-20997-01.dmp should have the answer to your problem, It is basically windows catching a hand in the wallet. Where the others are just complaining about the fact that the contents of the wallet have been changed.

    give me a minute to look at it

    Edit:
    corruption caused by
    \SystemRoot\system32\DRIVERS\athurx.sys
    date Wed Apr 20 03:07:45 2011


    I think this is just a old Atheros wireless driver connected to a USB device.
    you will want to locate and install and activate a new driver. (usb drivers don't always get activated as the default when they are installed, so check in device manager that you do get a new one installed and activated.)


    2: kd> lmvm athurx
    start end module name
    fffff880`0281c000 fffff880`029fa000 athurx T (no symbols)
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys


    debug info
    BugCheck C5, {fffffa80027c3018, 2, 0, fffff80002fc0127}
    DRIVER_CORRUPTED_EXPOOL (c5)

    notes:
    ASUS P5N32-E SLI ACPI BIOS Revision 1903
    BIOS Release Date 11/17/2009
    Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
    Manufacturer ASUSTeK Computer INC.
    Product P5N32-E SLI
    Max Speed 3800MHz
    Current Speed 2400MHz


    Note: you will want to update your BIOS if you can get a new one. It will have fixes that will work around errors in the various hardware in you machine. (incorrect memory settings, usb settings and fixes for microcode errors in the CPU.)
    I mention this because that driver will depend on the correct function of the USB host controller, and that host controller depends on correct BIOS settings which is why you want to make sure you have the best one you can get for your machine.
  2. johnbl said:
    95% of the time the term memory corruption does not mean that your RAM is broken. It means that the software had detected the wrong data stored at a particular place in the RAM on the machine. It is like a wallet, I put in a $50 bill, close it and later open it but it is now $3 one dollar bills. It can be a problem with the wallet but more likely something else happened and it is not the wallets fault (95% of the time)


    anyway back to the problem: the file 021414-20997-01.dmp should have the answer to your problem, It is basically windows catching a hand in the wallet. Where the others are just complaining about the fact that the contents of the wallet have been changed.

    give me a minute to look at it

    Edit:
    corruption caused by
    \SystemRoot\system32\DRIVERS\athurx.sys
    date Wed Apr 20 03:07:45 2011


    I think this is just a old Atheros wireless driver connected to a USB device.
    you will want to locate and install and activate a new driver. (usb drivers don't always get activated as the default when they are installed, so check in device manager that you do get a new one installed and activated.)


    2: kd> lmvm athurx
    start end module name
    fffff880`0281c000 fffff880`029fa000 athurx T (no symbols)
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys


    debug info
    BugCheck C5, {fffffa80027c3018, 2, 0, fffff80002fc0127}
    DRIVER_CORRUPTED_EXPOOL (c5)

    notes:
    ASUS P5N32-E SLI ACPI BIOS Revision 1903
    BIOS Release Date 11/17/2009
    Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
    Manufacturer ASUSTeK Computer INC.
    Product P5N32-E SLI
    Max Speed 3800MHz
    Current Speed 2400MHz


    Note: you will want to update your BIOS if you can get a new one. It will have fixes that will work around errors in the various hardware in you machine. (incorrect memory settings, usb settings and fixes for microcode errors in the CPU.)
    I mention this because that driver will depend on the correct function of the USB host controller, and that host controller depends on correct BIOS settings which is why you want to make sure you have the best one you can get for your machine.




    Hi John and THANK you for your help. I appreciate the response.

    I am having a little bity of a time following your instructions. I don't have the Atheros wireless adapter anymore (for several years) so I am a little confused on how it popped back up since I reformatted and all..... Do you know how I can properly remove the driver all together? I am not sure on that process.

    Also, I uploaded a few more pieces of information that may help in determining the root cause for all of this.

    Drivers List:https://www.mediafire.com/?lvw2u9badlzbyya

    System Information: https://www.mediafire.com/?lvw2u9badlzbyya

    None of these reports were obtained in safe mode.

    Was there anything else in your post that was instructional to me? I read through it a few times and the only thing I could gather was regarding the Atheros driver and updating it.

    THanks again for the help.

    Lane
  3. edit: on c:\windows\inf\setupapi.dev.log
    you can directly look at this log and find the date and time that the usb wireless device was inserted into your machine.
    (if you want to figure it when, why and who installed the driver)


    Note: you had many bugchecks that indicated failures do a drivers data being corrupted. But only one bugcheck where windows caught a driver attempting to write on memory it did not own. (causing the corruption.) That driver was the wireless network adapter, It would not be loaded unless at sometime someone plugged it into a usb port on your machine.
    It only take a second. From then on, it is loaded in case it gets plugged back in some time in the future.

    so, make sure the driver is removed. delete all of your current memory dumps and run your system and see if the problem is resolved.
    --------------------

    usb drivers are kind of special, they can be plugged in/out ant any time so rather than remove them they are hidden in device manager. This means their drivers are still loaded and cause problems even after you remove the device.

    What you want to do is have the device manager display hidden/removed devices so you can remove them
    it is a registry setting:
    http://support.microsoft.com/kb/315539

    You may find that it is best to use the plug and play utility to remove the actual installation files for the OEM driver.
    Windows will keep a copy of the driver and a backup copy of the driver in its driver store. You want to get rid of both. I looked at my network driver and I have 8 versions of the same driver on my machine.

    what you want to do in this case is start the command shell (cmd.exe) as a admin (windows key+x + A)
    then run
    pnputil.exe -e (this will make a list of all oem drivers on your system)
    look at the list, find the published name of the driver you want to remove, it will be something like "oem9.inf"
    then remove it using
    pnputil.exe -d oem9.inf

    This is very helpful because it removes the copy from the driverstore. If you remove the driver directly, the windows plug and play will detect the uninstalled hardware and reinstall the old driver a few seconds after your just removed it. (The only symptom you get is people complaining that updating the driver did not help.) Often you want to go to control panel device manager and confirm what driver you have for your device and who made the driver.

    Vendors will give Microsoft a basic driver for their device but they will keep working on the driver and make a enhanced version with special features that they will have on their own website. Some of these enhancements are bug fixes that they know about but don't want to go through the process required to give them to microsoft.
    Vendors sell hardware, it is often not in their best interest to update drivers because that allows you not to buy a new piece of hardware from them. basically, no update to old driver = more sales for them, you buy new hardware to get new drivers.




    look at the list, find the ones you want to remove and


    Lanep82 said:
    johnbl said:
    95% of the time the term memory corruption does not mean that your RAM is broken. It means that the software had detected the wrong data stored at a particular place in the RAM on the machine. It is like a wallet, I put in a $50 bill, close it and later open it but it is now $3 one dollar bills. It can be a problem with the wallet but more likely something else happened and it is not the wallets fault (95% of the time)


    anyway back to the problem: the file 021414-20997-01.dmp should have the answer to your problem, It is basically windows catching a hand in the wallet. Where the others are just complaining about the fact that the contents of the wallet have been changed.

    give me a minute to look at it

    Edit:
    corruption caused by
    \SystemRoot\system32\DRIVERS\athurx.sys
    date Wed Apr 20 03:07:45 2011


    I think this is just a old Atheros wireless driver connected to a USB device.
    you will want to locate and install and activate a new driver. (usb drivers don't always get activated as the default when they are installed, so check in device manager that you do get a new one installed and activated.)


    2: kd> lmvm athurx
    start end module name
    fffff880`0281c000 fffff880`029fa000 athurx T (no symbols)
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys


    debug info
    BugCheck C5, {fffffa80027c3018, 2, 0, fffff80002fc0127}
    DRIVER_CORRUPTED_EXPOOL (c5)

    notes:
    ASUS P5N32-E SLI ACPI BIOS Revision 1903
    BIOS Release Date 11/17/2009
    Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
    Manufacturer ASUSTeK Computer INC.
    Product P5N32-E SLI
    Max Speed 3800MHz
    Current Speed 2400MHz


    Note: you will want to update your BIOS if you can get a new one. It will have fixes that will work around errors in the various hardware in you machine. (incorrect memory settings, usb settings and fixes for microcode errors in the CPU.)
    I mention this because that driver will depend on the correct function of the USB host controller, and that host controller depends on correct BIOS settings which is why you want to make sure you have the best one you can get for your machine.




    Hi John and THANK you for your help. I appreciate the response.

    I am having a little bity of a time following your instructions. I don't have the Atheros wireless adapter anymore (for several years) so I am a little confused on how it popped back up since I reformatted and all..... Do you know how I can properly remove the driver all together? I am not sure on that process.

    Also, I uploaded a few more pieces of information that may help in determining the root cause for all of this.

    Drivers List:https://www.mediafire.com/?lvw2u9badlzbyya

    System Information: https://www.mediafire.com/?lvw2u9badlzbyya

    None of these reports were obtained in safe mode.

    Was there anything else in your post that was instructional to me? I read through it a few times and the only thing I could gather was regarding the Atheros driver and updating it.

    THanks again for the help.

    Lane
  4. hi John.

    Thank you again for the detailed reply.

    I did the command as you asked in the cmd.exe prompt and got the following. Can you tell me which one of these I should remove?


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>pnputil.exe -e
    Microsoft PnP Utility

    Published name : oem0.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7600.16385
    Signer name : Microsoft Windows

    Published name : oem1.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7601.17514
    Signer name : Microsoft Windows

    Published name : oem2.inf
    Driver package provider : TP-LINK
    Class : Network adapters
    Driver date and version : 04/20/2011 2.0.0.62
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem3.inf
    Driver package provider : NVIDIA
    Class : Display adapters
    Driver date and version : 12/19/2013 9.18.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem4.inf
    Driver package provider : ATK
    Class : System devices
    Driver date and version : 08/13/2004 1043.2.15.37
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem5.inf
    Driver package provider : Western Digital Technologies
    Class : WD Drive Management devices
    Driver date and version : 01/19/2011 1.0.0009.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem6.inf
    Driver package provider : Creative
    Class : Sound, video and game controllers
    Driver date and version : 07/07/2010 6.0.01.1348
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem7.inf
    Driver package provider : Adobe
    Class : Printers
    Driver date and version : 01/18/2007 8.1.0000.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem8.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 05/28/2012 15.0.4128.4000
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem9.inf
    Driver package provider : NVIDIA Corporation
    Class : Sound, video and game controllers
    Driver date and version : 11/28/2013 1.3.30.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem10.inf
    Driver package provider : NVIDIA
    Class : Universal Serial Bus controllers
    Driver date and version : 12/19/2013 6.14.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem11.inf
    Driver package provider : Apple, Inc.
    Class : Universal Serial Bus controllers
    Driver date and version : 12/12/2012 6.0.9999.65
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem12.inf
    Driver package provider : Apple
    Class : Network adapters
    Driver date and version : 07/15/2013 1.8.5.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher


    C:\Windows\system32>
  5. oem2.inf is your old wireless adapter

    use the pnputil.exe to remove the driver
    I would also go to the control panel, in the uninstall software and make sure you don't have anything
    there to uninstall (tp-link)


    Lanep82 said:
    hi John.

    Thank you again for the detailed reply.

    I did the command as you asked in the cmd.exe prompt and got the following. Can you tell me which one of these I should remove?


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>pnputil.exe -e
    Microsoft PnP Utility

    Published name : oem0.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7600.16385
    Signer name : Microsoft Windows

    Published name : oem1.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7601.17514
    Signer name : Microsoft Windows

    Published name : oem2.inf
    Driver package provider : TP-LINK
    Class : Network adapters
    Driver date and version : 04/20/2011 2.0.0.62
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem3.inf
    Driver package provider : NVIDIA
    Class : Display adapters
    Driver date and version : 12/19/2013 9.18.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem4.inf
    Driver package provider : ATK
    Class : System devices
    Driver date and version : 08/13/2004 1043.2.15.37
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem5.inf
    Driver package provider : Western Digital Technologies
    Class : WD Drive Management devices
    Driver date and version : 01/19/2011 1.0.0009.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem6.inf
    Driver package provider : Creative
    Class : Sound, video and game controllers
    Driver date and version : 07/07/2010 6.0.01.1348
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem7.inf
    Driver package provider : Adobe
    Class : Printers
    Driver date and version : 01/18/2007 8.1.0000.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem8.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 05/28/2012 15.0.4128.4000
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem9.inf
    Driver package provider : NVIDIA Corporation
    Class : Sound, video and game controllers
    Driver date and version : 11/28/2013 1.3.30.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem10.inf
    Driver package provider : NVIDIA
    Class : Universal Serial Bus controllers
    Driver date and version : 12/19/2013 6.14.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem11.inf
    Driver package provider : Apple, Inc.
    Class : Universal Serial Bus controllers
    Driver date and version : 12/12/2012 6.0.9999.65
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem12.inf
    Driver package provider : Apple
    Class : Network adapters
    Driver date and version : 07/15/2013 1.8.5.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher


    C:\Windows\system32>
  6. Hello and good morning.

    Well, I've done what you ask and there have been 4 more BSOD's over the past few days. A link to my minidump files is here: http://www.mediafire.com/download/7pr75fd9hb5j454/Lanep82-Minidump_2-20-14.zip

    My BSOD summaries are below. Can you please help??

    Quote:
    ==================================================
    Dump File : 022014-21777-01.dmp
    Crash Time : 2/20/2014 3:19:49 AM
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff880`00f5126c
    Parameter 3 : fffff880`03ec33b8
    Parameter 4 : fffff880`03ec2c10
    Caused By Driver : athurx.sys
    Caused By Address : athurx.sys+7750
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : Wdf01000.sys+7826c
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022014-21777-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 332,344
    Dump File Time : 2/20/2014 6:44:49 AM
    ==================================================

    ==================================================
    Dump File : 021914-20919-01.dmp
    Crash Time : 2/18/2014 4:58:15 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffffa80`027970f0
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff800`031ad98f
    Parameter 4 : 00000000`00000002
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021914-20919-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,680
    Dump File Time : 2/19/2014 4:39:19 PM
    ==================================================

    ==================================================
    Dump File : 021814-21543-01.dmp
    Crash Time : 2/17/2014 8:23:31 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000020
    Parameter 2 : fffffa80`06f1b8a0
    Parameter 3 : fffffa80`06f1b8a0
    Parameter 4 : 00000000`04000010
    Caused By Driver : usbhub.sys
    Caused By Address : usbhub.sys+358f
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021814-21543-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 332,312
    Dump File Time : 2/18/2014 6:34:19 AM
    ==================================================

    ==================================================
    Dump File : 021714-21559-01.dmp
    Crash Time : 2/17/2014 5:03:43 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffffa80`02e94f30
    Parameter 2 : 00000000`00000001
    Parameter 3 : fffff800`02e98dac
    Parameter 4 : 00000000`00000002
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021714-21559-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,680
    Dump File Time : 2/17/2014 5:05:12 PM
    ==================================================

  7. your problem is cause by athurx.sys it is still there in memory corrupting data.
    It has the same date and file as your previous bugchecks. You need to remove update your driver or remove the driver.


    3: kd> lmvm athurx
    start end module name
    fffff880`0280c000 fffff880`029ea000 athurx T (no symbols)
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp: Wed Apr 20 03:07:45 2011 (4DAEB071)
    CheckSum: 001E1C78
    ImageSize: 001DE000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
  8. johnbl said:
    oem2.inf is your old wireless adapter

    use the pnputil.exe to remove the driver
    I would also go to the control panel, in the uninstall software and make sure you don't have anything
    there to uninstall (tp-link)


    Lanep82 said:
    hi John.

    Thank you again for the detailed reply.

    I did the command as you asked in the cmd.exe prompt and got the following. Can you tell me which one of these I should remove?


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>pnputil.exe -e
    Microsoft PnP Utility

    Published name : oem0.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7600.16385
    Signer name : Microsoft Windows

    Published name : oem1.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 06/21/2006 6.1.7601.17514
    Signer name : Microsoft Windows

    Published name : oem2.inf
    Driver package provider : TP-LINK
    Class : Network adapters
    Driver date and version : 04/20/2011 2.0.0.62
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem3.inf
    Driver package provider : NVIDIA
    Class : Display adapters
    Driver date and version : 12/19/2013 9.18.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem4.inf
    Driver package provider : ATK
    Class : System devices
    Driver date and version : 08/13/2004 1043.2.15.37
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem5.inf
    Driver package provider : Western Digital Technologies
    Class : WD Drive Management devices
    Driver date and version : 01/19/2011 1.0.0009.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem6.inf
    Driver package provider : Creative
    Class : Sound, video and game controllers
    Driver date and version : 07/07/2010 6.0.01.1348
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem7.inf
    Driver package provider : Adobe
    Class : Printers
    Driver date and version : 01/18/2007 8.1.0000.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem8.inf
    Driver package provider : Microsoft
    Class : Printers
    Driver date and version : 05/28/2012 15.0.4128.4000
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem9.inf
    Driver package provider : NVIDIA Corporation
    Class : Sound, video and game controllers
    Driver date and version : 11/28/2013 1.3.30.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem10.inf
    Driver package provider : NVIDIA
    Class : Universal Serial Bus controllers
    Driver date and version : 12/19/2013 6.14.13.3221
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem11.inf
    Driver package provider : Apple, Inc.
    Class : Universal Serial Bus controllers
    Driver date and version : 12/12/2012 6.0.9999.65
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    Published name : oem12.inf
    Driver package provider : Apple
    Class : Network adapters
    Driver date and version : 07/15/2013 1.8.5.1
    Signer name : Microsoft Windows Hardware Compatibility Publisher


    C:\Windows\system32>



    Jon-

    the tp-link is my new wireless adapter that is being used for my wireless USB stick right now
  9. I have a few more BSODs lately and they look to be different than the previous. Blue Screen View Followed by detailed system info. Link at bottom has all my minidumps. please help.

    Quote:
    ==================================================
    Dump File : 022514-21684-01.dmp
    Crash Time : 2/24/2014 8:39:35 PM
    Bug Check String : DRIVER_CORRUPTED_EXPOOL
    Bug Check Code : 0x000000c5
    Parameter 1 : fffffa80`02696738
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff800`0300a127
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022514-21684-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,712
    Dump File Time : 2/25/2014 6:45:27 AM
    ==================================================

    ==================================================
    Dump File : 022414-21028-01.dmp
    Crash Time : 2/24/2014 7:58:42 PM
    Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x0000001e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff800`0310e1b0
    Parameter 3 : 00000000`00000001
    Parameter 4 : 00000000`0000000b
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022414-21028-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,712
    Dump File Time : 2/24/2014 8:00:02 PM
    ==================================================

    ==================================================
    Dump File : 022414-20935-01.dmp
    Crash Time : 2/24/2014 7:57:30 PM
    Bug Check String : BUGCODE_USB_DRIVER
    Bug Check Code : 0x000000fe
    Parameter 1 : 00000000`00000006
    Parameter 2 : fffffa80`077811a0
    Parameter 3 : 00000000`4f444648
    Parameter 4 : 00000000`00000000
    Caused By Driver : USBPORT.SYS
    Caused By Address : USBPORT.SYS+2d2f1
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022414-20935-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,712
    Dump File Time : 2/24/2014 7:58:39 PM
    ==================================================

    ==================================================
    Dump File : 022414-22105-01.dmp
    Crash Time : 2/24/2014 6:25:55 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffff880`03fc2e90
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : win32k.sys
    Caused By Address : win32k.sys+c5c90
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022414-22105-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 331,816
    Dump File Time : 2/24/2014 6:27:23 PM
    ==================================================

    ==================================================
    Dump File : 022114-21528-01.dmp
    Crash Time : 2/20/2014 11:15:30 PM
    Bug Check String : DRIVER_CORRUPTED_EXPOOL
    Bug Check Code : 0x000000c5
    Parameter 1 : fffffa80`026c30a0
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff800`02fb5123
    Caused By Driver : USBPORT.SYS
    Caused By Address : USBPORT.SYS+f9b9
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022114-21528-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 332,344
    Dump File Time : 2/21/2014 1:05:23 PM
    ==================================================

    ==================================================
    Dump File : 022014-21777-01.dmp
    Crash Time : 2/20/2014 3:19:49 AM
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff880`00f5126c
    Parameter 3 : fffff880`03ec33b8
    Parameter 4 : fffff880`03ec2c10
    Caused By Driver : athurx.sys
    Caused By Address : athurx.sys+7750
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : Wdf01000.sys+7826c
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\022014-21777-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 332,344
    Dump File Time : 2/20/2014 6:44:49 AM
    ==================================================

    ==================================================
    Dump File : 021914-20919-01.dmp
    Crash Time : 2/18/2014 4:58:15 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffffa80`027970f0
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff800`031ad98f
    Parameter 4 : 00000000`00000002
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021914-20919-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,680
    Dump File Time : 2/19/2014 4:39:19 PM
    ==================================================

    ==================================================
    Dump File : 021814-21543-01.dmp
    Crash Time : 2/17/2014 8:23:31 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000020
    Parameter 2 : fffffa80`06f1b8a0
    Parameter 3 : fffffa80`06f1b8a0
    Parameter 4 : 00000000`04000010
    Caused By Driver : usbhub.sys
    Caused By Address : usbhub.sys+358f
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021814-21543-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 332,312
    Dump File Time : 2/18/2014 6:34:19 AM
    ==================================================

    ==================================================
    Dump File : 021714-21559-01.dmp
    Crash Time : 2/17/2014 5:03:43 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : fffffa80`02e94f30
    Parameter 2 : 00000000`00000001
    Parameter 3 : fffff800`02e98dac
    Parameter 4 : 00000000`00000002
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021714-21559-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,680
    Dump File Time : 2/17/2014 5:05:12 PM
    ==================================================

    ==================================================
    Dump File : 021614-24414-01.dmp
    Crash Time : 2/16/2014 6:11:47 PM
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : fffffa80`02d438b8
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff880`0f1590e5
    Caused By Driver : nvlddmkm.sys
    Caused By Address : nvlddmkm.sys+980e5
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\021614-24414-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,680
    Dump File Time : 2/16/2014 6:14:07 PM
    ==================================================



    System Information: http://www.mediafire.com/view/5aku9gtbn0gvgin/Lanep82-SysInfo.txt

    Minidump: http://www.mediafire.com/download/4ra7io3c7xl3i6v/Lanep82-Minidump_2-25-14.zip
  10. delete this file: \SystemRoot\system32\DRIVERS\athurx.sys
    or find a update


    Debug session time: Mon Feb 24 18:39:35.688 2014 (UTC - 8:00)
    System Uptime: 0 days 0:39:54.655


    2: kd> lmvm athurx
    start end module name
    fffff880`02804000 fffff880`029e2000 athurx (deferred)
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp: Wed Apr 20 03:07:45 2011 (4DAEB071)
    CheckSum: 001E1C78
    ImageSize: 001DE000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Ask a new question

Read More

Blue Screen Memory Management Windows 7