BSOD leading me to believe Norton Anti-Virus is the cause

Sorry for the confusion.
The BSOD's w/ntoskrnl.exe/wpprecorder.sys/hal.dll are indicative of a separate problem.
As you haven't had any more bhdrvx64.sys BSOD's, I'd guess that Norton is no longer an issue.

Unfortunately, with the random BSOD's including hal.dll, I suspect either a hardware problem, or a lower level compatibility issue.

As you've run Driver Verifier already, please zip up the C:\Windows\Minidump folder ( right click on it, select "Send to", then select "Compressed (zipped) folder" and save it to your Desktop. Then upload it with your next post. Hopefully Driver Verifier will have generated a dump file for it's crashes and we'll be able to make some more suggestions on how to fix this.

If the system is still under warranty, they may insist that you wipe the system before returning it. If that's the case, don't forget to backup your stuff. And, if they ask you to send it in for them to look at, backup your stuff as the usual "test" is to wipe the system and install Windows "clean"

bro67 said:

Check all folders to make sure there is nothing left. Geek Uninstaller v1.4.6.140 Review (A Free Uninstaller) can help.

Thanks for the link, I have downloaded Geek Uninstaller and will run it shortly.

- - - Updated - - -

axe0 said:

Please don't forget to answer my question on the warranty.

axe0 , sorry. My warranty has expired.

- - - Updated - - -

jdc1 said:

Sorry for the confusion.
The BSOD's w/ntoskrnl.exe/wpprecorder.sys/hal.dll are indicative of a separate problem.
As you haven't had any more bhdrvx64.sys BSOD's, I'd guess that Norton is no longer an issue.

Unfortunately, with the random BSOD's including hal.dll, I suspect either a hardware problem, or a lower level compatibility issue.

As you've run Driver Verifier already, please zip up the C:\Windows\Minidump folder ( right click on it, select "Send to", then select "Compressed (zipped) folder" and save it to your Desktop. Then upload it with your next post. Hopefully Driver Verifier will have generated a dump file for it's crashes and we'll be able to make some more suggestions on how to fix this.

If the system is still under warranty, they may insist that you wipe the system before returning it. If that's the case, don't forget to backup your stuff. And, if they ask you to send it in for them to look at, backup your stuff as the usual "test" is to wipe the system and install Windows "clean"

I have run the Driver Verifier twice, but no dump files were generated. I must be doing something wrong. I will have to review the instructions and try again. Thanks for all the help.

Dump file generation is a complicated process - so don't blame yourself.
More info on dump file generation here: BSOD Crash Dump Generation

Did the system crash and not generate dump files?
Are you able to force the system to crash with Driver Verifier running? If so, force it to crash at least 3 times, run the V2 collector again, and then zip up the reports and upload them with your next post.

Beyond that, you can try doing a clean boot to see if that stops the BSOD's: Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

And, while waiting, you can try these free hardware diagnostics:
1) Memtest86 (not 86+): MemTest86 - Official Site of the x86 Memory Testing Tool

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): How to use SeaTools for Windows | Seagate Support US

3) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor

4) Furmark stress test for GPU: FurMark > Downloads
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: Hardware Stripdown Troubleshooting
Although it's old, it's still relevant in these situations.

Good luck!

jdc1 said:

Dump file generation is a complicated process - so don't blame yourself.
More info on dump file generation here: BSOD Crash Dump Generation

Did the system crash and not generate dump files?
Are you able to force the system to crash with Driver Verifier running? If so, force it to crash at least 3 times, run the V2 collector again, and then zip up the reports and upload them with your next post.

Beyond that, you can try doing a clean boot to see if that stops the BSOD's: Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

And, while waiting, you can try these free hardware diagnostics:
1) Memtest86 (not 86+): MemTest86 - Official Site of the x86 Memory Testing Tool

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): How to use SeaTools for Windows | Seagate Support US

3) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor

4) Furmark stress test for GPU: FurMark > Downloads
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: Hardware Stripdown Troubleshooting
Although it's old, it's still relevant in these situations.

Good luck!

I did have another BSOD, but the file was empty, so I could not unzip or upload it. I could not get the Driver Verifier to cause the laptop to crash. I will try it again and run the other test you suggested. Thnaks for all the help.

There's several reasons that a system may not crash using Driver Verifier - the most obvious being that there isn't any instability in the tested drivers (which implies that hardware problems are more likely).
Run Driver Verifier for a few days and see what happens. Often there's some evidence of the BSOD's in the V2 reports, so please create a new V2 report and upload it with your next post.

jdc1 said:

There's several reasons that a system may not crash using Driver Verifier - the most obvious being that there isn't any instability in the tested drivers (which implies that hardware problems are more likely).
Run Driver Verifier for a few days and see what happens. Often there's some evidence of the BSOD's in the V2 reports, so please create a new V2 report and upload it with your next post.

I am running the tests you suggested, so far no memory problems. You mentioned the V2 report, is that the report generated by Driver Versifier ?

Sorry (and thanks Ztrucker!) - yes the V2 is the log collector from the Posting Instructions.
It contains a lot of reports that make it easier for us to diagnose the system (and not have to continuously ask you to generate different reports).

[QUOTE=Ztruker;1707739]It's the V2 log collector here: Blue Screen of Death (BSOD) Posting Instructions [/

Thanks.

- - - Updated - - -

jdc1 said:

Sorry (and thanks Ztrucker!) - yes the V2 is the log collector from the Posting Instructions.
It contains a lot of reports that make it easier for us to diagnose the system (and not have to continuously ask you to generate different reports).

- - - Updated - - -

jdc1 said:

Sorry (and thanks Ztrucker!) - yes the V2 is the log collector from the Posting Instructions.
It contains a lot of reports that make it easier for us to diagnose the system (and not have to continuously ask you to generate different reports).

Thanks. Here is the V2 Log

PS - the only report from Driver Verifier is the BSOD that you get (and hopefully a dump file)

I see a couple of ath10x... errors on 31 Aug (to include BSOD's), and some Support Assistant errors on 01 Sep.
I'd suggest:
- uninstalling the Dell Support Agent (I've had problems with it within the last year at work)
- downloading a fresh copy of the latest Dell wifi drivers for your system. Then uninstall the old wifi driver package and install the new one.


Beyond that, I'd suggest that you finish up the free diagnostics that I mentioned earlier.
After the testing, I'd suggest 2 things as the final tests:
- physically remove the wifi card from the laptop (if you're able to access it) and uninstall the wifi software. Test to see if that helps. You'll have to use a wired internet connection while testing (if you have one). Wifi cards are fairly inexpensive - but that'll be your call (especially if you don't have a wired connection that you can use).
- backup your data (and make a disk image if you're concerned with setting the system back to the way it is today). Then do a clean install of Windows (either with the Dell recovery media, or the free, downloaded Microsoft Media Creation Tool). Don't add any 3rd party software - and see if that helps.

Unfortunately, with a laptop, there's not much that you can do to troubleshoot hardware.
There's only a few tests that are reliable, and there's not many components that you can remove to test it.