BSOD directly after Windows login, error 0x00000124

[Aart007]

Out of the blue, I am getting a BSOD literally every time I log into Windows starting today. I can only run Windows successfully and without problems in Safe Mode (which I'm running right now). I have not changed any hardware as of late, nor did I change any system settings. All my hardware is running at stock settings (XMP is enabled).

I've followed the procedure listed in the "Posting Instructions"-thread, so you'll find a .zip with the needed information as an attachment. You will need the dumps of today, june 20th. The other ones are older and not relevant anymore. You can find my systems specs in my profile, if needed.

Thanks in advance for the help.

 

[Gator]

A quick look at some of the installed programs and I see Daemon Tools

dtsoftbus01.sys Thu Jun 20 03:22:51 2013  (51C2ADCB) 
Daemon Tools driver [br] Possible BSOD issues in Win7}http://www.daemon-tools.cc/eng/downloads  
[URL="http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys"]Driver Reference Table - dtsoftbus01.sys[/URL]

Also, Gigabyte utilities are known to cause issues, remove them asap

gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175)  
Gigabyte Easy Saver - mobo power utility  driver}http://www.gigabyte.com.tw/Support/Motherboard/Driver_List.aspx 
[URL="http://www.carrona.org/drivers/driver.php?id=gdrv.sys"]Driver Reference Table - gdrv.sys[/URL]

Also, this Xbox controller driver seems to cause BSOD issues as well

xusb21.sys Thu Aug 13 18:10:17 2009 (4A848F49)  
XBox USB wireless controller [br] BSOD issues in Win7  with 2009 driver (found in  mid-2012)}http://www.microsoft.com/hardware/download/download.aspx?category=Gaming&type=Gaming&sku=JR9-00001  
[URL="http://www.carrona.org/drivers/driver.php?id=xusb21.sys"]Driver Reference Table - xusb21.sys[/URL]

Remove Daemon Tools and Gigabyte Utilities with Revo Uninstaller
How to easily clean an infected computer (Malware Removal Guide)


Let me look further but I would recommend running Malwarebytes, TDSS Cleaner and ADWCleaner

Malwarebytes
http://www.sevenforums.com/tutorials/338716-malwarebytes-anti-malware-free.html

TDSS Cleaner
http://www.sevenforums.com/tutorial...r-detect-repair-tdss-rookits.html#post2836778

ADW Cleaner
Downloading AdwCleaner

If these programs find a lot of infected files (flagged as Malware/Trojans/Rootkits) then i would recommend the link below
How to easily clean an infected computer (Malware Removal Guide)

You also may want to try troubleshooting with a Clean Boot
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Gator]

All of your most recent dumps are Whea error Bugcheck 0x124. Typically this means your processor is faulty in some way.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, [COLOR=Red]fffffa80083d8028[/COLOR], bf800000, 200401}

Probably caused by : GenuineIntel

Followup:     MachineOwner
---------

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!thread'
3: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!thread
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80083d8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.

3: kd> !errrec fffffa80083d8028
===============================================================================
Common Platform Error Record @ [COLOR=Red]fffffa80083d8028[/COLOR]
-------------------------------------------------------------------------------
Record Id     : 01d0ab3e1664ef22
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/20/2015 9:59:23 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80083d80a8
Section       @ fffffa80083d8180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR=Red]Micro-Architectural Error[/COLOR]
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80083d80f0
Section       @ fffffa80083d8240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb da 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80083d8240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80083d8138
Section       @ fffffa80083d82c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]Internal unclassified (Proc 3 Bank 1)[/COLOR]
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00000
  Misc.       : 0x0000000000000086

Before we come to that conclusion, lets try some things.

Along with the above steps in my previous posts, please do the following.

1. Remove ESET and install Microsoft Security Essentials. You can choose to go back to ESET after and test but since ESET was mentioned in a crash dump, lets make sure its not it.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  ekrn.exe

Remove ESET and install MSE
Microsoft Security Essentials - Microsoft Windows

2. Monitor your CPU Temperatures. Ensure your fans are running properly. Clean the inside of the PC to ensure no dust is accumulating inside

3. Go into your BIOS and reset your BIOS settings to the defaults

4. Run Memtest86+ - Follow the instructions in the tutorial. Run for at least 8 passes or until you find any errors. Stop the test and move onto the next step if you have ANY errors

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If all of the above fails, your CPU is likely faulty.

 

