New
#1
BSOD on Dell XPS 9100 caused by hal.dll
Please checkout my dmp files. My problem is similar to another forum member. My machine is still under warranty. The crashes are quite random. I'm thinking it is a pci issue.
Please checkout my dmp files. My problem is similar to another forum member. My machine is still under warranty. The crashes are quite random. I'm thinking it is a pci issue.
almondman, I have seen your earlier post. And, it is almost like a ditto copy of the issue being discussed in that thread.
So it is a hardware error, precisely, it is a PCIe device error.Code:******************************************************************************* * * * 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: 0000000000000004, PCI Express Error Arg2: fffffa800f3b0038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000 Arg4: 0000000000000000
UC status bit means Unexpected Completion, and CTO means Completion Timeout.Code:=============================================================================== Common Platform Error Record @ fffffa800f3b0038 ------------------------------------------------------------------------------- Record Id : 01cddc57248f101d Severity : Fatal (1) Length : 672 Creator : Microsoft Notify Type : PCI Express Error Timestamp : 12/17/2012 13:34:46 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : PCI Express ------------------------------------------------------------------------------- Descriptor @ fffffa800f3b00b8 Section @ fffffa800f3b0148 Offset : 272 Length : 208 Flags : 0x00000001 Primary Severity : Fatal Port Type : Root Port Version : 1.1 Command/Status: 0x4010/0x0506 Device Id : VenId:DevId : 8086:340c Class code : 030400 Function No : 0x00 Device No : 0x05 Segment : 0x0000 Primary Bus : 0x00 Second. Bus : 0x00 Slot : 0x0000 Dev. Serial # : 0000000000000000 Express Capability Information @ fffffa800f3b017c Device Caps : 00008021 Role-Based Error Reporting: 1 Device Ctl : 0107 ur FE NF CE Dev Status : 0005 ur FE nf CE Root Ctl : 0008 fs nfs cs AER Information @ fffffa800f3b01b8 Uncorrectable Error Status : 00040000 ur ecrc MTLP rof uc ca cto fcp ptlp sd dlp und Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und Uncorrectable Error Severity : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und Correctable Error Status : 00000000 adv rtto rnro dllp tlp re Correctable Error Mask : 00000000 adv rtto rnro dllp tlp re Caps & Control : 00000012 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP Header Log : 60000005 0900003f 00000004 b9486000 Root Error Command : 00000000 fen nfen cen Root Error Status : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer Correctable Error Source ID : 00,00,00 Correctable Error Source ID : 00,00,00
How many PCI and PCIe devices you have installed?
It may be caused by any of those.Code:0x0000D000-0x0000D0FF ATI Radeon HD 5900 Series OK 0x0000D000-0x0000D0FF Intel(R) 7500/5520/5500/X58 I/O Hub PCI Express Root Port 7 - 340E OK 0x0000D000-0x0000D0FF PCI Express standard Upstream Switch Port OK 0x0000D000-0x0000D0FF PCI Express standard Downstream Switch Port OK 0x0000C800-0x0000C8FF Realtek PCIe GBE Family Controller OK 0x0000E000-0x0000E0FF ATI Radeon HD 5900 Series OK 0x0000E000-0x0000E0FF PCI Express standard Downstream Switch Port OK 0x000003B0-0x000003BB ATI Radeon HD 5900 Series OK 0x000003B0-0x000003BB Intel(R) 7500/5520/5500/X58 I/O Hub PCI Express Root Port 7 - 340E OK 0x000003B0-0x000003BB PCI Express standard Upstream Switch Port OK 0x000003B0-0x000003BB PCI Express standard Downstream Switch Port OK 0x000003C0-0x000003DF ATI Radeon HD 5900 Series OK 0x000003C0-0x000003DF Intel(R) 7500/5520/5500/X58 I/O Hub PCI Express Root Port 7 - 340E OK 0x000003C0-0x000003DF PCI Express standard Upstream Switch Port OK 0x000003C0-0x000003DF PCI Express standard Downstream Switch Port OK 0x0000C000-0x0000CFFF Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40 OK 0x00000000-0x0000000F PCI bus OK 0x00000D00-0x0000FFFF PCI bus OK
If you are within warranty, contract your vendor, as the OP of the other thread did. But if (and only if; coz it may make the warranty void) the warranty is over, check it yourself, following Stop 0x124 - what it means and what to try, with a special reference of the step #9 ....
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Arc, see attached--this time it was a stop 0x00000122 error. How does it differ from the 000124 (121712-116688-01.dmp) on 12-17-2012.
Thanks in advance
That's another king od WHEA .... STOP 0x00000122: WHEA_INTERNAL_ERROR
From stacks,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 122, {a, 4, 3, 0} *** WARNING: Unable to verify timestamp for intelppm.sys *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys Probably caused by : pci.sys ( pci!ExpressRootPortAerInterruptRoutine+27f ) Followup: MachineOwner ---------
Overall, the same. Something is to do with the PCI and PCIe hardware. Have you contacted with the vendor? I may ask one of our forum member, who works for Dell.Code:STACK_COMMAND: kb FOLLOWUP_IP: pci!ExpressRootPortAerInterruptRoutine+27f fffff880`00e73bcf c78628050000ffffff7f mov dword ptr [rsi+528h],7FFFFFFFh SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: pci!ExpressRootPortAerInterruptRoutine+27f FOLLOWUP_NAME: MachineOwner MODULE_NAME: pci IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f FAILURE_BUCKET_ID: X64_0x122_pci!ExpressRootPortAerInterruptRoutine+27f BUCKET_ID: X64_0x122_pci!ExpressRootPortAerInterruptRoutine+27f Followup: MachineOwner ---------
Please do.
I have not contacted dell yet. My warranty goes to Feb 2014. I would like to know how Sabbyblue's replacement video card (he has a radeon hd 5800 series) does before I contact them.
The real odd part about this whole thing is that I have Windows 8 Pro 64bit and Windows XP SP3 32bit on this machine also with no BSOD's so far on these 2 systems. The 8pro has only been installed for 2 mos but the XP has been installed for almost 2 years.
The nagging question is why the BSOD's on the Win 7 64 only??
But I have had some anoying issues with the video card (radeon hd5900 series) on ALL 3 operating systems.
So if Sabby's machine is totally cured by replacing the video card, then I'll get mine replaced. The one difference is his is a 5800 series and mine is a 5900 series. So is the problem with the card or is it with the PCI-e slot on the motherboard? I just wonder how many more people are out there with this issue on these dell xps9100 machines.
Here is an interesting tidbit
Sabby's machine
Original Install Date: 2/16/2011, 11:32:24 AM
BIOS Version: Dell Computer Corporation A04, 10/21/2010
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 26 Stepping 5 GenuineIntel ~3200 Mhz
My machine
Original Install Date: 2/3/2011, 5:51:12 PM
BIOS Version: Dell Computer Corporation A04, 10/21/2010
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 44 Stepping 2 GenuineIntel ~3334 Mhz
I would really like to see GordonCCH's system info to see how it compairs to these machines!
I guess time will tell
I requested Debbie B to have a look ... he is offline now, but I am sure that he will reply shortly.
Hi Almondman,
I am extremely sorry for the inconvenience caused. If you still need any assistance, please send me Private Message with the Service Tag and your contact information ( Name & phone number). Will try to arrange a callback for you.
@Archie: Thanks for reffering me to this post.
I had a new BSOD this morning. First time I've seen this one.
Arc,
Could you let me know what it is? Something about MEMORY_MANAGEMENT???
Debbie B,
I've been away for a while and I'll get with you in a few days about this issue. By the way, I found another Studio XPS 9100 user that had the same problem with his 2 machines.
almondman, have a look, it is a stop 0x1A.
It is either a faulty RAM or any device driver failing, the particular dump is not saying anything very clearly. Better you try to search the cause of the crash in both the fields.Code:2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 000000000000e10c Arg4: ff5d8434ff5d8434 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003b4aafc to fffff80003ae2fc0 STACK_TEXT: fffff880`095789c8 fffff800`03b4aafc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000e10c : nt!KeBugCheckEx fffff880`095789d0 fffff800`03aef7ce : 00000000`00000001 00000000`27ee3000 fffff880`09578c20 fffff680`0013f718 : nt! ?? ::FNODOBFM::`string'+0x2983f fffff880`09578ac0 fffff800`03ae10ee : 00000000`00000001 00000000`27ee3000 00000000`0439ee01 00000000`00004000 : nt!MmAccessFault+0x5de fffff880`09578c20 000007fe`f3da3689 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`02bde3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f3da3689 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+2983f fffff800`03b4aafc cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2983f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2983f BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2983f Followup: MachineOwner ---------
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Let us know the results.