Windows 10: Repeated Problems with BSOD

Dear MS community,


for the past few weeks, I have been experiencing severely annoying BSODs of different nature. Before these weeks, I never got one of those, fortunately.


However, today my PC crashed with the error code or whatever: "WDF Violation". The past few days, it usually crashed with the SYSTEM_SERVICE_ERROR exception, referring to cldflt.sys.


As I am really not sure what details to post here, I will just go with an XML description of the error from the Event Log.


Your help would be kindly appreciated. Thanks!

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-11-06T15:03:55.565333100Z" />
<EventRecordID>8666</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>dolan</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">0x0000010d (0x0000000000000005, 0x00002b7ec5d86fd8, 0x0000000000001018, 0xffffd48125b3cd70)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">46d8f7a2-97bb-4f2b-bc29-0622207eaad6</Data>
</EventData>
</Event>

:)

 

Nvidia driver problem with 940 MX on Windows 10 x64


I would only go back to the driver from the computers manufacturers if you experience any issues with the latest drivers from devie manufacturers.

If everything is still working well with the clean boot then you can start troubleshooting as follows to start:

How to determine what is causing the problem after you do a clean boot


1. Log on to the computer by using an account that has administrator rights.
2. From Start, search for msconfig. (In Windows 10, use the Search box from the Start menu. In Windows 8 or 8.1, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.)
3. Select msconfig or System Configuration from the search results.
4. Tap or click the Services tab, and then tap or click to select the Hide all Microsoft services check box.
5. Tap or click to select the upper half of the check boxes in the Service list.
6. Tap or click OK, and then tap or click Restart.
7. After the computer finishes restarting, determine whether the problem still occurs.
• If the problem still occurs, repeat steps 1 through 6, but clear the lower half of the check boxes in the Service list that you originally selected.
• If the problem does not occur, repeat steps 1 through 6, and select only the upper half of the remaining check boxes that are cleared in the Service list. Repeat these steps until you have selected all the check boxes.
• If you still experience the problem when only one service is selected in the Service list, this means that the selected service causes the problem, and you should go to step 11. If no service causes the problem, go to step 8.
8. Repeat steps 1 and 3 in this section.
9. Tap or click the Startup tab, and then tap or click to select the upper half of the check boxes in the Startup Item list.
10. Click OK, and then click Restart.
• If the problem still occurs, repeat steps 8 and 9, but clear the lower half of the checked boxes in the Startup Item list that you originally selected.
• If the problem does not occur, repeat steps 8 and 9, and select only the upper half of the remaining check boxes that are cleared in the Startup Item list. Repeat these steps until you have selected all the check boxes.
• If you still experience the problem after only one Startup Item is selected in the Startup Item list, this means that the selected Startup Item causes the problem, and you should go to step 11. If no Startup Item causes this problem, a Microsoft service probably causes the problem. To determine which Microsoft service may be causing the problem, repeat steps 1 through 7 without selecting the Hide all Microsoft services check box in each step.
11. After you determine the startup item or the service that causes the problem, contact the program manufacturer to determine whether the problem can be resolved. Or, run the System Configuration utility, and then tap or click to clear the check box for the problem item.
From <https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows>

 

repeated BSOD after Windows 10 upgrade

Since upgrading to Windows 10 a month ago, I have been getting repeated BSOD crashes on my Lenovo Yoga 2 Pro. Typically, I'll get a "critical process died" BSOD while using Windows, and then when my computer reboots I get an "unmountable boot volume" BSOD.
Once this happens, it tends to happen every time I try to boot in, though every now and then it allows me to log in.

I have taken the following steps (multiple times) to address the problem:

I have scanned for viruses, with none reported.

I have run Windows update.

I have update my device drivers.

ran sigverif.exe

no problems reported

ran sfc /scannow

no integrity violations

ran DISM /Online /Cleanup-Image /RestoreHealth

the restore operation completed successfully

re-ran sfc /scannow

no integrity violations

ran chkdsk

no problems found

I know others have encountered similar problems, but I haven't found a solution. Does anyone have a suggestion?

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast: