BSOD while on Firefox, error 0x124

[aika]

Hello,

I've lurked a bit on this forum in my search for some solutions of why my laptop has been BSODing and I haven't really come across any reasons why. I know that this error is a hardware error but I'd like more details. I've uploaded my dump files with SF tool and hopefully you guys can help provide some insight. Very much appreciated!

Some info on my laptop:
Samsung np900x3c
Intel i5-3317U
4gb RAM
Integrated graphics

I've gotten this error various times but usually doing something different each time. Really thought it was a heating issue since the fan on an ultrabook isn't that great afterall lol. The most recent crash was today, Feb 10th 2013. It hasn't happened all too often, just once in a while it will show itself. I've had this laptop for the past 7 or 8 months already...assuming my laptop is still under warranty but I'd have to double check that. If there's any additional info needed, just let me know and I can see if I can get it. If not, I'll probably just ask you on how to obtain it.

Again, much appreciated guys!

 

[carwiz]

A Bugcheck 124 is a hardware error. The last dump indicates a failure in the processor micro architecture but it looks like it's failing to fill memory. I checked your pagefile size and it looks ok then a check to your error logs supplies a rather grim notice. It appears that your disk drive may be failing or there is something interfering with I/O.

1. Uninstall the Intel Management Engine Interface. It's a resource hog from the get-go. OEMs install this package at build time for remote debugging and is usually maintained/used by an IT department. It's of little value to the individual and places undue stress on the system.

2 Run Chkdsk on the C: drive to verify and repair any problems with the diskdrive. This will run after a reboot and must not be interrupted. Be sure the PC is plugged into an AC power supply. Do NOT run this task off the battery.

3. Run SFC /scannow to verify system drivers and registry entries. If errors are found, run it again for up to three times. Report back any console messages.

kd> !errrec fffffa8006b4f028
===============================================================================
Common Platform Error Record @ fffffa8006b4f028
-------------------------------------------------------------------------------
Record Id     : 01ce0660743bd3a5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/10/2013 6:20:29
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006b4f0a8
Section       @ fffffa8006b4f180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    :[B] Micro-Architectural Error
[/B]Flags         : 0x00
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000002
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006b4f0f0
Section       @ fffffa8006b4f240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000002
CPU Id        : a9 06 03 00 00 08 10 02 - bf e3 ba 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  @ fffffa8006b4f240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006b4f138
Section       @ fffffa8006b4f2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : Internal unclassified (Proc 2 Bank 4)
  Status      : 0xb200000000100402

Event[34999]:
Log Name: System
Source: Disk
Date: 2013-01-12T14:28:10.474
Event ID: 51
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Description:
An error was detected on device \Device\Harddisk1\DR7 during a paging operation.

 

[aika]

Thanks so much for the response and all the advice provided! I've uninstalled the Intel Management Engine Components.

I will report back after completing points 2 and 3.

 

[aika]

Quick question, for chkdsk, should i uncheck both the options (automatically fix or scan and attempt to recover)? Or should I just choose an option? Just wanted to know if you wanted me to post any reports received.

 

[carwiz]

Check mark both. It will take some time to run. Just make sure it doesn't get interrupted. As stated before, it will start after you reboot. Yes, provide any console messages.

 

[aika]

hey carwiz, finished the chkdsk run. Below is the log that was outputed, i went afk so I got the log in event viewer. I'll run sfc/scannow tomorrow though and will post as soon as I finish, thanks again carwiz!


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
193792 file records processed. File verification completed.
250 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
250430 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
193792 file SDs/SIDs processed. Cleaning up 380 unused index entries from index $SII of file 0x9.
Cleaning up 380 unused index entries from index $SDH of file 0x9.
Cleaning up 380 unused security descriptors.
Security descriptor verification completed.
28320 data files processed. CHKDSK is verifying Usn Journal...
34266376 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
193776 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
9411942 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

97640447 KB total disk space.
59608968 KB in 153840 files.
86576 KB in 28321 indexes.
0 KB in bad sectors.
297131 KB in use by the system.
65536 KB occupied by the log file.
37647772 KB available on disk.

4096 bytes in each allocation unit.
24410111 total allocation units on disk.
9411943 allocation units available on disk.

Internal Info:
00 f5 02 00 9d c7 02 00 4d 1c 05 00 00 00 00 00 ........M.......
3a 05 00 00 2c 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 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[carwiz]

It looks like it made some corrections to allocation. The allocation errors can be caused by loss of power as well as a disk going bad.

If you run your laptop to near a DOA battery life frequently, it's advisable to disable Write Caching.

To disable write caching on the drive;
Click the Orb, Right click Computer then select Manage.
Click on Device Manager, expand Disk Drives, Right click on drive and select Properties.
Click on the Policies Tab and un-check the Write Caching, click OK.

Below is a sample. The blue arrow points to the option.

 

[aika]

Thank you, I actually do sometimes run the laptop till it shuts off...definitely is not the best idea. I've now disabled it and below is a screenshot of my sfc scan. Seems like nothing is wrong

 

[Arc]

A stop ox124 is a hardware error error architecture uncorrectable error.

[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: [COLOR=Red]0000000000000000, Machine Check Exception[/COLOR]
Arg2: fffffa8006b4d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100402, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

The first argument here is a machine check exception; that means the CPU detected a hardware problem. I am guessing that the system is under warranty? Best if you utilize it.

 

[carwiz]

Are you still getting a BugCheck 124 BSOD?

 

[aika]

Well, the thing is that I don't get this error often. Since I got my laptop, which was probably in September of 2012 if i remember correctly, I've only had this BSOD 3 or 4 times. This was literally the only problem that I've been getting with this laptop and with it happening such infrequently, I'm not sure what I should really do lol

 

[carwiz]

Running multiple real-time AV programs can cause memory problems and thus disk corruption. AVG alone is known for corrupting memory. MSE and Malwarebytes on-demand are known here to be trouble-free and seamless to the OS. If you've installed those as suggested, fixed the disk and SFC came up clean, you should be good to go. Keep the AV's up to date and run occasional full scans with each, one at a time.


Ops! Posted to the wrong thread. Sorry
I think I only have 10 going at the moment.

 

[aika]

Hahaha, its all good...you think I should just keep it? It'll save alot of trouble lol but not sure how much trouble there will be later on in future years though

 

[carwiz]

If it serves you well, keep it. I still have a couple of older PCs that still run well for their use.