There aren't any .dmp files to anlayse, so I can't offer any advice except to state that:
0x50's are usually memory problems
0x124's are hardware-related.
If you get a BSOD during the video driver stress test, then uninstall all drivers completely, then use this tool:
Drivers - Clean Left over Files after Uninstalling
Run Windows Update and install the driver offered. Monitor for BSOPD's but do NOT update the driver further.
I just want to make sure I understand your request. You want me to uninstall my Nvidia driver completely using this tool and only install the Microsoft related video card drivers right? None of the Nvidia drivers?
I did get a BSOD while using the video card tester TechPowerUp GPU-Z and the logs were listed in my previous thread.
However, Display driver nvlddmkm stopped responding and has successfully recovered. happend out of game without the TechPowerUp GPU-Z on, and it only causes my monitor to turn black for about five seconds and then states the error display driver nvlddmkm stopped responding and has successfully recovered.
Last edited by jay11; 07 Jun 2014 at 22:23. Reason: updated convo
Request complete. I will let you know If I receive any further BSODs within the next week or so.
Thanks for all of your help!
Just got another BSOD today. Below are the new whocrashed results and attached is the new SF logs.
On Wed 6/11/2014 8:04:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061114-19422-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF88054752010, 0x0, 0xFFFFF800037E4CDC, 0x5)
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 Wed 6/11/2014 8:04:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x498B8)
Bugcheck code: 0x50 (0xFFFFF88054752010, 0x0, 0xFFFFF800037E4CDC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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.
On Sat 6/7/2014 10:53:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-16816-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF88028708010, 0x0, 0xFFFFF800037ACCDC, 0x2)
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 Sat 5/31/2014 9:41:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-17206-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8803F2B2010, 0x0, 0xFFFFF800037ABCDC, 0x2)
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 Sun 5/25/2014 8:51:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052514-18548-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88004AFE6E4)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF800034F6103)
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.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Sat 5/24/2014 6:04:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-24492-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80091D0028, 0xB4672000, 0xC5000145)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Thu 5/22/2014 10:38:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-17394-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008A4B028, 0xB64EC000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Sun 5/11/2014 1:56:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051014-18205-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008AB3028, 0xB4002000, 0xF3000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Wed 4/30/2014 2:55:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042914-27019-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC50122E10, 0xFFFFFFFFC000009C, 0x14B14880, 0xFFFFF8A0245C2000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Received another BSOD attached is the new SF and below is the new who crashed can someone help please?
On Mon 6/16/2014 2:43:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-20997-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034C2F1F, 0xFFFFF88008474F90, 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 Mon 6/16/2014 2:43:19 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034C2F1F, 0xFFFFF88008474F90, 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I thought the .DMP files were listed in the SF "zip file" that I have attached to the above threads?
I went into my dump folder and it looks like they are the same files listed in the SF attached to the above threads?
Last edited by jay11; 17 Jun 2014 at 03:02.
What should I do? =( I just got another BSOD today WHO crashed and SF attached to this thread.
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 6/24/2014 1:29:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062314-16910-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80091D9028, 0xB6004000, 0xA7000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Tue 6/24/2014 1:29:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80091D9028, 0xB6004000, 0xA7000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
Quote