BSOD at random times...ntoskrnl.exe

Hello,
A friend gave me her computer to fix because it has been BSODing at random times. I'm completely stumped after working on it, and i have yet to find a fix for the ntoskrnl.exe crash. I'm not a professional but the minidumps are blaming that driver so i just dont know. Any help is appreciated.

It's a custom build PC.

Motherboard: Asus M5A97
CPU: AMD Phenom(tm) II x4 945
Graphics Card: NVIDIA GeForce GT 440
Hard Drive: Western Digital WD7500AAKS-00RBA0 750 GB
RAM: 4GB

Code:

BugCheck 124, {0, fffffa80046df8f8, 0, 0}

Probably caused by : AuthenticAMD

Code:

2: kd> !errrec fffffa80046df8f8
===============================================================================
Common Platform Error Record @ fffffa80046df8f8
-------------------------------------------------------------------------------
Record Id     : 01ce7cf7256b33c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/9/2013 22:53:41 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000001

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

Local APIC Id : 0x0000000000000001
CPU Id        : 43 0f 10 00 00 08 04 01 - 09 20 80 00 ff fb 8b 17
                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  @ fffffa80046dfb10

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

Error         : DCACHEL1_EVICT_ERR (Proc 1 Bank 0)
  Status      : 0xb600400070000175
  Address     : 0x0000000000000b00
  Misc.       : 0x0000000000000000

The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue. However, the error does point to the Level 1 Cache.

In such a situation, it is best to use these steps:

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

• 
  Stop 0x124 - what it means and what to try

All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

Thank you for your help. I started the test now, so I'll let it run for a couple hours and let you know what happens.

Thanks :)

Ok...the test has ran for about 2.5 hours and no errors have been found that I saw. So is there any more testing i can do for other stuff or is it deffinitly the motherboard? Thanks for all the help so far!:)

Run the Large FFT's and Blend test for a few hours too, it's part of Prime95.

Ok, I ran all those tests and they came up ok. However, I did put the CPU on energy saving mode in the BIOS and and it underclocks it quite a bit so I don't know if that would've made a difference or not. I also ran a disk check and the hard drive has bad sectors and it is pretty old. I just got off the phone with the owner of the computer and she said that the guy that built it used the hard drive from her old computer. She also said that it has been BSODing ever since she got the computer. She took it back but the guy that built it said there was nothing wrong. One more thing, when she first gave me the computer the motherboard wouldn't even recognize the hard drive in the BIOS and I have no idea what I done, but it finally did recognize it and I got it to boot. Thanks for all the help!

If the BIOS is starting to struggle to find the hard-drive, then purchase a replacement, the hard-drive isn't going to last long, and you may begin to lose any saved data.

Ok, I'll try that. Thanks.

Welcome :)