- Joined
- Jan 8, 2020
- Messages
- 833 (0.53/day)
- Location
- Maryland, USA
| Processor | Ryzen 5 5600X |
|---|---|
| Motherboard | MSI MPG X570S Carbon Max Wifi |
| Cooling | CPU: bequiet! Dark Rock 4. Case fans: 2x bequiet Silent Wings 3 140s, 2x Silent Wings 3 120s |
| Memory | 2 x 8 GB Patriot Viper Steel DDR4-4400 C19 |
| Video Card(s) | Sapphire NITRO+ RX 5700 XT |
| Storage | 2TB Mushkin Pilot-E M.2, 1 TB SK Hynix P31 M.2, 1 TB Inland Professional, 500 GB Samsung 860 Evo |
| Display(s) | MSI Optix MAG271CQR 1440p 144Hz, MSI Optix MAG241C 1080p 144Hz |
| Case | Lian Li Lancool III |
| Audio Device(s) | Philips SHP9500, V-Moda BoomPro, Sybasonic Better Connectivity USB DAC/Amp |
| Power Supply | EVGA SuperNOVA G3 80+ Gold 750W |
| Mouse | Glorious Model D Wireless |
| Keyboard | Custom Qwertykeys Navy QK80: Sarokeys Strawberry Wine switches, GMK CYL DMG3 keycaps |
Have a client at work that's getting System Service Exception BSODs when trying to access external drives in Windows Explorer. After the BSOD, the client enters a boot loop that is only resolved by fully powering off the machine. He's able to browse the drives via CLI without error. I believe the drives are Seagate external HDDs (Seagate Backup Plus Hub BK). We replaced the drives which didn't solve the problem. The client was getting the BSODs with USB flash drives also. Updating the Intel Management Engine driver and the Intel Rapid Storage Tech driver solved the problem for USB flash drives but trying to browse the external HDDs still cause BSODs. Using a USB hub didn't help.
The client is running a 6700K (at stock from what I can tell) in an ASRock H110M-ITX board. BIOS is up to date (7.20). I'll have some time on the machine tomorrow morning, but we're getting to the point where my boss doesn't want us spending any more time on this issue given that it's a custom-built machine and not one of our standard deployments.
The client is running a 6700K (at stock from what I can tell) in an ASRock H110M-ITX board. BIOS is up to date (7.20). I'll have some time on the machine tomorrow morning, but we're getting to the point where my boss doesn't want us spending any more time on this issue given that it's a custom-built machine and not one of our standard deployments.
