BSOD - 0x00000124 - caused by ntoskrnl.exe dump attached

Saltychip · 23 Nov 2013

Hi guys,

Having BSOD issues. I thought initially it was scaned from hardware issue maybe loose connectors but my build is less than 30 days old and i've reseated all parts about 4 days ago. It didnt BSOD for 4 days but today it BSOD while browsing the internet, the next BSOD was when trying to hardware scan device manager so I know it must be caused from some files inside my OS and not hardware. It has happened in gaming before.

I've attached the dump file but theres a lot of dumps becuase of BSOD i've had so far caused by ntoskrnl.exe. I will be trying driver sweeper to remove graphic card drivers then reinstalling them maybe that will help. Looking forward to any expert help on this matter thank you.

I think most recent dump file is 112213-25724-01.dmp

* All temps are fine CPU hasnt gone above 50c when playing games I've been monitoring with HW monitor. I did overclock once but it wasnt sustainable so I reset to stock a while back so I'm NOT OC'd now.

Arc · 23 Nov 2013

Hi Saltychip.

We nave noticed that sometimes the absence of Service Pack 1 causes stop 0x124 BSODs (though it is basically a hardware related BSOD).

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

If it continues to BSOD in the same way even after installing the Service Pack 1, we will go for further troubleshooting.
________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008c13788, 0, 0}

Probably caused by : AuthenticAMD

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

Saltychip · 23 Nov 2013

Okay thanks for your reply I will try this and report back!