Trying to figure out whats going on with my pc, I keep getting BSOD, also some windows 7 updates will just not install, I keep thinking it might be the HD since its probably one of the oldest components in there, but I've read somewhere it could be a RAM issue as well. I have around 6 .dmp files from the crashes and I'm not sure how to read them, or how to post them here if it would help.
Looking for BSOD dump file help
- Thread starter BlueVyper
- Start date
Solution
- Feb 18, 2010
- 30,566
- 321
- 107,640
use this it will read them in plain text http://www.resplendence.com/whocrashed post the result back .
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 6/23/2015 2:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062315-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004849320, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Mon 6/22/2015 8:50:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062215-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x34D180)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DAB180, 0xFFFFF88003368798, 0xFFFFF88003367FF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 that cannot be identified at this time.
On Wed 6/17/2015 5:28:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061715-22963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A69611, 0xFFFFF8800CF85970, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Tue 6/16/2015 11:05:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061615-20670-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A015EFB200, 0xFBFFF8A015EFB200, 0xFFFFF8A015EFB200)
Error: BAD_POOL_HEADER
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 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 that cannot be identified at this time.
On Wed 6/10/2015 4:48:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061015-23072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x557, 0x10000558FFFFFFFE)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Mon 2/23/2015 10:01:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022315-24585-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x20B8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A6F2098, 0xFFFFF8800A6F18F0, 0xFFFFF88001257D81)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: Avast Software s.r.o.
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates a problem occurred in the NTFS file system.
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 s.r.o.).
Google query: Avast Software s.r.o. NTFS_FILE_SYSTEM
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, Avast Software s.r.o.)
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 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.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 6/23/2015 2:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062315-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004849320, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Mon 6/22/2015 8:50:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062215-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x34D180)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DAB180, 0xFFFFF88003368798, 0xFFFFF88003367FF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 that cannot be identified at this time.
On Wed 6/17/2015 5:28:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061715-22963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A69611, 0xFFFFF8800CF85970, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Tue 6/16/2015 11:05:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061615-20670-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A015EFB200, 0xFBFFF8A015EFB200, 0xFFFFF8A015EFB200)
Error: BAD_POOL_HEADER
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 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 that cannot be identified at this time.
On Wed 6/10/2015 4:48:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061015-23072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x557, 0x10000558FFFFFFFE)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Mon 2/23/2015 10:01:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022315-24585-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x20B8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A6F2098, 0xFFFFF8800A6F18F0, 0xFFFFF88001257D81)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: Avast Software s.r.o.
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates a problem occurred in the NTFS file system.
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 s.r.o.).
Google query: Avast Software s.r.o. NTFS_FILE_SYSTEM
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, Avast Software s.r.o.)
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 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.
Looks like Avast maybe one of the causes.
An 0x24 stop since ntfs.sys is involved can mean its corrupt or it's faulty / maybe ready to die
Download]http://support.kaspersky.com/viruses/utility#TDSSKiller]Download then run tdsskiller see if you've got rootkits[/url]
An 0x24 stop since ntfs.sys is involved can mean its corrupt or it's faulty / maybe ready to die
Download]http://support.kaspersky.com/viruses/utility#TDSSKiller]Download then run tdsskiller see if you've got rootkits[/url]
TRENDING THREADS
-
[SOLVED] Is it safe to use a recapped PSU for a long time ?- Started by zwtch_17
- Replies: 5
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 3K
-
-
News Microsoft updates Windows 11 24H2 requirements, CPU must support SSE4.2 or the OS will not boot- Started by Admin
- Replies: 19
Facebook
Twitter
Instagram