Random BSOD Windows 10

I have been trying to figure out this BSOD for about a week now, and have given up.  I need your help.

I have ran WinDbg x64 on the MEMORY.DMP file on a remote computer, and so far it seems when I have verifier.exe activated, the BSOD is related to CI.DLL.  I have since ran an in-place upgrade of Windows 10 (1607), but I still get BSOD's.  I will upload the latest minidump file.

According to WhoCrashed,

crash dump file: C:\WINDOWS\Minidump\101416-22953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0xC6)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Can anyone help me track this down?
101416-22953-01.zip
LVL 8
Scott ThompsonComputer Technician / OwnerAsked:
Who is Participating?
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
By going one at a time, I think I've worked down the BSOD's to be caused by the Intel Rapid Storage Technology driver.  Now, whether that's being caused by the version of the driver, the OS, the software (Intel's), or the HDD, I don't know.  Any suggestions?  I have already uninstalled the software and reinstalled from Dell's website.
0
 
Dustin SaundersDirector of OperationsCommented:
What sort of antivirus are you running on this machine?
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Frontier Secure version 2.50.214.0
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
Paul MacDonaldDirector, Information SystemsCommented:
Have you run SFC /SCANNOW yet?  Might be worth a shot.
0
 
JohnBusiness Consultant (Owner)Commented:
In addition to the above, go to the support site for the computer manufacturer and download / install updated BIOS, Chipset and Video drivers. If there are new Network Drivers, update those as well.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Yes, sfc scannow found no issues.  I also ran DISM.exe /online /cleanup-image /scanhealth, /startcomponentcleanup, and /restorehealth
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Oh, I'm sorry, I forgot to post the model of laptop.  Dell Inspiron 3721, Service Tag BHCQ2X1
0
 
rindiCommented:
Wait until you have at least 3 minidumps, and then zip those and attach it. One alone doesn't say much.
0
 
JohnBusiness Consultant (Owner)Commented:
Also try driver updates as suggested
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
For some reason, the Dell website is not behaving today.  I have another minidump file from before I did the in-place upgrade.

The other problem is I can't figure out how to consistently cause the BSOD.
101316-27015-01.zip
0
 
Dustin SaundersDirector of OperationsCommented:
Minidumps can help to a certain point, but if it's a pretty generic item you'd want to use the full dump to see what was loaded into memory at the point of the fault.

How often does it BSOD?  Can you try a different AV for a week and see what happens with it?  The only time I've seen the WATCHDOG error was with AVG, and in those instances when we changed to Vipre the problems went away.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Okay, unfortunately it's a customer's computer, so I don't know if they would want to go with a different antivirus, but I can always check.  Frontier Secure is provided by Frontiernet as part of the service and I believe they pay for it.  Here's a couple more minidumps since I last left a message.

Oh, and I have it doing a COMPLETE Memory dump also, but can't figure out how to read exactly what's causing it.
101416-17296-01.zip
0
 
rindiCommented:
A complete memory dump won't give us any better idea of the problem. All it does is waste disk space, and it will probably be too large to attach to a comment.

Test your RAM using memtest86+. You'll find it on the UBCD:

http://mirror.sysadminguide.net/ubcd/ubcd536.iso

If there are errors in the memory test, replace the bad memory. If it is fine, then look at thinkpad's suggestions, as the problem is likely to be caused by bad drivers then.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
I have ran memtest 86+, but I will have it run all night and see if there are any issues.
0
 
Dustin SaundersDirector of OperationsCommented:
A complete dump is the best way to find the problem- the reason it's so large is because it gives you everything loaded into memory and you can use the faulting thread to find the pool where the fault actually occurred, and you can see what was loaded at the time.  If you are able to put a full dump somewhere I can get it, I'll take a look at it (this weekend at some point) and see what I can find but I would probably still recommend trying to temporarily turn off that AV and see what happens.
0
 
nobusCommented:
i would install an OS on a spare drive, and run that to see if the BSOD's come back
intermittent problems are best attacked like this : elimininating parts or softwares
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Here's pictures of the memtest 86+ I had run all weekend.
20161017_085704-1-.jpg
20161017_085700-1-.jpg
20161017_085653-1-.jpg
0
 
JohnBusiness Consultant (Owner)Commented:
The pictures seem to suggest no memory errors.

Is the Dell Website working? Did you try driver updates as suggested (BIOS, Chipset, Video)?
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
I will take a look at the dell Website after I try a formatted drive and install Windows 10.  Oh, here's a transcript of Windbg x64 since the memory.dmp file is 6GB.
DebugDell.txt
0
 
rindiCommented:
Those images you posted aren't from memtest86+. I have found that only memtest86+ is reliable, all others often will tell your the memory is fine even if it isn't, while memtest86+ at the same time said that RAM was bad.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Isn't it Passmark memtest 86+?  That's what I posted the pictures from (taken from my phone)
0
 
rindiCommented:
It doesn't have the "+" at the end. On the UBCD there is more than one memory testing tool, but only one is called "memtest86+".
0
 
