Windows 10: BSOD when writing to USB

Hello all,

I had some issues with BSODs and assumed I could solve the issue by moving to windows 10.
I had repaired files with sfc scannow but every time a new file was corrupted.
It appears it is a hardware issue as it has followed me after extensive virus scanning.
I think there is something wrong with the mainboard as PCI lane doesn't seem to matter.

I am just about to start A+ training course so forgive me for not being able to tease this one apart.

:)

 

XP SP2 BSOD when writing to D drive after Windows 10 accessed it

Picture below.

I also found that mounting the D: drive in Linux was causing an error as described here

Unable to mount Windows (NTFS) filesystem due to hibernation

The solution mentioned there i.e.

1. Open Control Panel in the small icons
view and click on Power Options.

2. Click on Choose what the power buttons do.

3. Click on Change settings that are currently unavailable.

4. Uncheck Turn on fast startup (recommended).

worked for mounting the D: drive in Linux. Is it possible that it will also fix it for XP?

It seems that Windows 10 on disk 0 is putting the ntfs volume on disk 1 into "hybernation" mode. Is there a way to keep fast startup, but to tell it not to put a second disc into hybernation mode? Can I mark it as a removable disk or something?

Note that the picture below is when the XP disc is inserted.





Same PC with Windows 10 disc. It seems to swap Disk 0 / Disk 1 compared with XP

 

XP SP2 BSOD when writing to D drive after Windows 10 accessed it

When you are in XP SP2, open Disk Management and take a snapshot of it. Post it here.

 

The recent one is apparently display related.
Code: BugCheck 119, {800, 6, ffffe001b49905f0, ffffe001b4991170} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSendToExecutionQueue+a2d7 ) Followup: MachineOwner ---------[/quote] And the display driver is not very latest.
Code: Image name: nvlddmkm.sys Timestamp: Thu Nov 05 20:05:23 2015 (563B692B)[/quote] Please install the 368.69 - WHQL.

Also, Stress test the Graphics Card using Furmark. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

THe older one is pointing to the memory.
Code: BugCheck 1A, {61941, 6ca8bda0, 1d, ffffd00022da4c40} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 4 instance(s) of page corruption, target is likely to have memory corruption.[/quote] Test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums