J
jen_ang92
Guest
Hello,
My Windows 10 has recently, and out of the blue, started crashing with BSoD's that have different error codes each time. This first started on Sunday.
System Info:
Windows version: Windows 10 , 10.0, Version 1903, Build: 18362
Windows Dir: C:\WINDOWS
Hardware: 20ARS1R703, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 12555984896 bytes (11.7GB)
I have tried a number of things, to no avail:
- Virus scan and did not find anything.
- SFC /SCANNOW that only worked in Safe Mode, which said: Windows Resource Protection found corrupt files but was unable to fix some of them.
- I tried CHKDSK which didn't seem to help.
- I tried updated the iaStorA.sys Driver.
- Tried to re-set and Fresh Start my computer, both of which I was unable to do.
Aside from the BSoD's, my Chrome Browser also keeps crashing and my audio no longer works.
I used WhoCrashed, and this is what came back:
On Mon 2019-11-18 5:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-10734-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000002)
Bugcheck code: 0x50 (0xFFFFFFFFC1F60D7E, 0x2, 0xFFFFD5E995C5D566, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Mon 2019-11-18 5:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: Unknown (0x0000000000000002)
Bugcheck code: 0x50 (0xFFFFFFFFC1F60D7E, 0x2, 0xFFFFD5E995C5D566, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Mon 2019-11-18 5:32:36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xDE (0x2, 0xFFFFCC0E36DA0A58, 0xFFFFCC0E36DA0A58, 0x200046F518C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 2019-11-18 4:04:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-10234-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8052103712C, 0xFFFF8F88C7D01700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
On Sun 2019-11-17 6:03:51 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-9265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x139 (0x3, 0xFFFFDD03E842E140, 0xFFFFDD03E842E098, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 2019-11-17 5:27:57 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-8453-01.dmp
This was probably caused by the following module: Unknown (0xFFFFDF8583348A30)
Bugcheck code: 0x1A (0x782, 0xFFFF9E0D6EBF0590, 0xFFFF8D8766F00000, 0xFFFFDF8583348A30)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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.
Google query: MEMORY_MANAGEMENT
On Sun 2019-11-17 2:54:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80672573358, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
Not sure what else to do as it keeps crashing whenever I try to fix it!
Continue reading...
My Windows 10 has recently, and out of the blue, started crashing with BSoD's that have different error codes each time. This first started on Sunday.
System Info:
Windows version: Windows 10 , 10.0, Version 1903, Build: 18362
Windows Dir: C:\WINDOWS
Hardware: 20ARS1R703, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 12555984896 bytes (11.7GB)
I have tried a number of things, to no avail:
- Virus scan and did not find anything.
- SFC /SCANNOW that only worked in Safe Mode, which said: Windows Resource Protection found corrupt files but was unable to fix some of them.
- I tried CHKDSK which didn't seem to help.
- I tried updated the iaStorA.sys Driver.
- Tried to re-set and Fresh Start my computer, both of which I was unable to do.
Aside from the BSoD's, my Chrome Browser also keeps crashing and my audio no longer works.
I used WhoCrashed, and this is what came back:
On Mon 2019-11-18 5:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-10734-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000002)
Bugcheck code: 0x50 (0xFFFFFFFFC1F60D7E, 0x2, 0xFFFFD5E995C5D566, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Mon 2019-11-18 5:43:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: Unknown (0x0000000000000002)
Bugcheck code: 0x50 (0xFFFFFFFFC1F60D7E, 0x2, 0xFFFFD5E995C5D566, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Mon 2019-11-18 5:32:36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xDE (0x2, 0xFFFFCC0E36DA0A58, 0xFFFFCC0E36DA0A58, 0x200046F518C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 2019-11-18 4:04:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-10234-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8052103712C, 0xFFFF8F88C7D01700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
On Sun 2019-11-17 6:03:51 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-9265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x139 (0x3, 0xFFFFDD03E842E140, 0xFFFFDD03E842E098, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 2019-11-17 5:27:57 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-8453-01.dmp
This was probably caused by the following module: Unknown (0xFFFFDF8583348A30)
Bugcheck code: 0x1A (0x782, 0xFFFF9E0D6EBF0590, 0xFFFF8D8766F00000, 0xFFFFDF8583348A30)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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.
Google query: MEMORY_MANAGEMENT
On Sun 2019-11-17 2:54:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111719-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80672573358, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
Not sure what else to do as it keeps crashing whenever I try to fix it!
Continue reading...