Blue screen error :PAGE_FAULT_IN_NONPAGED_AREA in windows 7

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by msauro33, Feb 2, 2012.

  1. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12
    Original title:"BSOD Windows 7. "
    I am running a HP Pavilion 6 with AMD processor. I am getting BSOD at radom times. I was able to read the blue screen with the program blue scree viewer. I kept seeing ntoskrnl.exe this is a problem and PAGE_FAULT_IN_NONPAGED_AREA. That was the most common fault that would stop the crash the computer and give me a BSOD. HP says to restore the system. Is there another fix before I have to start all over and reinstall all of my software?

    012812-40092-01.dmp 1/28/2012 9:06:58 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffc00`00000007 00000000`00000000 fffff800`02cba1ab 00000000`00000007 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\012812-40092-01.dmp 2 15 7601 274,528


    I got this one too. I am not sure if the above problem is causing other problems.

    013012-23400-01.dmp 1/30/2012 2:41:17 PM DRIVER_CORRUPTED_EXPOOL 0x000000c5 fffff280`04eef988 00000000`00000002 00000000`00000001 fffff800`02e05617 athrx.sys athrx.sys+2a2b5 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\013012-23400-01.dmp 2 15 7601 274,528


    013112-28142-01.dmp 1/31/2012 12:33:53 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff0a0`0f1fa748 00000000`00000000 fffff800`02dafb05 00000000`00000007 AVGIDSDriver.Sys AVGIDSDriver.Sys+147ea x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\013112-28142-01.dmp 2 15 7601 274,528


    If anyone can help that would be great. I really don't want to start all over.

    I added a screen shot. I am not sure if it will post or not. If anyone can help out, that would be great.



    [​IMG]
     
  2. Saltgrass

    Saltgrass Excellent Member Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    14,365
    What I can tell from your information, it seems to be a memory related problem. Whether the memory is having a problem, or a driver is hard to tell.

    We need the minidump file because we look at other things beside just the basic cause of the crash..... If you could just attach it using the paperclip in the advanced replies window.

    Some folks here can even check the settings on your memory to see if it looks correct. The sticky explains how to get some of that info.
     
    1 person likes this.
  3. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12
  4. Mike

    Mike Windows Forum Admin Staff Member Premium Supporter Microsoft MVP

    Joined:
    Jul 22, 2005
    Messages:
    8,468
    Location:
    New York, USA
    Hi msauro33,

    Please allow me to welcome you to the website. The crash is likely caused by Atheros Extensible Wireless LAN driver. Go to your computer manufacturer's website and download and install the latest updates for your wireless card. Lots of people mention blue screens caused by this device.

    You should seriously consider going to the support site for your computer and performing updates. If you assembled your own system, or do not have support from the manufacturer, what you need to do is assemble an inventory list of potentially outdated drivers and software and go from there. However, right now you should eliminate the possibility of it being your wireless LAN driver and either disable it temporarily in Device Manager (use a wired connection) or update it.

    Other members may have further analysis for you.

    See the report below:

    On Tue 1/31/2012 5:32:26 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\013112-28142-01.dmp
    uptime: 09:38:39
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFF0A00F1FA748, 0x0, 0xFFFFF80002DAFB05, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Mon 1/30/2012 7:40:12 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\013012-23400-01.dmp
    uptime: 04:11:50
    This was probably caused by the following module: athrx.sys (athrx+0x2A2B5)
    Bugcheck code: 0xC5 (0xFFFFF28004EEF988, 0x2, 0x1, 0xFFFFF80002E05617)
    Error: DRIVER_CORRUPTED_EXPOOL
    Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys .
    Google query: athrx.sys DRIVER_CORRUPTED_EXPOOL




    On Sun 1/29/2012 2:05:20 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\012812-40092-01.dmp
    uptime: 1 day, 00:23:01
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000007, 0x0, 0xFFFFF80002CBA1AB, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 1/28/2012 1:41:52 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\012712-31293-01.dmp
    uptime: 22:23:51
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    [HR][/HR]Conclusion[HR][/HR]
    4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    athrx.sys

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
     
  5. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12
    I checked the drive like you suggest. It is up-to-date. I can give you a few more mini dumps.

    I have put them all in a zip file. View attachment 012111-70886-01.zip

    Please let me know what else you find.
     
  6. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,904
    The dumps in your last upload where all pre 30 Nov 2011. That's 2 months plus old. If that is all that is in your dumpfolder nw then delete them. Please re upload the latest. Also to help us to help you (here comes my canned speech!!) :D :

    Please see: How to ask for help with a BSOD problem Following Method 2:
    Download
    and run the SF Diagnostics Tool. Right click the SF Diag tool and select Run as Administrator before running. When the reports have been created, zip them up and attach to a post.

    Download and run CPU-Z. Take screenshots**/snips of the CPU tab, Mainboard tab, Memory tab and all the slot #'s under the SPD tab.
    Go to Post Reply, click on the Go Advanced button and attach the screenshots**/snips to your post for all the RAM experts to see by using the paper clip you will find on the top toolbar. Do not zip them up.
    **
    If screenshots, please crop.

    Also see: http://windows7forums.com/blue-scre...lp-us-help-you-filling-your-system-specs.html

    When attaching dmp files, PLEASE put them in a single zipped folder

    It might be boring reading, but it does help!
     
  7. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12
    1 person likes this.
  8. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,904
    That's better!! Can you now run through the other stuff in my last post?

    Not sure who's going to win here in dear old Blighty. Bed or Bowie. If Bowie wins I'll get you a quick answer otherwise tomorrow am unless any body else jumps in.
     
  9. Mike

    Mike Windows Forum Admin Staff Member Premium Supporter Microsoft MVP

    Joined:
    Jul 22, 2005
    Messages:
    8,468
    Location:
    New York, USA


    David Bowie?
     
  10. Mike

    Mike Windows Forum Admin Staff Member Premium Supporter Microsoft MVP

    Joined:
    Jul 22, 2005
    Messages:
    8,468
    Location:
    New York, USA
    [FONT=Segoe UI, Arial]Seeing a lot of memory errors here. You may want to run memtest86+ (although not a popular option -- it is an option). You may very well have bad RAM.

    On Thu 2/2/2012 2:02:39 PM GMT your computer crashed

    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\020212-44319-01.dmp
    uptime: 21:14:42
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000007, 0x0, 0xFFFFF80002CB01AB, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 1/31/2012 5:32:26 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\013112-28142-01.dmp
    uptime: 09:38:39
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFF0A00F1FA748, 0x0, 0xFFFFF80002DAFB05, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Mon 1/30/2012 7:40:12 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\013012-23400-01.dmp
    uptime: 04:11:50
    This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x2A2B5)
    Bugcheck code: 0xC5 (0xFFFFF28004EEF988, 0x2, 0x1, 0xFFFFF80002E05617)
    Error: [FONT=Segoe UI, Arial]DRIVER_CORRUPTED_EXPOOL[/FONT]
    Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys .
    Google query: [FONT=Segoe UI, Arial]athrx.sys DRIVER_CORRUPTED_EXPOOL[/FONT]


    [/FONT]

    [FONT=Segoe UI, Arial]On Sun 1/29/2012 2:05:20 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\012812-40092-01.dmp
    uptime: 1 day, 00:23:01
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000007, 0x0, 0xFFFFF80002CBA1AB, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sat 1/28/2012 1:41:52 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\012712-31293-01.dmp
    uptime: 22:23:51
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC10)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Wed 1/25/2012 3:16:37 AM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\012412-19328-01.dmp
    uptime: 12:37:52
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x1A (0x411, 0xFFFFF68000021908, 0xA6100000BD5F1886, 0xFFFFF28000021909)
    Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 1/24/2012 2:37:53 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\012412-25896-01.dmp
    uptime: 1 day, 00:25:28
    This was probably caused by the following module: [FONT=Segoe UI, Arial]athrx.sys[/FONT] (athrx+0x2F2AC)
    Bugcheck code: 0x50 (0xFFFFF8001D28A7C8, 0x1, 0xFFFFF80002CD518F, 0x2)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys .
    Google query: [FONT=Segoe UI, Arial]athrx.sys PAGE_FAULT_IN_NONPAGED_AREA[/FONT]


    [/FONT]

    [FONT=Segoe UI, Arial]On Mon 1/23/2012 1:57:09 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\012312-25303-01.dmp
    uptime: 6 days, 14:05:44
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFBFFFFFFFFFF, 0x0, 0xFFFFF80002CD1BB6, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Mon 1/16/2012 11:47:22 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011612-19063-01.dmp
    uptime: 1 day, 00:21:11
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000007, 0x0, 0xFFFFF80002C9E1AB, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sun 1/15/2012 11:25:16 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011512-22027-01.dmp
    uptime: 08:10:51
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000003, 0x1, 0xFFFFF80002C90348, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sun 1/15/2012 3:10:50 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011512-27378-01.dmp
    uptime: 1 day, 16:26:50
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000003, 0x1, 0xFFFFF80002C93348, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 1/13/2012 10:43:09 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011312-22417-01.dmp
    uptime: 06:14:22
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000003, 0x1, 0xFFFFF80002C90348, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 1/13/2012 4:27:52 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011312-26208-01.dmp
    uptime: 02:36:48
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000003, 0x1, 0xFFFFF80002C96348, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 1/13/2012 1:50:09 PM GMT your computer crashed
    crash dump file: C:\Users\Mike\Downloads\011312-31106-01\011312-31106-01.dmp
    uptime: 15:45:26
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFC0000000003, 0x1, 0xFFFFF80002CA6348, 0x7)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]The following dump files were found but could not be read. These files may be corrupt:
    [/FONT][FONT=Segoe UI, Arial]C:\Users\Mike\Downloads\011312-31106-01\021212-44319-01.dmp
    [/FONT][FONT=Segoe UI, Arial]
    [/FONT]

    [FONT=Segoe UI, Arial][HR][/HR]Conclusion[HR][/HR][/FONT]
    [FONT=Segoe UI, Arial]On your computer a total of 15 crash dumps have been found. Only 14 could be analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    [FONT=Segoe UI, Arial]athrx.sys [/FONT]

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
    [/FONT]
     
  11. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,904
    The one and only! Did you think I meant a bloke who stole a knife design??? :D My life Hero from the tender age of 14. (Or from the tender age of three I was hooked to a Machine. (Our tom, A tad later)
     
    Last edited: Feb 3, 2012
    1 person likes this.
  12. Mike

    Mike Windows Forum Admin Staff Member Premium Supporter Microsoft MVP

    Joined:
    Jul 22, 2005
    Messages:
    8,468
    Location:
    New York, USA
    You are still getting a DRIVER_CORRUPTED_EXPOOL error on athrx.sys but I am also seeing a MEMORY_MANAGEMENT error from the Windows kernel. This indicates, to me at least, that this driver is assigning memory to the wrong area, or you have a memory problem. For some reason, athrx.sys keeps coming up, but my method is very likely not as meticulous as Elmer. I would suggest still viewing athrx.sys as suspect, even though you have the latest driver. The reason being: There seems to be countless mentions of BSOD's related to this file all over the net. There is also a clear instance whereas the driver itself is causing the crash. Maybe even re-install the driver.
     
  13. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12

    I will do the other stuff you have asked and get you a report. I kept seeing the same ntoskrnl.exe problem in the dumps. Does that mean anything?
     
  14. Mike

    Mike Windows Forum Admin Staff Member Premium Supporter Microsoft MVP

    Joined:
    Jul 22, 2005
    Messages:
    8,468
    Location:
    New York, USA
    When invalid system memory is referenced by Windows, this is almost always caused by a bad driver. It is the reason why the system is crashing, but ntoskrnl.exe is being reported, as this is the Windows 7 operating system kernel executable (for all intents and purposes it is the foundation of your operating system). The kernel references memory based on what system-level device drivers tell it do and this is what creates most crash conditions.
     
    1 person likes this.
  15. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,904
    I'll agree with Mike there. ntoskrnl.exe is always running. Something dies and ntoskrnl.exe gets the blame! Bit like pointing your finger at your pal for eating the last cookie! You really need to find who ate the last but one cookie.

    With those rather sad words of pseudo wisdom, I shall retire to my bed chamber for a good snorafookling. :p
     
  16. msauro33

    msauro33 New Member

    Joined:
    Feb 2, 2012
    Messages:
    12
    I tried to run that sf tool. It worked on a couple of buttons, but the rest the program didn't work. Here is what it says. View attachment Seven Forums.zip
    I am going to run the other folders.

    @mike, ok that is good to know. I am just seeing the result not the problem.


    @elmer,

    Here are the other files that you requested and screen shots. Caches.PNG Memory.PNG Graphics.PNG View attachment RAMMon - SPD Info.txt Mainboard.PNG SPD2.PNG CPU.PNG SPD1.PNG
     
    Last edited: Feb 3, 2012

Share This Page