BSOD while browsing on Firefox, Error 124.

[Silverfyre]

Hello!

My Dell Inspiron just started giving me some issues this morning. It generated a BSOD error 124 and force closed everything, restarting with the "Windows has encountered an unexpected error" message upon restart. I ran a test on the hard drive, RAM and CPU and everything came back fine, at least according to the tests. HDMonitor is telling me that everything is running in normal temperature limits too.

I haven't had a crash since I was having NVidia driver issues back in December once I put my NVidia GeForce 560Ti into my computer and resolved those crashes by using the 314.22 driver. Nothing bad since then until this morning. I'm at a loss on what might be going on.

I really appreciate any help I can get. Requested logs and files are attached below. My thanks!

 

[Thedoctor44]

1: kd> [COLOR="Green"]!errrec fffffa8007a5a6c8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8007a5a6c8
-------------------------------------------------------------------------------
Record Id     : 01cf83d1aaf8d745
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/9/2014 10:58:00 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f63
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 63 0f 10 00 00 08 02 00 - 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  @ fffffa8007a5a8e0

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

Error         : [COLOR="red"]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR[/COLOR] (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

This bus error could mean many things so it's best to use basic troubleshooting method.

If you are overclocking STOP!
Return all clock speeds to default values.

Run the stress tests posted below.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.