Windows 10: BSOD Dell Latitude E6220 0x000009f

Hi folks

I have a Dell laptop that was runnning Windows 7. It was BSODing regularly, so I swapped out the hard drive and did a clean install of Windows 7, then upgraded it to Windows 10.

Unfortunately, it's BSODing again unfortunately.

It's been fine all day running on mains power, however a couple of hours ago I moved to a different location and ran on battery. During this time, I had 3 BSODs. I'm back on mains power again and it seems to be OK (fingers crossed).

The BSODs seem to occur randomly. A couple of times I was browsing on the web. Another time, the laptop was just sat idle.

I've attached the diagnostics ZIP file. I'd be grateful if someone could have a look at it and see offer thoughts.

Thanks

Al

:)

 

Bluetooth

Hello Microsoft

Recently I bought a Bluetooth Microsoft Designer peripheral set, which worked great for the past few months. Because I am running on a Dell Latitude E6220, I had to purchase a Bluetooth USB chip. I did, and just today, it stopped working. I just left
it there, and it stopped working. I shook it and I didn't here anything rattling, so there was no physical damage. Please help!

Thanks,

Issra Ali

 

Windows Hello unsupported on my computer

Hi Linda,

Windows Hello is a security system designed by Microsoft that uses bio metrics to log you into your Windows 10 laptop. To take advantage of facial recognition, your device needs a special kind of camera that can scan your face, so not all laptops with webcams
are compatible. Kindly check the list which compatible with Windows Hello.

• Dell Inspiron 13 5379 2-in-1
• Dell Inspiron 13 7370 2-in-1
• Dell Inspiron 13 7373 2-in-1
• Dell Inspiron 15 5567
• Dell Inspiron 15 5579 2-in-1
• Dell Inspiron 15 7570
• Dell Inspiron 15 7573 2-in-1
• Dell Inspiron 17 7773 2-in-1
• Dell Latitude 12 5280
• Dell Latitude 12 5285 2-in-1
• Dell Latitude 12 5289 2-in-1
• Dell Latitude 12 7280
• Dell Latitude 12 7285 2-in-1
• Dell Latitude 13 3379 2-in-1
• Dell Latitude 13 7380
• Dell Latitude 13 7389 2-in-1
• Dell Latitude 14 3000
• Dell Latitude 14 3480
• Dell Latitude 14 5480
• Dell Latitude 14 7480
• Dell Latitude 15 3580
• Dell Latitude 15 5580
• Dell Inspiron 15 5570
• Dell Inspiron 17 5770
• Dell Latitude 11 5000 2-in-1
• Dell Latitude 12 5285 2-in-1
• Dell Latitude 12 5289 2-in-1
• Dell Latitude 12 7000 Rugged
• Dell Latitude 13 7000
• Dell Precision 15 7000
• Dell XPS 13
• Dell XPS 13 2-in-1
• Dell XPS 15

Keep us posted if you need additional help.

 

Hi Slarty,

Welcome to the 10forums.

It seems there are 3 windows drivers blamed in the crashes.
Because windows drivers are rarely the real cause I want to try a few things

First we need to be sure there is no corruption, missing files or other problems with the system files.

Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

If sfc fixes the problem, then driver verifier may be ignored.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Thanks

I've attached the CBS log. I'm going to run the driver verifier next.

Al

 

I don't see any problem, did sfc not say "Windows Resource Protection did not find any integrity violation"?

 

Well I ran the laptop with driver verifier running for a few days and it's been OK. However yesterday evening I had two or three BSODs. It was trying to connect to a fairly weak WiFi network, so I wonder if it's those drivers that's causing the problem?

Anyway, I've attached the CBS.zip file. Can you have a look at it please.Attachment 38791

Thanks

 

What did sfc say?
I don't see any corruption or missing files.

Please use the tool again and upload the zip file.