![]() |
|
24 May 2014 | #1 |
|
BSOD WhoCrashed states 0x124 (0x0, 0xFFFFFA80091D0028, 0xB4672000, 0xC
Hello,
I keep getting BSOD when playing Diablo3 or Starcraft 2. I have not seen the BSOD happen anytime other then when I am playing those two games. I have tried to run SFC and got the Windows Resource Protection did not find any integrity violations. I have attached the SF diagnostic results and also attached myWhocrashed info Sytem Information windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: M68MT-S2, Gigabyte Technology Co., Ltd. CPU: AuthenticAMD AMD Phenom(tm) II X6 1100T Processor AMD586, level: 16 6 logical processors, active mask: 63 RAM: 8588324864 total VM: 2147352576, free: 1924096000 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 Sat 5/24/2014 6:04:07 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, 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. |
My System Specs![]() |
. |
|
24 May 2014 | #2 |
|
bump
|
My System Specs![]() |
24 May 2014 | #3 |
![]() |
0x124's typically point to hardware errors. 0x7E's could be RAM issues.
To get to the bottom of this, you will need to stress test the major components. RAM: run a minimum of 8 passes, no less RAM - Test with Memtest86+ Video: Graphics Card Problems - Diagnose CPU: CPU - Stress Test Using IntelBurnTest |
My System Specs![]() |
. |
|
24 May 2014 | #4 |
|
Thanks for the advice. After reading over a lot of threads on these forums I tried this :
NVIDIA Drivers - Avoid Problems I have not received a BSOD today at all.. I Will reports back in 2-3 days to determine if this has fixed it. Thanks! |
My System Specs![]() |
24 May 2014 | #5 |
![]() |
![]() |
My System Specs![]() |
25 May 2014 | #6 |
|
Damn, I was running smooth all day yesterday, which is a huge improvement because prior to the change I made I would play 1-2 games get BSOD.. I have been able to play 50+ or so since this last fix. Attached is the new SF and below is my new Who crashed Error. Its stating that its a driver issue and not hardware related.. Do you think I should still do the stress test?
Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. 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 Sun 5/25/2014 8:51:07 PM GMT your computer crashed crash dump file: C:\Windows\memory.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 |
My System Specs![]() |
25 May 2014 | #7 |
![]() |
Yes. Complete all stress tests first
|
My System Specs![]() |
28 May 2014 | #8 |
|
Ran the memtest for 24hrs with 12 passes 0 errors. Will be working on the other stress tests asap
|
My System Specs![]() |
07 Jun 2014 | #9 |
|
Ran the Video Test and I got a BSOD again but i dont think the BSOD has anything to do with vid card. At lease not from these logs that I attached, I do not think? Attached are the GPU Sensor Logs and the new SF logs.. In addition, Below is the new WhoCrashed:
Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. 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 6/7/2014 10:53:20 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 (0xFFFFF88028708010, 0x0, 0xFFFFF800037ACCDC, 0x2) 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 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. Conclusion 8 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 actually 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. |
My System Specs![]() |
07 Jun 2014 | #10 |
|
I am getting a new error of : Display driver nvlddmkm stopped responding and has successfully recovered.
This error has only started since I have done this : NVIDIA Drivers - Avoid Problems.. I did not get any version above 331.82 even though there is newer ones available.. |
My System Specs![]() |
![]() |
Thread Tools | |
Similar help and support threads | ||||
Thread | Forum | |||
Multiple BSOD different reasons acording to WhoCrashed Hello guys! New here so don't be harsh. I need some help with my laptop. I'm getting BSOD errors since I start using my 2nd screen. I think it over heats. That's just my theory. So who can help me understand my dump files and how can I upload them or something like that? :) I'll be... |
BSOD Help and Support | |||
BSOD's, WhoCrashed says ntoskrnl.exe Hi guys, PC noob builder here. 3 weeks ago I built up a gaming pc for my son (specs are in my profile for those interested). The build went very well considering it was my first time ever (prior to this my most adventurous attempt inside a case was switching out a bad video card). I used the... |
BSOD Help and Support | |||
BSOD problem + screenshots (bluescreenview, whocrashed) pls help! Hey guys, Recently my (relatively new) PC, has been crashing multiple times a day, for no apparent reason, giving a blue screen of death. Usually the main error is IRQL_NO_LESS_OR_EQUAL, but this also varies sometimes to MEMORY_MANAGEMENT or NTFS_FILE_SYSTEM. Some research showed me that it... |
BSOD Help and Support | |||
BSOD - whocrashed points to cdd.dll and kernel Hi. Thank you all for your help. My computer has been getting BSOD memory dump errors for a couple of weeks now and I have tried many tools to pin down the error but at this point I need some expert guidance. Steps I've taken so far: Booting to safe mode and restoring to an earlier... |
BSOD Help and Support | |||
Randoms BSOD since ~1 week. WhoCrashed - ntoskrnl.exe and ntkrnlmp.exe Hello there, After browing the Internet for about 5 full days and still getting my BSODs, I'm creating this thread because of how desperate this is making me. I've tried formating and reinstalling Windows three times, with two different boot ISOs. The second seemed to worked better than the... |
BSOD Help and Support |
Our Sites |
Site Links |
About Us |
Find Us |
Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd All times are GMT -5. The time now is 06:11. |
![]() ![]() ![]() ![]() ![]() |