You're welcome, and good luck!
BSOD
I have an issue with a BSOD on a new (purchased in December) laptop, and would be grateful for any help.
I collected the dumps, MSinfo output, and specifications and put them here on OneDrive: https://1drv.ms/f/s!AstAdIvnzcozgTa\_YeXFaXOI-CwU
I got this laptop for my wife, and she was very happy with it until it began having regular BSODs.
She says that the BSODs usually occur when she attempts to open a new tab in a browser (she mostly uses Chrome).
I have tried to fix the error by making sure software updates have been applied; and in particular by using Dell's tool to get the latest Dell drivers, patches, and so on. Yet the BSOD keeps happening.
If any of the Win10 experts here could help me understand what's causing this issue, I would very much appreciate it.
Thanks in advance for any assistance!
Best regards,
Chris
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
3 answers
Sort by: Most helpful
-
Anonymous
2019-05-14T00:27:34+00:00 -
Anonymous
2019-05-13T23:55:46+00:00 Thank you very much, @auggy. I will try those solutions and post again about whether they solved the problem.
-
Anonymous
2019-05-11T05:20:48+00:00 Hi,
The BSOD is network related and there appears to be a clash between Forticlient drivers and the drivers for the Killer E2400 network adapter:
BugCheck D1, {ffffba8cf3d93ff8, 2, 0, fffff80313c03390}
*** ERROR: Module load completed but symbols could not be loaded for SmbCo10X64.sys
*** ERROR: Module load completed but symbols could not be loaded for fortisniff2.sys
Probably caused by : SmbCo10X64.sys ( SmbCo10X64+13390 )
BugCheck D1, {ffffcd8f18fefff8, 2, 0, fffff80124187410}
*** WARNING: Unable to verify timestamp for RfeCo10X64.sys
*** ERROR: Module load completed but symbols could not be loaded for RfeCo10X64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : RfeCo10X64.sys ( RfeCo10X64+17410 )
The SmbCo10X64.sys and RfeCo10X64.sys are Killer network control drivers (not drivers for the adapter itself) and appear to be the issue.
Try updating the Killer software/drivers:
https://support.killernetworking.com/download/killer-software-package-for-windows-10-1803/
If the issue persists you could try uninstalling the Killer software and update the Killer driver using "Drivers Only Installation":
https://support.killernetworking.com/download/killer-drivers-installation-64bit/