F5F Stay Refreshed Hardware Desktop I'm here to assist you with whatever you're facing. Please share more details so I can help effectively.

I'm here to assist you with whatever you're facing. Please share more details so I can help effectively.

I'm here to assist you with whatever you're facing. Please share more details so I can help effectively.

Pages (2): 1 2 Next
S
Sk8ter10
Junior Member
31
08-11-2024, 08:06 AM
#1
Performed several driver swaps on my main system to try different GPUs. Removed them using DDU and always in Safe mode. After reinstalling the latest drivers, GeForce Experience didn’t work. I can’t access Safe Mode or Windows normally. The PC won’t boot from USB with the correct ISO, showing a black screen with white text. This seems outside my expertise—any suggestions?
S
Sk8ter10
08-11-2024, 08:06 AM #1

Performed several driver swaps on my main system to try different GPUs. Removed them using DDU and always in Safe mode. After reinstalling the latest drivers, GeForce Experience didn’t work. I can’t access Safe Mode or Windows normally. The PC won’t boot from USB with the correct ISO, showing a black screen with white text. This seems outside my expertise—any suggestions?

F
Fluffycakes123
Senior Member
696
08-11-2024, 08:26 AM
#2
Specs?
F
Fluffycakes123
08-11-2024, 08:26 AM #2

Specs?

R
Reborn01
Member
59
08-11-2024, 10:45 AM
#3
You can try using a different OS installation method. Simply remove GeForce Experience from the setup. Any standard operating system should work. Just ensure the program isn’t running during the process. I keep a Linux Live CD key handy for this. If you don’t have access to external media, consider a clean install after DDU removes the unwanted components. This step helps avoid frequent reinstalls. Make sure to back up important data beforehand. A clean install involves wiping the entire disk and reinstalling everything. You’ll also need a Windows installation key for that process. Getting one is essential as it ensures a proper reinstall.
R
Reborn01
08-11-2024, 10:45 AM #3

You can try using a different OS installation method. Simply remove GeForce Experience from the setup. Any standard operating system should work. Just ensure the program isn’t running during the process. I keep a Linux Live CD key handy for this. If you don’t have access to external media, consider a clean install after DDU removes the unwanted components. This step helps avoid frequent reinstalls. Make sure to back up important data beforehand. A clean install involves wiping the entire disk and reinstalling everything. You’ll also need a Windows installation key for that process. Getting one is essential as it ensures a proper reinstall.

C
chrisnoble
Member
103
08-11-2024, 04:41 PM
#4
Include this info on your page, but I7 8700 GTX 1080 32 GB 3000 CL15 Z390 Aorus Elite 970 Evo Plus Random HDD random 16 gig USB drive.
C
chrisnoble
08-11-2024, 04:41 PM #4

Include this info on your page, but I7 8700 GTX 1080 32 GB 3000 CL15 Z390 Aorus Elite 970 Evo Plus Random HDD random 16 gig USB drive.

B
Bubzkittys
Member
50
08-12-2024, 12:11 AM
#5
It makes sense, I’m still getting the hang of this. Honestly, I’m not familiar with these concepts, so I don’t understand why I can’t access safe mode or boot from my USB drive. It’s really confusing.
B
Bubzkittys
08-12-2024, 12:11 AM #5

It makes sense, I’m still getting the hang of this. Honestly, I’m not familiar with these concepts, so I don’t understand why I can’t access safe mode or boot from my USB drive. It’s really confusing.

S
Shad0wHydra13
Senior Member
716
08-12-2024, 01:29 AM
#6
You might need to adjust the BIOS settings and ensure the USB drive is listed first in the boot sequence. This process can vary depending on the manufacturer’s instructions. The BIOS itself is quite basic, stored in flash memory or ROM chips, and it mainly serves to check hardware and start the system. Once the machine successfully boots, the actual operating system loads. The UFEI or BIOS acts like a bridge, making sure compatibility regardless of the hardware maker. It handles simple tasks like fan speed settings. After the initial setup, the OS takes over. Getting the boot order correct is essential for a smooth experience. Typically, you press a specific key right after powering on—often the delete key or F8 on HP boards. Various manufacturers offer their own setup utilities, such as those from Phoenix or AmericanMegatrends. Since procedures differ by model, I can’t give a universal method. Your manual should provide clear guidance for your particular board.
S
Shad0wHydra13
08-12-2024, 01:29 AM #6

