Dell Latitude E5400 0x124 BSOD

RaidoR · 11 Mar 2013

After installing fresh windows 7 I keep getting BSOD. Previously I had XP and had no problems. All drivers should be up do date.

I will attach my log to the post.

Saurabh A · 11 Mar 2013

Hi RaidoR,

The system crash seems to be happening due to a 'hardware issue':

Code:

Loading Dump File [C:\Errors\RaidoR\SF_11-03-2013\031113-38547-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Mon Mar 11 11:47:25.547 2013 (UTC + 5:30)
System Uptime: 0 days 0:00:30.388
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004b17038, 0, 0}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
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: 0000000000000000, Machine Check Exception
Arg2: fffffa8004b17038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fe06b0 fffff800`02cd9a89 : fffffa80`04b17010 fffffa80`036fa040 00000000`0000003c 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fe0bd0 fffff800`02bbb547 : fffffa80`04b17010 fffff800`02c345f8 fffffa80`036fa040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fe0c00 fffff800`02b23b95 : fffff800`02c96360 fffffa80`048eccb8 fffffa80`048eccb0 fffffa80`036fa040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fe0c40 fffff800`02a9e161 : fffff880`01108e00 fffff800`02b23b70 fffffa80`036fa040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fe0c70 fffff800`02d34166 : 00000000`00000000 fffffa80`036fa040 00000000`00000080 fffffa80`036e7840 : nt!ExpWorkerThread+0x111
fffff880`02fe0d00 fffff800`02a6f486 : fffff880`009ea180 fffffa80`036fa040 fffff880`009f4f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe0d40 00000000`00000000 : fffff880`02fe1000 fffff880`02fdb000 fffff880`02fdfea0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner

Please run 'Hardware Diagnostics' to check 'hardware functionality':
- Power off the notebook > Power it back on > Repeated tap 'F 12 key' at the 'Dell splash screen' > Highlight 'Diagnostics' > Tap 'Enter' > Capture and share 'errors' is any. (Alternatively, you may launch the diagnostics by 'powering on' the system with the 'function key' held down.

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled. That will rule out most (lack of) cooling issues.

Code:

1: kd> lmntsmn
start             end                 module name
fffff880`00f28000 fffff880`00f7f000   ACPI     ACPI.sys     Tue Jul 14 04:49:34 2009 (4A5BC106)
fffff880`010cd000 fffff880`010d8000   amdxata  amdxata.sys  Tue May 19 23:26:59 2009 (4A12F2EB)
fffff880`00de9000 fffff880`00df2000   atapi    atapi.sys    Tue Jul 14 04:49:47 2009 (4A5BC113)
fffff880`010a3000 fffff880`010cd000   ataport  ataport.SYS  Tue Jul 14 04:49:52 2009 (4A5BC118)
fffff880`00ff0000 fffff880`00ffc000   BATTC    BATTC.SYS    Tue Jul 14 05:01:01 2009 (4A5BC3B5)
fffff880`00d0a000 fffff880`00dca000   CI       CI.dll       Tue Jul 14 07:02:13 2009 (4A5BE01D)
fffff880`01800000 fffff880`01830000   CLASSPNP CLASSPNP.SYS Tue Jul 14 04:49:58 2009 (4A5BC11E)
fffff880`00cac000 fffff880`00d0a000   CLFS     CLFS.SYS     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 05:19:40 2009 (4A5BC814)
fffff880`00fe7000 fffff880`00ff0000   compbatt compbatt.sys Tue Jul 14 05:01:02 2009 (4A5BC3B6)
fffff880`01830000 fffff880`0183e000   crashdmp crashdmp.sys Tue Jul 14 05:31:01 2009 (4A5BCABD)
fffff880`019cd000 fffff880`019e3000   disk     disk.sys     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`0184a000 fffff880`01853000   dump_atapi dump_atapi.sys Tue Jul 14 04:49:47 2009 (4A5BC113)
fffff880`0183e000 fffff880`0184a000   dump_ataport dump_ataport.sys Tue Jul 14 04:49:47 2009 (4A5BC113)
fffff880`01853000 fffff880`01866000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 04:51:51 2009 (4A5BC18F)
fffff880`01124000 fffff880`01138000   fileinfo fileinfo.sys Tue Jul 14 05:04:25 2009 (4A5BC481)
fffff880`010d8000 fffff880`01124000   fltmgr   fltmgr.sys   Tue Jul 14 04:49:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 04:49:45 2009 (4A5BC111)
fffff880`01993000 fffff880`019cd000   fvevol   fvevol.sys   Tue Jul 14 04:52:15 2009 (4A5BC1A7)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Tue Jul 14 04:51:08 2009 (4A5BC164)
fffff800`02ffc000 fffff800`03045000   hal      hal.dll      Tue Jul 14 06:57:36 2009 (4A5BDF08)
fffff880`0198a000 fffff880`01993000   hwpolicy hwpolicy.sys Tue Jul 14 04:49:22 2009 (4A5BC0FA)
fffff880`00dca000 fffff880`00dd2000   intelide intelide.sys Tue Jul 14 04:49:48 2009 (4A5BC114)
fffff800`00bbb000 fffff800`00bc5000   kdcom    kdcom.dll    Tue Jul 14 07:01:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 04:50:54 2009 (4A5BC156)
fffff880`015bf000 fffff880`015ea000   ksecpkg  ksecpkg.sys  Tue Jul 14 05:20:34 2009 (4A5BC84A)
fffff880`00c54000 fffff880`00c98000   mcupdate mcupdate.dll Tue Jul 14 06:59:10 2009 (4A5BDF66)
fffff880`00c39000 fffff880`00c53000   mountmgr mountmgr.sys Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`01138000 fffff880`01170000   MpFilter MpFilter.sys Thu Nov 01 04:13:06 2012 (5091A97A)
fffff880`00f88000 fffff880`00f92000   msisadrv msisadrv.sys Tue Jul 14 04:49:26 2009 (4A5BC0FE)
fffff880`01170000 fffff880`011ce000   msrpc    msrpc.sys    Tue Jul 14 04:51:32 2009 (4A5BC17C)
fffff880`01978000 fffff880`0198a000   mup      mup.sys      Tue Jul 14 04:53:45 2009 (4A5BC201)
fffff880`0146d000 fffff880`0155f000   ndis     ndis.sys     Tue Jul 14 04:51:40 2009 (4A5BC184)
fffff880`0155f000 fffff880`015bf000   NETIO    NETIO.SYS    Fri Apr 09 08:13:59 2010 (4BBE946F)
fffff800`02a1f000 fffff800`02ffc000   nt       ntkrnlmp.exe Tue Jul 14 05:10:48 2009 (4A5BC600)
fffff880`0124b000 fffff880`013ee000   Ntfs     Ntfs.sys     Tue Jul 14 04:50:47 2009 (4A5BC14F)
fffff880`00fd2000 fffff880`00fe7000   partmgr  partmgr.sys  Tue Jul 14 04:49:58 2009 (4A5BC11E)
fffff880`00f92000 fffff880`00fc5000   pci      pci.sys      Tue Jul 14 04:49:51 2009 (4A5BC117)
fffff880`00de2000 fffff880`00de9000   pciide   pciide.sys   Tue Jul 14 04:49:49 2009 (4A5BC115)
fffff880`00dd2000 fffff880`00de2000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 04:49:48 2009 (4A5BC114)
fffff880`00c00000 fffff880`00c39000   pcmcia   pcmcia.sys   Tue Jul 14 05:01:10 2009 (4A5BC3BE)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Tue Jul 14 04:49:27 2009 (4A5BC0FF)
fffff880`00c98000 fffff880`00cac000   PSHED    PSHED.dll    Tue Jul 14 07:02:23 2009 (4A5BE027)
fffff880`0193e000 fffff880`01978000   rdyboost rdyboost.sys Tue Jul 14 05:04:34 2009 (4A5BC48A)
fffff880`01936000 fffff880`0193e000   spldr    spldr.sys    Mon May 11 22:26:27 2009 (4A0858BB)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Fri Apr 09 08:15:54 2010 (4BBE94E2)
fffff880`00fc5000 fffff880`00fd2000   vdrvroot vdrvroot.sys Tue Jul 14 05:31:31 2009 (4A5BCADB)
fffff880`0144a000 fffff880`0145a000   vmstorfl vmstorfl.sys Tue Jul 14 05:12:54 2009 (4A5BC67E)
fffff880`00e00000 fffff880`00e15000   volmgr   volmgr.sys   Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`00e15000 fffff880`00e71000   volmgrx  volmgrx.sys  Tue Jul 14 04:50:33 2009 (4A5BC141)
fffff880`018ea000 fffff880`01936000   volsnap  volsnap.sys  Tue Jul 14 04:50:08 2009 (4A5BC128)
fffff880`00e75000 fffff880`00f19000   Wdf01000 Wdf01000.sys Tue Jul 14 04:52:07 2009 (4A5BC19F)
fffff880`00f19000 fffff880`00f28000   WDFLDR   WDFLDR.SYS   Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`00f7f000 fffff880`00f88000   WMILIB   WMILIB.SYS   Tue Jul 14 04:49:51 2009 (4A5BC117)

Following device drivers need to be updated; please use these links to install latest drivers for your machine (Tested with Windows 7 32 bit):
Note: Download each file one by one; and follow the on-screen instructions to finish installation. Restart the system if prompted.
1. Intel Chipset Software: Driver Details | Dell US
2. Media Card Reader: Driver Details | Dell US
3. Audio: Driver Details | Dell US
4. Ethernet Driver: Driver Details | Dell US
5. Intel 5100 WLAN: Driver Details | Dell US
6. Intel Display: Driver Details | Dell US

Update the BIOS firmware:
Note: Make sure the ac adapter is connected and the battery is charged 10% or above to update the BIOS. Also, disconnect all the external peripherals before updating the BIOS. All the programs should be closed and documents saved.
- Click Driver Details | Dell US to download and update the firmware

Hope this helps. Do reply with the findings; will take it forward from there.

RaidoR · 13 Mar 2013

Updated all drivers and still keep getting BSOD

VistaKing · 13 Mar 2013

Run a memory test

Note

Run it over night or until 10 passes

RAM - Test with Memtest86+

Northernsoul55 · 13 Mar 2013

Just a note:

I noticed you do not have Windows Service pack 1 installed also ensure all Windows updates are installed.

https://www.sevenforums.com/windows-updates-activation/139146-windows-7-service-pack-1-faqs-installation-issues-helpful-links.html

Saurabh A · 13 Mar 2013

RaidoR said:

Updated all drivers and still keep getting BSOD

Hi RaidoR,

Thank you for the reply.

Was wondering if you ran the 'Hardware Diagnostics' as I suggested in my previous post; please share the results.

You may also try to change the 'SATA Mode' in 'BIOS' to see if that helps. Please follow these steps:
- Restart the unit > Repeatedly tap 'F2' key to enter the 'System Setup' > Locate & Expand 'SATA Operation' (Mouse would not work in this environment; use the 'arrow keys' to navigate) > Please change the 'SATA Mode' from 'AHCI' to 'ATA' (If the current setting is AHCI); else, change it to 'AHCI' if the current setting is 'ATA' > Tap 'F10' key to 'Save settings' and 'Exit' > Try getting back to 'Windows' and check results.

You may find the following 'BIOS navigation commands' useful:

Also install 'Windows Updates' as suggested by Northernsoul55.
@Northernsoul55: Thank you for the valuable inputs, Dave :)

Also share the recent crash dump data for analysis: Blue Screen of Death (BSOD) Posting Instructions

Do reply with the findings; will take it forward.

RaidoR · 14 Mar 2013

Installed W7 SP1, Dell diagnostics showed no errors and Prime95 run over night without errors. Today I will run Memtest overnight and post results.

Saurabh A · 14 Mar 2013

Hi RaidoR,

Thank you for the reply.

Good that the result of 'diagnostics' look fine and 'Windows sp1' is installed; please run 'Memtest' and share results.
Would like to know if you tried changing the 'SATA Mode' in 'BIOS'. If you continue facing the issues, also change that setting as suggested and check if the notebook 'Blue screens' again.

Do reply with the results.

RaidoR · 15 Mar 2013

Memtest - 13 passes, no error. Changed SATA mode to AHCI, let's see what happens :)

Saurabh A · 16 Mar 2013

Hi RaidoR,

Thank you for the reply.

It is recommended that you move the settings from 'ATA' to 'AHCI' before installing 'Windows 7'. Switching to 'AHCI (Advanced Host Controller Interface)' allows SATA drive hot plug and supports 'native command queuing (NCQ)'. This is likely to improve Windows 7 performance. Please observe the system to see if it works fine.

Do reply with the findings; glad to assist.