F5F Stay Refreshed Software Operating Systems Windows 10 crashing because of a USB device.

Windows 10 crashing because of a USB device.

Windows 10 crashing because of a USB device.

Pages (2): Previous 1 2
S
ScoutandMilo
Member
71
01-28-2016, 07:19 AM
#11
Running on Windows 10 Pro version 10240, successfully creating files from the laptop without problems. Clock was adjusted back to default using CMOS reset. Other machines using Fedora 22 also worked fine.
S
ScoutandMilo
01-28-2016, 07:19 AM #11

Running on Windows 10 Pro version 10240, successfully creating files from the laptop without problems. Clock was adjusted back to default using CMOS reset. Other machines using Fedora 22 also worked fine.

J
JewishJustin
Member
95
01-30-2016, 08:03 AM
#12
It seems the system was originally set to default before the reset. You're asking about the base clock, not the multiplier. I need to clarify how it functions now and whether it's crashing. Build 10240 indicates it's not a new Win10 release but rather an update. Are you part of the insider program? Could you get a fresh installation of Windows or Linux? Have you tried transferring files to a standard USB drive?
J
JewishJustin
01-30-2016, 08:03 AM #12

It seems the system was originally set to default before the reset. You're asking about the base clock, not the multiplier. I need to clarify how it functions now and whether it's crashing. Build 10240 indicates it's not a new Win10 release but rather an update. Are you part of the insider program? Could you get a fresh installation of Windows or Linux? Have you tried transferring files to a standard USB drive?

Q
Quartzenstein
Junior Member
10
02-06-2016, 10:54 AM
#13
I haven't encountered a crash yet, so it seems the issue might be connected to my overclocking. The phone stopped midway during writing—possibly due to an SD card failure—but unplugging it removed the blue screen I was expecting. This suggests the blue screen could have been caused by the overclock. I also think the base clock remained at its default setting, and I only adjusted the multiplier, which might explain the BSoDs.
Q
Quartzenstein
02-06-2016, 10:54 AM #13

I haven't encountered a crash yet, so it seems the issue might be connected to my overclocking. The phone stopped midway during writing—possibly due to an SD card failure—but unplugging it removed the blue screen I was expecting. This suggests the blue screen could have been caused by the overclock. I also think the base clock remained at its default setting, and I only adjusted the multiplier, which might explain the BSoDs.

Y
YouAreL
Junior Member
1
02-07-2016, 06:24 PM
#14
It seems unusual how the multiplier doesn't clarify things for you. However, I'm happy to help. If you had a different approach, copying everything to your desktop and swapping the SD card quickly would be a good solution.
Y
YouAreL
02-07-2016, 06:24 PM #14

It seems unusual how the multiplier doesn't clarify things for you. However, I'm happy to help. If you had a different approach, copying everything to your desktop and swapping the SD card quickly would be a good solution.

Pages (2): Previous 1 2