Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Memory Management, STOP 0x0000008E BSODs


  • Please log in to reply
11 replies to this topic

#1 nov4k

nov4k

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 13 January 2012 - 12:40 AM

Ok, so I'm pretty sure I caused the issue, please help me fix it!

Computer was running fast and smooth. No issues what so ever. I had 2 4Gb memory sticks in slots 1 and 2 of my motherboard. I was stupid and decided to put some old memory I had laying around in slots 2 and 3. Of course the new added memory was not the same and when I turned on the computer I heard a loud noise coming from the power supply and the computer was running tremendously slower! I then removed the new added memory and when I turned the computer back on the noise was gone but the computer was still running super slow! The OS takes forever to load and when it finally does load, all applications run really slow. Even after clicking on the start menu, it takes about 20-30 seconds before it pops up. The computer also now randomly crashes. I have gotten 2 different BSODs. The first one was a Memory Management and second STOP 0x0000008E. I ran a memtest86 and it passed all tests, saying my memory was fine. I'm not really sure what to do now, I think I may have messed up the bios settings some how. I was stupid, please help!

OS: Windows 7 Professional (build 7600)
MB: Gigabyte Technology Co., Ltd. GA-MA785GM-US2H
BIOS: Award Software International, Inc. F5 09/16/2009
CPU: 2.80 gigahertz AMD Athlon II X2 240
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
64-bit ready
RAM: 2x Ultra (ULT40089) 2048MB PC2-5300 DDR2 667MHz

RAM I added to the open slots was 2 Corsair XMS2 1024MB DDR2 (5-5-5-12/800MHz/1024MB/XMS2-6400/1.90V/ver5.1)

Thank you,
Jason

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,398 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:41 AM

Posted 13 January 2012 - 10:22 AM

I would go into the BIOS...and reset to factory defaults, save the changes.

System will reboot, see if there is improvement.

Louis

#3 nov4k

nov4k
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 13 January 2012 - 08:25 PM

Hey I actually forgot to mention I rebooted the bios to factory defaults already. Still really bogged down. I'm not to sure what's going on. I also installed a few windows updates after the mishap as well but I don't think that did anything positive or negative to the system. I used to be able to hit the reset button and computer and os would be back up and running fast and smooth within 60-90 seconds. Now it takes like 10 minutes to reboot...and even after all the startup programs are running I get lucky if I can load chrome to web browse...

#4 nov4k

nov4k
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 13 January 2012 - 08:42 PM

Also just booted it up tonight, before the os loaded up all startup items the system crashed, this time it showed a 0x000000C5 bsod

Sigh,
Jason

#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,398 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:41 AM

Posted 14 January 2012 - 08:34 PM

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt, copy all content and paste it into your next reply.

Louis

#6 nov4k

nov4k
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 19 January 2012 - 12:39 AM

==================================================
Dump File : 011312-79685-01.dmp
Crash Time : 1/13/2012 8:44:16 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82b3a067
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4686b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+4686b
Stack Address 1 : ntkrnlpa.exe+120067
Stack Address 2 : ntkrnlpa.exe+b6ff2
Stack Address 3 : ndis.sys+9edf
Computer Name :
Full Path : C:\Windows\Minidump\011312-79685-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,552
==================================================

