MACHINE_CHECK_EXCEPTION hal.dll+12818 - Random BSOD on Dell XPS Laptop

[williamfox4]

Hello,
I have a new(ish) Dell XPS Laptop which is approx 3/4 months old so its still under warranty.
I have been in touch with Dell but they keep fobbing me off without fixing the problem.

For the past 3 weeks I have been getting random BSOD, sometimes I am using the machine, sometimes not. I am a developer/desiger so I have a lot of apps installed like illustrator, fireworks, visual studio but there are times when none of these are running, its crashing even when surfing the web.

I have attached a zip file as per instructions for posting in this category - I really hope someone can help me with this as its driving me crazy!

Dell XPS L702X 17" Laptop
Windows 7 Ultimate 64
Core i7-2760 QM CPU @ 2.4GHz
8GB RAM
220GB SSD HD

Thanks in advance
Will.

 

[writhziden]

Your Windows install appears to be corrupted.

• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

 

[williamfox4]

Hello,
Thank you for the information.
I have just run the SFC as you have requested but it came back with nothing.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

Its crashed again this morning, at the time I was only listening to music through Media Player - I usually use Spotify but had stopped using that to see if that could be the cause. Ive since taken a look on the Dell website and found and updated driver for the sound card and no crash since.... But, its far too early to tell if that has fixed it - It has gone for a week of normal usage between crashing so I guess I just need to keep using it and trying one thing after another....

Kind regards,
Will.

 

[writhziden]

Odd that no corruption shows up. Your hardware error checking software that is built into Windows 7 does not seem to be starting properly.

Remarks

In Windows Vista and later operating systems, this bug check occurs only in the following circumstances.

• WHEA is not fully initialized.
  
  
• All processors that rendezvous have no errors in their registers.

For other circumstances, this bug check has been replaced with bug Check 0x124: WHEA_UNCORRECTABLE_ERROR in Windows Vista and later operating systems.
For more information about Machine Check Architecture (MCA), see the Intel or AMD Web sites.

Bug Check 0x9C: MACHINE_CHECK_EXCEPTION


For a 0x124 hardware bugcheck: If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For a hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.

 

[williamfox4]

hello,
i have run several tests on the hardware, there is a pre-boot system test which tests everything (or so they say at Dell).
ive been asked to wipe and reinstall my OS now!

i have used windbg on the dump file which gives the following:

Arguments:
Arg1: 0000000000000000
Arg2: fffff80000ba8bb0
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
LAST_CONTROL_TRANSFER: from fffff80003013818 to fffff800030c6c80
STACK_TEXT:
fffff800`00ba8b78 fffff800`03013818 : 00000000`0000009c 00000000`00000000 fffff800`00ba8bb0 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba8b80 fffff800`03012f57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff800`00ba8cd0 fffff800`03006e88 : 00000000`00000000 fffff800`0323be80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff800`00ba8d00 fffff800`030c556c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`030c53d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`061ca9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2

STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm+39c2
fffff880`061ca9c2 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: intelppm+39c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd
FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+39c2
BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+39c2
Followup: MachineOwner
---------

 

[writhziden]

When you re-install the OS, make sure to backup your files. See step 3 of http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164 on how to backup data.

 

[williamfox4]

I just wanted to give an update on this issue for people who may be having the same problem...
I reinstalled Windows from scratch - 2 hours later it crashed again.
I called Dell and they have been out and replaced the motherboard - 2 hours later it crashed again!!!
Now I'm pushing them for a refund /replacement. I'm thinking this could be an SSD issue, several other people online with similar unsolved issues all seem to have SSD in their machines... Hmmmmm...

Thank you for all of your assistance with this.

Will.

 

[writhziden]

It could be the SSD is not compatible with the hardware or it is not compatible with drivers/firmware on the system. Are all of the following up to date:

• SSD firmware
• BIOS version
• Chipset drivers
• Hard disk controller drivers

?