📎 AI Summary:
The thread discusses a Dell XPS 15 9550 experiencing frequent BSODs, primarily caused by driver issues related to network hardware, specifically ndis.sys and possibly incompatible Broadcom Wi-Fi drivers. The expert recommends updating all drivers via the official manufacturer page, running system scans (sfc /scannow and dism), and testing RAM with Memtest86 if the problem persists. The overall sentiment indicates that unresolved driver conflicts, particularly with network components, are causing the system instability.
Aniruddha Chauhan

Aniruddha Chauhan

New Member
Member details
Joined
Aug 31, 2017
Messages
1
Thread Author #1
I am working on Dell XPS 15 9550 Laptop with 512 GB SSD, I have been getting BSODs for quite some time now. My Windows is up to date and so are all the drivers. Once I reboot the Laptop it works perfectly fine then out of nowhere BSOD comes along.
I have attached the Report generated by the Diagnostic Tool in this thread. Kindly look into this matter.
Thanks !!
 

Attachments

  • RAWRRRR.rar
    RAWRRRR.rar
    1.7 MB · Views: 284
    Microsoft Defender: No threats detected Scan details
  • IMG_20170831_215916.webp
    IMG_20170831_215916.webp
    448.7 KB · Views: 405
    Microsoft Defender: No threats detected Scan details
Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffd1828b23c420, ffffa900a7c7f870, ffffd182972dd520}

Implicit thread is now ffffd182`9a0a0040
Probably caused by : ndis.sys ( ndis!ndisQuerySetMiniportEx+143 )

Followup:     MachineOwner
Hi,
all your dump files point to the same bugcheck 9F which basically means...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffd1828b23c420, ffffa900a7c7f870, ffffd182972dd520}

Implicit thread is now ffffd182`9a0a0040
Probably caused by : ndis.sys ( ndis!ndisQuerySetMiniportEx+143 )

Followup:     MachineOwner
Hi,
all your dump files point to the same bugcheck 9F which basically means a driver didn't cycle properly (turn on or off) .

After studying the dump files it seems the bsod is network related with something causing this Windows driver to crash:
Raspppoe.sys

Further investigation leads me to believe it's this driver causing the problems:

bcmpciedhd63.sys Sat Sep 26 01:30:18 2015: Broadcom wifi driver.

Is this something you have added yourself like a wifi USB stick or similar? The reason I ask is because i checked your systems manufacturer page for drivers and couldn't find any Broadcom drivers, laptops must use drivers supplied by the manufacturer (apart from gpu drivers) otherwise blue screens can occur.
Never ever be tempted to use a driver finding application..
Here is your system support page:
Link Removed

Please update your drivers as there are later versions.

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

If the bsod continues and because memory corruption was mentioned in a number of dumps you'll need to test your RAM. Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool

Please post any new dump files.
 
Upvote 1 Downvote
Solution
You must log in or register to reply here.