nobusCommented:
it is worth testing with memtest86+ from www.memtest.org
they are clearly different
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Hello again,

So far with the replacement drive, fresh load of Windows, and installing all the proper drivers, it seems to be working fine.  I currently have verifier turned on waiting to see if it crashes.  Maybe it is their antivirus causing it.  Is there any way to tell what program is causing it?
0
 
JohnBusiness Consultant (Owner)Commented:
Open Control Panel, Security and Maintenance, pull down Maintenance and run Reliability History. Conflicting software causing crashing should show up here.

Also almost ALL antivirus needs new versions after the August 2 Anniversary Update. Get new AV versions for your systems.
0
 
nobusCommented:
check that the system is set to make minidumps, and post them if it happens
then we can see if they're the same
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
I have put the original drive back in and checked Security and Maintenance.  Just the BSOD's, but no program issues listed.  Have not had it crash again yet.  I love the intermittent waiting :(
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Here's the latest minidump...

On Tue 10/18/2016 8:27:28 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101816-25640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80188E30248)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/18/2016 8:27:28 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80188E30248)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
101816-25640-01.zip
0
 
JohnBusiness Consultant (Owner)Commented:
checked Security and Maintenance.  Just the BSOD's, but no program issues listed  and from your dumps, you have driver issues

http://answers.microsoft.com/en-us/windows/forum/all/win7-bsod-daily-whocrashed-logs-attached/83ca593c-d8bb-464e-abbf-f958c0b110c9

The answer here is drivers.

Did you get Chipset (and Video) in ALL your drivers?
0
 
rindiCommented:
Look for driver updates for your wireless card. Or disable the wireless LAN or remove the card.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
John Hurst,

I am confused by your link, since it doesn't seem to have any answers besides the standard 'Update Windows, Drivers, Programs' scenario.  But, I will uninstall and reinstall ALL drivers and see if that helps.
0
 
JohnBusiness Consultant (Owner)Commented:
Sorry for the confusion. I am suggesting the Dell Site for driver updates. Get them there and install. I hope that helps.
0
 
nobusCommented:
i can only add that i was unable to read your minidumps
0
 
rindiCommented:
I've just realized I have analyzed the wrong minidump.

Have you meanwhile run the correct memtest86+? Also test the HD using the manufacturer's utility (they are also included on the UBCD). If it is an SSD, download it's utility from the manufacturer's website, and run that. Those tools normally also check whether the firmware of the SSD is current. If it isn't, allow it to update it.
0
 
nobusCommented:
rindi - could you read the dmp?  i got "wrong symbol file" error
0
 
rindiCommented:
Yes, I was able to analyze it, but it is one of those general dumps that can have many causes, like drivers, bad disks, RAM etc. That's why he should test his RAM using memtest86+ and the disk manufacturer's diagnostic before going any further.
0
 
nobusCommented:
then something went wrong on my installation...tx for the feedback Rindi
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
I'm running Memtest 86+ 5.0.1 from UBCD right now.  To update you, I have reinstalled ALL drivers on the system for Dell.  The BIOS did not need updated as it is running the latest version provided by Dell.  I did have a BSOD this morning, but it did not save a minidump file or memory.dmp file for some reason.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Here's a picture of the memtest 86+ 5.0.1.

Memtest
0
 
rindiCommented:
Run at least 2 more passes to make sure. After that test your disk with the manufacturer's tool.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Dell Diagnostics
Here is the Dell Diagnostics Through test.  Everything passes.
0
 
rindiCommented:
Not the Dell tests. Run the disk manufacturer's diagnostics.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Latest Memtest 86  5.0.1 Passes
0
 
rindiCommented:
OK, the RAM is OK. Next test the disk.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
SeaTools
Here is the SeaTools Long Run.
0
 
nobusCommented:
does the laptop get hot?  overheating can cause it also
install speedfan - and monitor the temps  http://www.almico.com/speedfan.php
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
The laptop does not get hot.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
0
 
JohnBusiness Consultant (Owner)Commented:
I have had Intel RST drivers cause Stopped Working errors but not Blue Screen crash.

Try Intel drivers:

https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver

Also:

https://downloadcenter.intel.com/download/26361/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver?v=t

where they say a newer version is available.
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Both of those drivers say system  is not supported.
12.8.2.1000 Intel Rapid Storage Technology is what is currently installed.
0
 
JohnBusiness Consultant (Owner)Commented:
The RST driver for my Lenovo desktop is V14. 5.0.1081
0
 
Scott ThompsonComputer Technician / OwnerAuthor Commented:
Finally determined that I need to install and OLDER version of the Intel Rapid Storage Technology driver.  I do not remember what version I installed, but it has not BSOD'ed since.  Hopefully it will be fine back in the customer's hands.  Thank you for your assistance.

Oh, I selected my answer as the best answer since it points to the actual culprit, but gave John Hurst the credit since drivers was his suggestion.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.