Windows 10: BSOD when trying to map driver

Hello, I am mapping a driver by dragging a .sys file into an .exe for a video game. Now it uses NAL which is in use so I am running NalFix.exe which is described by the owner as The way this tool works is by iterating over all Kernel services, getting the Binary path and scanning each binary for the Device\Nal string. I didn't find a better way to associate a symbolic link to a service, maybe I missed something, but it works. But then once i try to map the driver it gives me a BSOD with SYSTEM THREAD EXCEPTION NOT HANDLED. I have analyze minidumps and got the following*************************

:)

 

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:

 

Windows 10 maps

To narrow down your concern, we would like to know the following:

• Have you tried using another USB in saving your offline maps?
• Were you able to update your drivers? We suggest that you check if your drivers are up to date by following the steps on this
  link.
  

For your reference, below are the steps to save Offline Maps to USB:

• Click on Start; then, Settings.
• Select Maps; then, Storage Locations.
• Click on the Change where you store offline maps drop down menu and choose the
  new location.

We will be waiting for your response.

 

Connecting NAS - mapping of drives

Ok, If you want, we can do a step by step troubleshooting of your current situation: If you are able to ping your Machine and it responds. Code:

Try to view if your NAS appears on the Network List: Code:

If Your NAS appears on the list, try to view it: Code:

The available shares will be listed there. Then Try to List the content of one of the directories: Code:

This should list the content of the directory, If all this works Try to map a drive on one share: Code:

Pls reply with the "response" of the first "encounter" of a non positive output. This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.