Skip to main content
Start a Conversation

Unsolved

D

DDWillens

5 Posts

15281

February 20th, 2019 18:00

XPS 9570 BSOD when using wireless ONLY (not LAN)

So I have had my 9570 for six months and I am now getting frequent BSODs whenever I remove the laptop from the LAN connection (through Thunderbolt dock) and try to use it via wifi.  The BSOD is WHEA UNCORRECTABLE ERROR but the dump files are all over the place showing all sorts of different things.  After extensive troubleshooting including testing memory (fine) and SSD, updating Win10 and drivers, nothing worked.  I gave up and restored the laptop to the original system image from Dell (I did note that the BIOS was immediately 1.7 so it must have done that in the background while reinstalling the original system image?)  Same thing.  Works absolutely perfectly on LAN, within 5-30 minutes after I get on wifi it gives me the BSOD.

So does anyone think this could be anything OTHER than a network card/driver issue?  I don't want to send this back to Dell and wait weeks for them to send it back to me if I can just fix it with the $15 Intel wi-fi card.  I just can't imagine what else it could be that would make for a perfectly functioning laptop at all other times.

Any thoughts would be greatly appreciated!

Damon

mvrh

49 Posts

February 21st, 2019 04:00

Hi,

This absolutely sounds like a driver or hardware issue. Did you try re-installing (not updating/upgrading) the Wi-Fi drivers? As in uninstalling it and deleting the driver software for the device, then installing the latest driver for your OS?

Anything in the device manager or event viewer that might give any hints?

Mark

DDWillens

5 Posts

February 21st, 2019 07:00

I completely restored the laptop to original factory settings through the boot menu option to restore factory image. (Windows 10 Home).  It was fine last night while I was working on it, then I left it idle overnight, then I started working on it again this morning and it almost immediately started again BSOD with WHEA_UNCORECTABLE_ERROR.  I don't really see anything helpful in the event viewer.  All of the most recent .DMP files are showing WIN8_DRIVER_FAULT in the bucket ID but the process names are different each time.  I've now rebooted several times just in the past few minutes and it doesn't last very long before it crashes (again only on wifi).  In fact it crashed while I was reading your post.

I am not sure what you mean by uninstalling and reinstalling the driver.  Isn't that what restoring the original factory image would have done?  I can uninstall the driver and reinstall it if necessary to try to troubleshoot.  Not sure where to find the original driver though.

Device manager doesn't show any problem drivers and when I tested the network card with Dell SupportAssist it worked ok.  In fact I ran the entire Dell SupportAssist stress tests last night and it worked fine.

Because of the seeming randomness of all this it makes me think that it is a hardware issue and not a driver issue.  But I am certainly not any kind of expert.

Here's the first parts of the two .DMP files:

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: ffff9d8c69ad7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000011000402, Low order 32-bits of the MCi_STATUS value.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

 

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: ffff880b965f3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000011000402, Low order 32-bits of the MCi_STATUS value.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  f

 

DDWillens

5 Posts

February 21st, 2019 08:00

ps this is really odd.  When I checked SupportAssist history just now it lists the BSODs and it gives completely different information on them, with an Intel graphics kernel error.  ???

February 21, 2019 - Thursday
Blue Screen Error - February 21, 2019 6:43:31 AM
Bug check code
0x00000124
Bug check parameters

0x0000000000000000,

0xffff9d8c69ad7028,

0x00000000ba000000,

0x0000000011000402

Device name
Intel Graphics Kernel Mode Driver
Driver version
24.20.100.6287
Driver path
C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dc_base.inf_amd64_2e0115c93a163d68\igdkmd64.sys
Blue Screen Error - February 21, 2019 6:17:14 AM
Bug check code
0x00000124
Bug check parameters

0x0000000000000000,

0xffff880b965f3028,

0x00000000ba000000,

0x0000000011000402

Device name
Intel Graphics Kernel Mode Driver
Driver version
24.20.100.6287
Driver path
C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dc_base.inf_amd64_2e0115c93a163d68\igdkmd64.sys

DDWillens

5 Posts

February 21st, 2019 09:00

Even though I had already reimaged the whole machine back to original factory settings, I went ahead and tried your idea to uninstall and reinstall the network card driver.  So I am now running the latest Killer driver (NOT what Dell says is the most current driver,).  So we shall see what happens now.  After this I think I give up and will RMA back to Dell in Houston (yuk).

DDWillens

5 Posts

February 21st, 2019 09:00

Nope.  New network drivers didn't work either.  Sigh.

View More

View All

No Events found!

Top