[SOLVED] [Win7 x64] BSOD - 0x124

Re: BSOD - 0x124 Win7 x64

Hi Pablo And Welcome to the forums ^_^,

I checked your dump files and all of your Dump files except 2 have the 0x124 STOP errors which is the WHEA_UNCORRECTABLE_ERROR. The two dump files in which the errors are different are having the error :- "SYSTEM_SERVICE_EXCEPTION" and "DRIVER_VERIFIER_IOMANAGER_VIOLATION" errors. In the dump file having the Driver Verifier pointing to the Dtsoftbus01.sys which is contained in the Daemon Tools Suite of software. Please remove the Daemon Tools software to make sure that it is not the issue.

Generally, the WHEA_UNCORRECTABLE_ERROR is a case of hardware failure and this is present in most of your dump files. If we run !errrec on the second parameter of the Dump File which gives the address of the structure which describes the error condition we get the below output. Below is provided an analysis of your most recent dump file :-
Read More:

Furthermore HAL.DLL (Hardware Abstraction Layer) is present in the stack of the dump file which indicates that there is no software conflict but rather hardware conflict.
Please follow these instructions below :-
There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting or to clear overclock settings - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Source :- BSOD one to two times a day - Microsoft Community
Thanks PATRICK!

Before replacing the processor, please make sure you stress test using OCCT or similar software to make sure that there is problem with the hardware only.
 
Re: BSOD - 0x124 Win7 x64

Hi,

WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

Code:
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800985f138
Section       @ fffffa800985f2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
[COLOR=#ff0000]
Error         : DCACHEL1_DRD_ERR (Proc 1 Bank 0)[/COLOR]
  Status      : 0xb634a00081000135
  Address     : 0x0000000093a26400
  Misc.       : 0x0000000000000000

DCACHEL1_DRD_ERR implies that there was a problem restoring data deferred to the L1 Cache when the instruction was needed.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

Code:
2: kd> k
Child-SP          RetAddr           Call Site
fffff880`08de5ad8 fffff800`02484169 nt!KeBugCheckEx
fffff880`08de5ae0 fffff800`02483abc nt!KiBugCheckDispatch+0x69
fffff880`08de5c20 fffff800`024af75d nt!KiSystemServiceHandler+0x7c
fffff880`08de5c60 fffff800`024ae535 nt!RtlpExecuteHandlerForException+0xd
fffff880`08de5c90 fffff800`024bf4c1 nt!RtlDispatchException+0x415
fffff880`08de6370 fffff800`02484242 nt!KiDispatchException+0x135
fffff880`08de6a10 fffff800`02482dba nt!KiExceptionDispatch+0xc2
fffff880`08de6bf0 fffff880`0a1307fb nt!KiPageFault+0x23a
fffff880`08de6d80 fffffa80`0a28a840 [COLOR=#ff0000]nvlddmkm+0x44d7fb[/COLOR]
fffff880`08de6d88 fffffa80`0a29db30 0xfffffa80`0a28a840
fffff880`08de6d90 00000000`00000000 0xfffffa80`0a29db30

nvlddmkm.sys is the nVidia video driver.

DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)

This is the bug check code for all Driver Verifier I/O Verification violations.

Code:
BugCheck C9, {[COLOR=#4b0082]23e[/COLOR], fffff88001a01360, fffff9800f562ea0, 0}

FAILURE_BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1360

dtsoftbus01.sys is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. In this case, it appears to have marked an IRP pending but didn't return STATUS_PENDING.




1. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

2. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:

Avira removal - How do I uninstall my Avira product?

MSE - Microsoft Security Essentials - Microsoft Windows

4. Uninstall Samsung Rapid Disk ASAP! Very troublesome.

5. wdcsam64.sys is listed and loaded which is the Western Digital SES (SCSI Enclosure Services) driver. Please remove this software ASAP as it's troublesome and is also not necessary to the functionality of your system.

6. If the above fails, please refer to below....




1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Re: BSOD - 0x124 Win7 x64

Hello again patrick, I'm the argentinian :D

As soon as I get my hands on that PC again I'll test what you say; I'm not at the shop now.
I'll come back with news :D

Thanks!
 
Re: BSOD - 0x124 Win7 x64

I did everything you said, and up to the moment no crashed happened again. You solved it once again ;)

Thanks a lot Patrick & team! I'll mark this as solved
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top