RLMadd
Posts: 30 +0
I've been having BSOD issues for the last several months, It has been terribly annoying but I'm doing my best to get to the bottom of it without having to spend extensive amounts of money on it. I analyzed my dump folder using a program called "Who Crashed" and there have been three different issues I'll list them for anyone interesting in taking a look.
crash dump file: C:\Windows\Minidump\021313-26020-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]hal.dll[/FONT] (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80059E8028, 0xB6344000, 0xA8000145)
Error: [FONT=Segoe UI]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
crash dump file: C:\Windows\Minidump\030413-28688-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]ntoskrnl.exe[/FONT] (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]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 that cannot be identified at this time.
crash dump file: C:\Windows\Minidump\022613-27612-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]wdf01000.sys[/FONT] (Wdf01000+0xD737)
Bugcheck code: 0xD1 (0xFFFFFA804EAEF4E0, 0x2, 0x1, 0xFFFFF88000ED8737)
Error: [FONT=Segoe UI]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]Microsoft Corporation[/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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.
crash dump file: C:\Windows\Minidump\021313-26020-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]hal.dll[/FONT] (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80059E8028, 0xB6344000, 0xA8000145)
Error: [FONT=Segoe UI]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
crash dump file: C:\Windows\Minidump\030413-28688-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]ntoskrnl.exe[/FONT] (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]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 that cannot be identified at this time.
crash dump file: C:\Windows\Minidump\022613-27612-01.dmp
This was probably caused by the following module: [FONT=Segoe UI]wdf01000.sys[/FONT] (Wdf01000+0xD737)
Bugcheck code: 0xD1 (0xFFFFFA804EAEF4E0, 0x2, 0x1, 0xFFFFF88000ED8737)
Error: [FONT=Segoe UI]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI]Microsoft Corporation[/FONT]
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
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.
