Random restarts memory dump
- Thread starter Varuna_1
- Start date
Solution
can you follow these steps to create a minidump in c/windows/minidump - http://www.thewindowsclub.com/automatic-memory-dump-settings-windows-8
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
- Jun 12, 2015
- 67,080
- 6,975
- 168,140
can you follow these steps to create a minidump in c/windows/minidump - http://www.thewindowsclub.com/automatic-memory-dump-settings-windows-8
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
Colif :
can you follow these steps to create a minidump in c/windows/minidump - http://www.thewindowsclub.com/automatic-memory-dump-settings-windows-8
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
make a copy of that file and save it to documents
upload the copy from documents to a file sharing site and share it here, someone who can read them will help you fix the errors.
can you also download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
Hi there Colif thanks for the reply I ran who crashed it
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 5/5/2017 3:07:21 AM your computer crashed
crash dump file: C:\Windows\Minidump\050517-20343-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x15F0)
Bugcheck code: 0xA (0xFFFFFFFF8014BA10, 0xFF, 0x1, 0xFFFFFFFF81E23D48)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswsnx.sys
product: Avast Antivirus
company: AVAST Software
description: Avast Virtualization Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: aswsnx.sys (Avast Virtualization Driver, AVAST Software).
Google query: AVAST Software IRQL_NOT_LESS_OR_EQUAL
On Fri 5/5/2017 3:07:21 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x15F0)
Bugcheck code: 0xA (0xFFFFFFFF8014BA10, 0xFF, 0x1, 0xFFFFFFFF81E23D48)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswsnx.sys
product: Avast Antivirus
company: AVAST Software
description: Avast Virtualization Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: aswsnx.sys (Avast Virtualization Driver, AVAST Software).
Google query: AVAST Software IRQL_NOT_LESS_OR_EQUAL
On Sun 4/30/2017 3:34:20 AM your computer crashed
crash dump file: C:\Windows\Minidump\043017-21875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6D8)
Bugcheck code: 0x50 (0xFFFFFFFFB25E3F55, 0x0, 0xFFFFFFFF82420074, 0x0)
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 that cannot be identified at this time.
On Fri 4/28/2017 11:28:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\042817-20593-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1541D)
Bugcheck code: 0xA (0x58, 0xFF, 0x1, 0xFFFFFFFF81DCEF6A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
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:
aswsnx.sys (Avast Virtualization Driver, AVAST Software)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
- Jun 12, 2015
- 67,080
- 6,975
- 168,140
Most recent error was caused by avast so check you have latest version. Also check that you have the latest drivers for motherboard as often virus programs are blamed for lan driver errors. The error blaming ntfs.sys could be caused by sata drivers
If you upload the dump files someone who can read them might get you more direct answers.
If you upload the dump files someone who can read them might get you more direct answers.
Hi so I decided to try another antivirus but still getting memory dump errors. I updated all drivers as well
Windows version: Windows 8 , 6.2, build: 9200
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., A8N-SLI
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 2952318976 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 8/27/2017 3:04:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\082717-18703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6F4)
Bugcheck code: 0xA (0xFFFFFFFFC07A6D78, 0x0, 0x0, 0xFFFFFFFF81A9620F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 8/27/2017 3:04:17 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!HalRequestIpiSpecifyVector+0x889)
Bugcheck code: 0xA (0xFFFFFFFFC07A6D78, 0x0, 0x0, 0xFFFFFFFF81A9620F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Wed 8/23/2017 6:37:39 AM your computer crashed
crash dump file: C:\Windows\Minidump\082317-18375-01.dmp
This was probably caused by the following module: avgsnx.sys (avgSnx+0x250E4)
Bugcheck code: 0x1A (0x31, 0xFFFFFFFF88E4CDD8, 0xFFFFFFFF8FF73000, 0xFFFFFFFFAD49646F)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\avgsnx.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Virtualization Driver
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. This problem might also be caused because of overheating (thermal issue).
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: avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. MEMORY_MANAGEMENT
On Sat 8/19/2017 3:06:37 AM your computer crashed
crash dump file: C:\Windows\Minidump\081917-17765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6D8)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC0014118, 0x8000000, 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 8/18/2017 11:14:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\081817-18046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6D8)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC03B19E8, 0xFFFFFFFF80000000, 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.)
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.
Windows version: Windows 8 , 6.2, build: 9200
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., A8N-SLI
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 2952318976 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 8/27/2017 3:04:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\082717-18703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6F4)
Bugcheck code: 0xA (0xFFFFFFFFC07A6D78, 0x0, 0x0, 0xFFFFFFFF81A9620F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 8/27/2017 3:04:17 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!HalRequestIpiSpecifyVector+0x889)
Bugcheck code: 0xA (0xFFFFFFFFC07A6D78, 0x0, 0x0, 0xFFFFFFFF81A9620F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Wed 8/23/2017 6:37:39 AM your computer crashed
crash dump file: C:\Windows\Minidump\082317-18375-01.dmp
This was probably caused by the following module: avgsnx.sys (avgSnx+0x250E4)
Bugcheck code: 0x1A (0x31, 0xFFFFFFFF88E4CDD8, 0xFFFFFFFF8FF73000, 0xFFFFFFFFAD49646F)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\avgsnx.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Virtualization Driver
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. This problem might also be caused because of overheating (thermal issue).
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: avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. MEMORY_MANAGEMENT
On Sat 8/19/2017 3:06:37 AM your computer crashed
crash dump file: C:\Windows\Minidump\081917-17765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6D8)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC0014118, 0x8000000, 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 8/18/2017 11:14:17 AM your computer crashed
crash dump file: C:\Windows\Minidump\081817-18046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDB6D8)
Bugcheck code: 0x1A (0x41792, 0xFFFFFFFFC03B19E8, 0xFFFFFFFF80000000, 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.)
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.
- Jun 12, 2015
- 67,080
- 6,975
- 168,140
can you go to c:\Windows\minidump and copy the files there to your documents folder
Upload the copies from my documents to a file sharing web site and share a link here
I will get someone to look at them.
whocrashed is blaming AVG but I would suspect its actually a LAN driver, as 2 Anti virus programs in a row won't cause this error without some pushing.
Upload the copies from my documents to a file sharing web site and share a link here
I will get someone to look at them.
whocrashed is blaming AVG but I would suspect its actually a LAN driver, as 2 Anti virus programs in a row won't cause this error without some pushing.
TRENDING THREADS
-
News Bill Gates says Intel has lost its way, hints that 'brave' Pat Gelsinger exited too soon- Started by Admin
- Replies: 43
-
-
Review Nvidia GeForce RTX 5080 Founders Edition review: Incremental gains over the previous generation
- Started by Admin
- Replies: 224
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
-
News Edward Snowden slams Nvidia's RTX 50-series 'F-tier value,' whistleblows on lackluster VRAM capacity
- Started by Admin
- Replies: 107
-
Review Nvidia GeForce RTX 5090 Founders Edition review: Blackwell commences its reign with a few stumbles
- Started by Admin
- Replies: 233
Facebook
Twitter
Instagram