[Aart007]

Wow, thanks for the help and in-depth information, really appreciate it!

Strange this is... I just came home (haven't done/changed/fixed anything since leaving home, right after I created this thread) and booted up my PC, finding that it's functioning normally for some reason. No BSODs or anything.
I was expecting to get a BSOD and having to reboot and go into Safe Mode to even have a look at this thread and see if someone had replied, but I'm currently logged into Windows as if nothing happened.

I uninstalled DAEMON Tools just now, but if my Windows can start normally, I guess that means it couldn't have been the culprit?
I've also been monitoring my temperatures, but my CPU is running between 23-28 degrees Celcius across all four cores when idling/web browsing. All my case fans are running and so is the fan of my aftermarket CPU cooler.

Does this mean it could've been a one/two-time occurrence/bug, or can my CPU still be faulty even though it's running normally right now?

 

[Gator]

Daemon Tools could have still been the problem. Either way it is a program that is known to cause problems and/or BSOD's

The only way for that Bugcheck to be thrown is a small subset of issues. If it doesn't get fixed with the steps provided above, its almost certainly a CPU thats is/going bad.

 

[Aart007]

Daemon Tools could have still been the problem. Either way it is a program that is known to cause problems and/or BSOD's

The only way for that Bugcheck to be thrown is a small subset of issues. If it doesn't get fixed with the steps provided above, its almost certainly a CPU thats is/going bad.

Thought I'd do an update on the situation, so here goes:

I haven't had a BSOD in almost two days now. Yesterday morning (about 24 hours ago) the system rebooted itself without any warning, but no blue screen was presented. It booted me into the BIOS menu, giving me the option to load the optimized BIOS settings, so I did that. I let it run for a while, doing my usual stuff, but no crashes whatsoever.
In the meantime I uninstalled a program called "EasyTuner" (Gigabyte motherboard program), which I had never used (to my knowledge). After some time I re-enabled the XMP profile (I've got 2133Mhz memory), and all seems to be fine. I can even run heavy games (GTA 5) without my PC crashing, and the temperatures are excellent across the board.

The only weird thing that happened, was that my USB driver seemingly crashed during the game. I've had that about 3 to 5 times before in the past (maybe four months ago, always happened during gaming), but it went away after a while. I've got a Logitech G110 USB-keyboard, a Logitech G700s USB-mouse and a Kingston HyperX Cloud II USB-headset.
The game froze for two seconds with a popping sound in my headphones and after that:

- no sound at all
- my keyboard "sticking" on the last key I was using ("S" key, in this case), but other than that giving no reaction to input
- the lights on my keyboard went out as well
- no reaction to mouse input

After about one minute, my USB devices came back to life, with the exception of the in-game sound (Windows sounds did play when I Alt-Tabbed), resulting in me having to restart the game.
I have searched through the Windows logs, but there was no error corresponding to such an event and there was no error to be found corresponding to the point in time it happened. I have the correct USB 3.0 drivers installed from the Gigabyte website, btw.

So yeah, no BSODs these past days, "just" this weird USB thing (happened once).

 

[essenbe]

I would suggest you uninstall Easy Tune and all Gigabyte Utilities. They are well know causes of a multitude of problems.

 

[Aart007]

I would suggest you uninstall Easy Tune and all Gigabyte Utilities. They are well know causes of a multitude of problems.

Yeah, that's what I did (meant "EasyTune", not "EasyTuner"). And as far I can tell, I don't have any other Gigabyte utility program running.

 

[Callsignmako]

Hello, I recently built my own computer with Windows 7, Intel i7 4790k (no overclocking), MSi 970, and Gigabyte Z97X Gaming 7 motherboard. My computer was working fine until this morning, whenever I boot windows normally it goes to a blue screen with a stop error 0x00000124. I am able to boot in safe mode and I have tried to recover to a previous time but it did not work. I have attached the dump file, if anyone can help that'd be great.

 

[essenbe]

Callsignmako, I would suggest you start your own thread by going here, http://www.sevenforums.com/bsod-help-support/ and clicking the big Orange button. Please include the posting instructions there too.

 

[ICIT2LOL]

I would suggest you uninstall Easy Tune and all Gigabyte Utilities. They are well know causes of a multitude of problems.

Yep I can vouch for that too I used the install disk that came with the board and it took a clean install to tidy it up again, and the support I got from Gigabyte was pretty ordinary too.