==================================================
Dump File : 122011-124675-01.dmp
Crash Time : 12/20/2011 3:58:47 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82a53e83
Parameter 3 : 0xa077fa74
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+3ee83
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+3ee83
Stack Address 1 : ntkrnlpa.exe+1e3022
Stack Address 2 : ntkrnlpa.exe+219c22
Stack Address 3 : ntkrnlpa.exe+23e54c
Computer Name :
Full Path : C:\Windows\Minidump\122011-124675-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121911-126969-01.dmp
Crash Time : 12/19/2011 11:02:38 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82b26eff
Parameter 3 : 0xa0bc3abc
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+11feff
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+11feff
Stack Address 1 : ntkrnlpa.exe+253206
Stack Address 2 : ntkrnlpa.exe+26ee7c
Stack Address 3 : ntkrnlpa.exe+27f720
Computer Name :
Full Path : C:\Windows\Minidump\121911-126969-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121911-98358-01.dmp
Crash Time : 12/19/2011 10:21:21 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82b71795
Parameter 3 : 0xa1a57a54
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+120795
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+120795
Stack Address 1 : ntkrnlpa.exe+11f8aa
Stack Address 2 : ntkrnlpa.exe+221d70
Stack Address 3 : ntkrnlpa.exe+221b15
Computer Name :
Full Path : C:\Windows\Minidump\121911-98358-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121611-252425-01.dmp
Crash Time : 12/16/2011 9:55:20 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000022
Parameter 2 : 0x01000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+aca2e
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+9dee2
Stack Address 1 : ntkrnlpa.exe+11f144
Stack Address 2 : ntkrnlpa.exe+a234b
Stack Address 3 : ntkrnlpa.exe+23e496
Computer Name :
Full Path : C:\Windows\Minidump\121611-252425-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121611-54459-01.dmp
Crash Time : 12/16/2011 7:15:31 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xd08ec033
Parameter 2 : 0x00000000
Parameter 3 : 0x82f74795
Parameter 4 : 0x00000002
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+fe4b
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+85a23
Stack Address 1 : ntkrnlpa.exe+465d8
Stack Address 2 : ntkrnlpa.exe+120795
Stack Address 3 : ntkrnlpa.exe+11f8aa
Computer Name :
Full Path : C:\Windows\Minidump\121611-54459-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121311-112632-01.dmp
Crash Time : 12/13/2011 6:03:08 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82f227ff
Parameter 3 : 0xa059d65c
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+1207ff
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+1207ff
Stack Address 1 : ntkrnlpa.exe+11f8aa
Stack Address 2 : fltmgr.sys+200f2
Stack Address 3 : fltmgr.sys+20df4
Computer Name :
Full Path : C:\Windows\Minidump\121311-112632-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121311-92555-01.dmp
Crash Time : 12/13/2011 4:19:22 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82f2e26e
Parameter 3 : 0x8f99eae4
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+12026e
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+12026e
Stack Address 1 : ntkrnlpa.exe+2243f9
Stack Address 2 : ntkrnlpa.exe+22424d
Stack Address 3 : ntkrnlpa.exe+23c9c4
Computer Name :
Full Path : C:\Windows\Minidump\121311-92555-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121211-115705-01.dmp
Crash Time : 12/12/2011 6:20:31 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xaabf79f6
Parameter 2 : 0x00000000
Parameter 3 : 0x82f2c795
Parameter 4 : 0x00000002
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+85a23
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+85a23
Stack Address 1 : ntkrnlpa.exe+465d8
Stack Address 2 : ntkrnlpa.exe+120795
Stack Address 3 : ntkrnlpa.exe+11f8aa
Computer Name :
Full Path : C:\Windows\Minidump\121211-115705-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121211-130229-01.dmp
Crash Time : 12/12/2011 3:38:58 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xd08ec033
Parameter 2 : 0x00000000
Parameter 3 : 0x82f3a795
Parameter 4 : 0x00000002
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+85a23
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+85a23
Stack Address 1 : ntkrnlpa.exe+465d8
Stack Address 2 : ntkrnlpa.exe+120795
Stack Address 3 : ntkrnlpa.exe+11f8aa
Computer Name :
Full Path : C:\Windows\Minidump\121211-130229-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

==================================================
Dump File : 121111-84037-01.dmp
Crash Time : 12/11/2011 9:26:49 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041287
Parameter 2 : 0x0127729c
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+bccfc
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+85a23
Stack Address 1 : ntkrnlpa.exe+465d8
Stack Address 2 : ntkrnlpa.exe+a9e82
Stack Address 3 : ntkrnlpa.exe+817b7
Computer Name :
Full Path : C:\Windows\Minidump\121111-84037-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,456
==================================================

#7 Layback Bear

Layback Bear

  • Members
  • 1,880 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Ohio
  • Local time:12:41 AM

Posted 19 January 2012 - 09:08 AM

Nov4k have you got your computer fixed? If not I would remove the new ram. Their are many opinion on mixing ram and mine is don't mix rams. If it was my computer I would install matched ram. Be sure and check the specs on the volts, 1.9 seams high to me.

#8 nov4k

nov4k
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 19 January 2012 - 09:32 AM

Oh I immediately removed the new RAM. I only had it in there for literally one boot up. I new something was wrong so I took it out. It left residual effects though and I'm not sure how to fix it. I will point out that I just installed a few Windows updates and the computer has been running overnight for quite some time now and it is running smooth as butter right now. I will restart it and see if it goes back to the normal sluggishness it has been.

#9 Chase_Wheeler

Chase_Wheeler

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:12:41 AM

Posted 19 January 2012 - 09:53 AM

I would recommend running the program "Who Crashed", its really great for tracking what caused the bluescreen, just yesterday I was removing ZeroAccess and kept getting these bluescreens, come to find out after running Who Crashed it was the customers STOPzilla causing it, booted up into safemode autoruns'd it out and no more bluescreens.

#10 nov4k

nov4k
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:41 AM

Posted 19 January 2012 - 10:36 PM

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.03
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: NORMAN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon™ II X2 240 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 3487031296 total
VM: 2147352576, free: 1973780480



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 1/19/2012 6:46:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011912-102851-01.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x5F5)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82B39A18, 0x0, 0xFFFFFFFF82B39A18)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This indicates that a pool header is corrupt.
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software BAD_POOL_HEADER




