Windows 10: BSOD, maybe spool\V4Dirs\ related

I've been getting a BSOD every week or so. I don't seem to be doing anything in particular when it happens.

No minidump or MEMORY.DMP files are ever created even though I have verified in system setup that these should be created. I do have a PRFO.log file, which gets written to each time I get a BSOD (and only when I do). Here is its info from the last two BSODs:

Last week's:

10/10/2018 10:47:59 - PFRO Error: \??\C:\Program Files\Mozilla Firefox\tobedeleted\moz16fb2cdb-59e1-46a4-a2bd-60ec0c403004, |delete operation|, 0xc000003a
10/10/2018 10:47:59 - PFRO Error: \??\C:\Program Files\Mozilla Firefox\tobedeleted\, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYM.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMB.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYML.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMSB.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMSL.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMXL.TTF, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\fonts\flat_officeFontsPreview.ttf, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - PFRO Error: \??\C:\WINDOWS\system32\spool\V4Dirs\FD4EEC5A-75FA-4296-B491-14673445B309\94766af2.gpd, |delete operation|, 0xc0000034
10/10/2018 10:47:59 - 11 Successful PFRO operations

Today's:

10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\TEMP\INS_ff72ec17.TMP, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\TEMP\NvidiaLogging, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\TEMP\NvidiaLogging, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\Users\Tine\AppData\Local\Temp\TeamViewer\update.exe, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYM.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMB.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYML.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMSB.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMSL.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\OFFSYMXL.TTF, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\fonts\flat_officeFontsPreview.ttf, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - PFRO Error: \??\C:\WINDOWS\system32\spool\V4Dirs\C58F4260-7E44-4909-B9F2-3220D383CE41\94766af2.gpd, |delete operation|, 0xc0000034
10/17/2018 19:25:8 - 31 Successful PFRO operations


Any help would be much appreciated!

:)

 

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:

 

Print Spooler Service Stopping


I followed the steps you listed. When I opened C:\Windows\System32\spool\PRINTERS, it was empty.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.