Backing up to a M.2 SSD
Windows 10 Professional x64 OS - Acronis TI Home 2018 Build 11530
No problems backing up to a WD Blue 3D NANA 1TB 2.5" SATA SSD
Problem backing up to a Samsung 960 Pro 512GB M.2 drive. Every time (I have tried many times) I try I get the BSOD.
Is there an issue writing an image to an M.2 drive?


- Se connecter pour poster des commentaires

ASRock Z370 Professional Gaming i7 LGA 1151 (300 Series) Z370 ATX Intel Motherboard |
M.2 1 | Samsung 970 EVO M.2 500 | MZ-V7E500BW |
M.2 2 | Samsung 960 PRO M.2 512 | MZ-V6P512BW |
M.2 3 | Samsung 960 EVO M.2 250 | MZ-V6E250BW |
PCIe 4 | Samsung 960 PRO M.2 512 | MZ-V6P512BW |
SATA | WD Blue 3D NAND 1TB | WDS100T2BOA |
SATA-CADDY | Corsair Neutron Xti | CSSD-N240GBXTI |
M.2-1 Professional
M.2-2 Spare*
M.2 -3 DATA
PCIe slot 4 - Spare*
SATA & SATA Caddy - Asmedia Conroled SATA 3 ports
*these 2 drives will not accept images - BSOD - I can copy data to them in File Explorer
- Se connecter pour poster des commentaires

If you remove one of the spares, say the M.2-2, can you write to the PCIe-4 drive? If you remove the PCIe-4 drive from the equation and leave the M.2-2 drive installed can you write to the M.2-2 drive?
I am thinking there might be a limitation in the product with your configuration. Which drive(s) are you attempting to backup from here? Are there any RAID arrays in play? Do you occasionally loose drives due to initialization failure during boot, (drives not appearing in Explorer or Disk Management after startup)?
- Se connecter pour poster des commentaires

Removed PCIe drive - can't write to M.2 - 2.
Removed both - can't write to M.2-3
No RAID arrays
Do not lose drives due to initialization failure during boot
Now that the sun is up here, and I've had some coffee :-) - I noticed the following on the BSOD:
STOP CODE
Driver IRQL Not less or Equal
I have no idea what this means - but at least have a starting point for research
Sorry for not including this tidbit of info earlier - and thank you for your time Enchantech
ETA - 2nd machine has an ASUS ROG Maximus X Hero mobo with 2 M.2 slots and a PCIe adapter - all have M.2 drives. Tried backing up to M.2 drives and all went well. Had never tried this operation the ASUS machine before. Now I know the issue is somewhere in the ASRock machine setup.
ASUS has ATI 2017
ASRock has ATI 2018 - 2017 didn't work on this machine either.
NOT and ATI issue.
- Se connecter pour poster des commentaires

The BSOD means a driver attempted to access paged memory at an address that was invalid while it had a raised interrupt request level.
Figure out the offending driver, uninstall it, then install the latest version in its place.
I caution against simply updating the driver as in my experience that rarely works.
- Se connecter pour poster des commentaires
En réponse à The BSOD means a driver… par truwrikodrorow…

How do I figure out which driver it is?
This is a fairly new build, so I think I have the latest drivers from the ASRock site
- Se connecter pour poster des commentaires

Use Windows Computer Management, Event Viewer to look for the BOSD"s. These should specify the faulting driver Common name. You can then Google the name and find out what the driver is for.
You can also Google the event ID for more on the cause. I find manufacturer support sites slightly behind the curve on most drivers. The hardware makers themselves are usually more up to date .
- Se connecter pour poster des commentaires

Will do thanks - agree on the hardware makers being more up to date.
- Se connecter pour poster des commentaires