On Thu 1/19/2012 6:46:53 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x5F5)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82B39A18, 0x0, 0xFFFFFFFF82B39A18)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This indicates that a pool header is corrupt.
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software BAD_POOL_HEADER




On Sat 1/14/2012 1:40:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011312-79685-01.dmp
This was probably caused by the following module: netr28u.sys (netr28u+0x3C9D3)
Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF82B3A067)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\netr28u.sys
product: Ralink 802.11n Wireless Adapters
company: Ralink Technology Corp.
description: Ralink 802.11n Wireless Adapter Driver
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: netr28u.sys (Ralink 802.11n Wireless Adapter Driver, Ralink Technology Corp.).
Google query: netr28u.sys Ralink Technology Corp. DRIVER_CORRUPTED_EXPOOL




On Tue 12/20/2011 8:53:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-124675-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3EE83)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A53E83, 0xFFFFFFFFA077FA74, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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.


On Tue 12/20/2011 3:55:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121911-126969-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11FEFF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B26EFF, 0xFFFFFFFFA0BC3ABC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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.


On Tue 12/20/2011 3:17:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121911-98358-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120795)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B71795, 0xFFFFFFFFA1A57A54, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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.


On Sat 12/17/2011 2:47:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121611-252425-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9DEE2)
Bugcheck code: 0x19 (0x22, 0x1000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
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.
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 12/17/2011 12:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121611-54459-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x50 (0xFFFFFFFFD08EC033, 0x0, 0xFFFFFFFF82F74795, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Tue 12/13/2011 10:59:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-112632-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2BCA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F227FF, 0xFFFFFFFFA059D65C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Tue 12/13/2011 9:15:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-92555-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x12026E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F2E26E, 0xFFFFFFFF8F99EAE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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.


On Mon 12/12/2011 11:16:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121211-115705-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x50 (0xFFFFFFFFAABF79F6, 0x0, 0xFFFFFFFF82F2C795, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 12/12/2011 8:34:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121211-130229-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x50 (0xFFFFFFFFD08EC033, 0x0, 0xFFFFFFFF82F3A795, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 12/12/2011 2:22:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-84037-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9AEA)
Bugcheck code: 0x1A (0x41287, 0x127729C, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

13 crash dumps have been found and analyzed. 4 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:

netr28u.sys (Ralink 802.11n Wireless Adapter Driver, Ralink Technology Corp.)

aswtdi.sys (avast! TDI Filter Driver, AVAST Software)

aswsp.sys (avast! self protection module, AVAST Software)

aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

#11 Chase_Wheeler

Chase_Wheeler

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:12:41 AM

Posted 20 January 2012 - 10:56 AM

It appears that your crashes are software related, from your Avast! and your Ralink (probably linksys or cisco).

Its possible that the Avast! program is corrupted, and needs to be installed, or possibly a virus is messing with Avasts drivers.

Here is what I would do, but don't do it until another forumer comes and verifies this because its kindof some hinky waters, if its a virus when you do what I would do the virus may go full blown.

Personally (and please take this warning seriously, if you do this its at your own risk)

Programs needed for what I would do:
CCleaner
Newest Avast installation
Avast Uninstall tool
Newest driver for your network adapter

Steps:
Uninstall your network card driver
Uninstall Avast with the uninstall tool
Restart your comptuer
Run the CCleaner registry tool (BACK UP ALL CHANGES!!!)
Reinstall Avast
Reinstall your network card driver


Then hopefully you should be running fine.


Like I said please wait for another forumer to come and verify this post. I would be comfortable doing it on my own system or one that I am physically working with, but I am out of my comfort zone telling you just because if its a virus it could go fullblown when you take out Avast.

#12 hamluis

hamluis

    Moderator


  • Moderator
  • 55,398 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:41 AM

Posted 20 January 2012 - 11:11 AM

<<Here is what I would do, but don't do it until another forumer comes and verifies this because its kindof some hinky waters, if its a virus when you do what I would do the virus may go full blown.

Personally (and please take this warning seriously, if you do this its at your own risk)>>

If it's a malware situation...then this topic should be moved to the Am I Infected forum.

As for running Ccleaner's registry function, this website does not favor such.

Bleeping Computer DOES NOT recommend the use of registry cleaners/optimizers for several reasons:
  • Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable.

    The Windows registry is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component because it is where Windows "remembers" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry.
  • Not all registry cleaners are created equal. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work.
  • Not all registry cleaners create a backup of the registry before making changes. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE making any changes to the registry.
  • Improperly removing registry entries can hamper malware disinfection and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable to removal tools.
  • The usefulness of cleaning the registry is highly overrated and can be dangerous. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results".

Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily or incorrectly could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great.
Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users