You might need to adjust the BIOS settings and ensure the USB drive is listed first in the boot sequence. This process can vary depending on the manufacturer’s instructions. The BIOS itself is quite basic, stored in flash memory or ROM chips, and it mainly serves to check hardware and start the system. Once the machine successfully boots, the actual operating system loads. The UFEI or BIOS acts like a bridge, making sure compatibility regardless of the hardware maker. It handles simple tasks like fan speed settings. After the initial setup, the OS takes over. Getting the boot order correct is essential for a smooth experience. Typically, you press a specific key right after powering on—often the delete key or F8 on HP boards. Various manufacturers offer their own setup utilities, such as those from Phoenix or AmericanMegatrends. Since procedures differ by model, I can’t give a universal method. Your manual should provide clear guidance for your particular board.

G
goatpig
Member
55
08-12-2024, 08:09 PM
#7
Clear understanding, appreciated. The boot sequence issue remains unresolved even after changing the order. From the USB, it displays a black screen with a white blinking dash for extended periods. I'm now attempting to run it on a custom-built machine for this RQ and install there, then transferring it to the primary system. Once there, I need to access the OS and resolve the existing problem.
G
goatpig
08-12-2024, 08:09 PM #7

Clear understanding, appreciated. The boot sequence issue remains unresolved even after changing the order. From the USB, it displays a black screen with a white blinking dash for extended periods. I'm now attempting to run it on a custom-built machine for this RQ and install there, then transferring it to the primary system. Once there, I need to access the OS and resolve the existing problem.

S
232
09-01-2024, 02:34 AM
#8
Ok. If that doesn’t work, try pulling the hard drive. The machine will post without a hard drive in it. If it still doesn’t work, something is likely messed up in the bios and it needs to be rewritten over. An indication of that is a post code of some sort. It can be a beep or series of beeps, a light on the motherboard, or a digital readout also on the motherboard. If none of those are activated At that point things get difficult unless your motherboard has some equivalent to bios flashback which allows the bios to be rewritten
S
SpakmenRus2012
09-01-2024, 02:34 AM #8

Ok. If that doesn’t work, try pulling the hard drive. The machine will post without a hard drive in it. If it still doesn’t work, something is likely messed up in the bios and it needs to be rewritten over. An indication of that is a post code of some sort. It can be a beep or series of beeps, a light on the motherboard, or a digital readout also on the motherboard. If none of those are activated At that point things get difficult unless your motherboard has some equivalent to bios flashback which allows the bios to be rewritten

A
AFKCosmos
Member
183
09-17-2024, 03:59 PM
#9
I successfully installed Windows on a separate drive and can reach all my files there, but I’m unable to boot from that second drive. The operating system appears intact, though I still can’t start from it.
A
AFKCosmos
09-17-2024, 03:59 PM #9

I successfully installed Windows on a separate drive and can reach all my files there, but I’m unable to boot from that second drive. The operating system appears intact, though I still can’t start from it.

L
levoyageur92
Posting Freak
807
09-17-2024, 11:21 PM
#10
Other storage device might be faulty. We can verify that. This isn’t always ideal but it’s fast. Near the windows icon on the lower left there will be either a magnifying glass symbol which you should click on, or a box. Inside the box, type “cmd” and press enter. This opens the terminal. It resembles a Linux command line and functions as a command interface, though its shell differs significantly from standard shells unless you use KORNshell or PowerShell in *nix. When the terminal appears (should be extremely quick), input “chkdsk”. You can also run it via the graphical interface, but I’m unsure. I’m an old fart. This will scan the drive for issues and attempt repairs. It’s likely there are none, so you’d then examine cables. Cables are prone to damage. Perhaps inspect them just in case. If problems persist but repairs fail (usually due to serious damage), you’d need to back up necessary files, then perform a low-level format followed by a clean install on the suspect drive. If the device still cannot be fixed, it likely points to a hardware issue. Edited May 7, 2022 by Bombastinator
L
levoyageur92
09-17-2024, 11:21 PM #10

Other storage device might be faulty. We can verify that. This isn’t always ideal but it’s fast. Near the windows icon on the lower left there will be either a magnifying glass symbol which you should click on, or a box. Inside the box, type “cmd” and press enter. This opens the terminal. It resembles a Linux command line and functions as a command interface, though its shell differs significantly from standard shells unless you use KORNshell or PowerShell in *nix. When the terminal appears (should be extremely quick), input “chkdsk”. You can also run it via the graphical interface, but I’m unsure. I’m an old fart. This will scan the drive for issues and attempt repairs. It’s likely there are none, so you’d then examine cables. Cables are prone to damage. Perhaps inspect them just in case. If problems persist but repairs fail (usually due to serious damage), you’d need to back up necessary files, then perform a low-level format followed by a clean install on the suspect drive. If the device still cannot be fixed, it likely points to a hardware issue. Edited May 7, 2022 by Bombastinator

Pages (2): 1 2 Next