Windows 10: RDR_FILE_SYSTEM BSOD on specific model of PC?

We are using Windows 10 LTSB 2016 on some PCs in our organisation (the rest are still on Windows 7).


The majority of these do not have any issues but we have noticed that on one particular model of PC, users are sometimes getting an RDR_FILE_SYSTEM BSOD when accessing their network drive area.


I've collected the dump files from the most recent of these - a zipped copy of these can be found on OneDrive - can anyone suggest what might be causing the issue?


Thanks,

Dan Jackson (Senior ITServices Technician)

Long Road Sixth Form College

Cambridge, UK.

:)

 

Please help with RDR_FILE_SYSTEM (0x27) on Windows 10 during RDP

While connected over RDP (Remote Desktop Connection) and transferring files to the server, I've experienced the RDR_FILE_SYSTEM (0x27) BSOD. This just started happening now, the server was upgraded to Windows 10 several months ago and did not experience
this until now. It even crashed while being connected over RDP when no file transfer was being performed.

I ran memtest86 for 24 hours straight (5 full passes) and no errors were found.

I'm posting a link to several minidumps, all of which show RDR_FILE_SYSTEM BSODs during a file transfer except for the last 122316-45328-01 dump and accompanying memory.dmp that happened without a file transfer:

https://onedrive.live.com/?authkey=!AHy6s6w92BWpNg0&id=E5B7539FE8A63C1B!866&cid=E5B7539FE8A63C1B

I'd really like some insight into what might be wrong.

Thanks.

 

BSOD when using uTorrent


Could you be more specific on the model? The model given shows many different laptops.
Could you also check if HP has BIOS updates please, your laptop could use one.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?