Jamarlie

Thanks lol, way too much work for my smooth brain

For some reason it didn't embed it when I did that. I enabled embedding as well, no clue why it's not working lol Edit: Wait I think I know why, is it because it is shorts? lmao great job YT

I had to do this Linus after the paint rant, I'm sorry

So a quick update for the people that find this issue on Google in the future since they have trouble with the same thing: The problem reappeared in different flavors and today I about finally had it with this stupid issue and diagnosed it in depth. Basically the problem of my BIOS not even getting past the BIOS splash screen had nothing to do with either my motherboard OR my USBs. My MoBo flashed an LED on post that has the label "BOOT_DEVICE_LED". So it was having trouble with boot devices. The issue correlated pretty well timing wise to me installing Manjaro and switching to GRUB to dual boot Windows. Around that time I also got the USBs which made it seem like it was their fault. It sometimes did post, sometimes it didn't, sometimes no USB was present and it wasn't posting, sometimes it was. In the end the issue is entirely on GRUB or Linux. For some reason either of the two decided to add about 20 "bootable drives" called "UEFI OS" to my list of installed drives (Side note: Before I had Legacy windows and UEFI Manjaro which made GRUB unusable, I used to go into the BIOS to switch between the two and that's when I first saw the massive amounts of "ghost drives" that were supposedly connected - I had GRUB installed at that time however since I wasn't aware dual booting wasn't possible with Legacy and UEFI, they both need to be the same so I later converted Windows to UEFI). I just kinda ignored these "ghost drives" since I thought it wasn't really doing much but something about this seems to really make my MoBo struggling. It's probably trying to add the USB to the connected devices but since there's like 20 of those already maybe the BIOS gets overloaded so it doesn't post or even let me into the BIOS settings then? No clue what the technical details are, just a hunch. In the end I restarted the computer without the drive on which Manjaro and GRUB are installed. Then I shut it down after post, put the drive back in and when I post now I only have one "UEFI OS" entry left. I tried to plug all of the USB ports I have on my board and it worked just fine. I hope this permanently fixed my issue. PCs can sometimes really be detective work and I have no fucking clue what about unplugging and replugging the drive did the trick for my BIOS but here is to this hopefully being resolved permanently.

I know an ISO is not bootcode which is why I said "iso installed on a drive" which would make it bootable. They can be hidden all they want, I didn't check the stick with Windows but with Linux and if there's anything on there it'd tell me. Now I think I might have fixed the issue? I went into the drive and just deleted the "System Volume Information" folder, for some reason that magically made the PC boot again? I'm kinda lost for an explanation on that one, but I wouldn't be surprised if Windows was the thing bricking it.

Nope, just with this one USB. I'll use initdisk to see if there's any bootcode but over all this shouldn't really prevent the BIOS itself from booting, should it? And I also never had any .iso or anything installed on the drive that could remotely be a "boot code". It's also not like the flash drive is dead, it's brand new and if I plug it in once the system is posted it works just fine.

So I have a rather old ASUS Sabertooth Mark S MoBo, and I have a USB plugged in which I use as a quick and dirty way to transfer files between my systems (I dual boot Manjaro and Win10). Now this USB has mostly some text files on it, no .iso or executable files, but it makes my motherboard act... weirdly. Whenever it is plugged in, it gets stuck on the boot screen. And I don't mean it's trying to boot the USB which gives you a black screen and a cursor because it has no bootable OS on it, I mean it boots up, shows you the splash screen of the BIOS and then freezes in said post screen. You can't access the BIOS menu anymore like it says on screen which is how I know it is frozen, it just stays like this until you power it off. I've successfully identified the USB as the culprit, no matter where I plug it in it doesn't move past the splash screen on startup. If I unplug it, I can boot into GRUB just fine. What could be a way to fix that? I'm pretty well versed with tech and I have absolutely no bloody idea what that is, never even heard or read of that anywhere. Like if it would just try to post the USB I could at least tell it not to in the BIOS boot options, but if the BIOS itself doesn't work anymore with it plugged in, like whaddaya do then?? Thankful for any help!

So, I investigated and found the issue, it was not my SSD, but not my CPU either. So for future reference here is what I did: I went to the event logger to check the system error, DPC_Watchdog_Violation. I downloaded the WinDbg App and opened the minidump of the latest BSOD in C:/Windows/Minidump/ I analyzed the dump using the tool and found that the reason my PC crashed was "FAILURE_BUCKET_ID: 0x133_DPC_gwdrv!unknown_function" gwdrv.sys as a driver had failed. gwdrv.sys is the Glasswire driver. Come to think of it my crashes started right around the time I got Glasswire again, so THAT was the cause of these random BSODs. I uninstalled it obviously. If anyone has the same problem go check on those dump files.

And I just got yet another bluescreen, again a DPC Watchdog Violation. Starting to lose it a bit here. This time my CPU was at a constant 15% usage which I know, because I had the resource monitor open

Well the BSODs happened when I was playing games, other than that Chrome is hogging about 20% of the CPU and it still stutters there. I wasn't really thinking about the CPU at all tbh since I've always heard about how long you can use CPUs before they die. New CPU would be kind of the worst case scenario since that means new Motherboard + RAM which has me looking at at least 700 bucks. The SSD was also my focus since I read online that the Watchdog Violation and stutters sometimes come from the drive and the OS? So that was why I was assuming that, along with the weird file loading issue I had and the high temp spike I saw. Edit: Idk how useful this is but I used CPU-Z to bench my CPU and it tells me my Single Thread rating is 97.6% of what the CPU should be at and my Multi Thread is hovering around 94.4% of what the average benchmark says.

Yo, so about a month ago my PC started having his first small stutters. The mouse would freeze for a split second or video would freeze up while watching Netflix every now and again. I wasn't really all too worried until the BSODs started coming, 3 in a month, error code always was "DPC Watchdog Violation". I did a couple things already like checking my RAM, diagnosis tool says no errors. I ran chkdsk, fixed a few errors, stuttering was still there. I checked temps, under full load it's 55°C non OC (specs are listed below), Crystaldisk reports no errors, however it did show me in one instance that my SSD was 50°C hot, that was pretty unusual considering my HDDs are around 20°C less than that right below it. I updated all the drivers for my GPU and around the PC, nothing. I then went on and completely reinstalled Windows, and it did get a little better but it still persists. I have stretches like the last 3 hours with now spikes, but when I booted it up earlier today I had a spike every other minute. I was now starting to narrow the problem down a bit and think (and still hope lol) it's just the SSD. Samsung's SSD Magician doesn't seem to help all too much, my SSD according to that thing is fine? That is despite the fact the SSD had some weird issues a few weeks back where I opened a folder and it would take about 10 seconds to display its contents one by one. I presume it's gotta do something with it. Considering it was never running above 50% capacity and it wasn't a cache or something handling massive amounts of data, it can't be the flash memory on it. The flash memory itself has only 20TB written to it out of 100TB it's rated for, but it's about 4 years old at this point. So my working theory now is that my SSD controller might just be dying atm. My system was built around mid 2016, except for the GPU which is like 3 years old? Here are the specs i7 4790K @ 4.00Ghz cooled by custom water loop 16GB HyperX Fury RAM Asus Sabertooth MARK S Z97 Mainboard EVGA GTX 1070 FTW be quiet Pure Power 9 600W PSU Boot OS is Windows 10 Pro on a Samsung 750 EVO So I ordered a new SSD now, but still I'm unsure if I'm in the right with my diagnosis? Which is where you guys come in. Maybe, just as a sanity check, do you guys think it's the SSD as well or is it maybe something I haven't thought of yet? Thanks for the answers and reading through all of this in the first place!

Okay, maybe a quick update, I seem to have found the problem. I believe my SSD is fine, the issue has probably something to do with my keyboard. Now I was also able to reproduce how. To "force" this error I can just hold down the power button on my PC which will make it turn off, turning it on again after that basically caused the weird pointer to flash again and not boot. That's when I noticed my keyboard was faintly flashing when I did this, I presume it gets barely enough power from the USBs to vaguely kind of half turn on? It's a Steelseries M800 meaning it's basically it's own computer. It usually requires two USBs to be connected for power delivery as well. Now my theory was that the faint flicker of the keyboard probably draws just enough current to make my PC think there is a USB connected as a boot drive. Meaning my PC (most likely) effectively tried to boot from my keyboard, giving me this blinking thing. Disconnecting the keyboard and trying again resulted in everything booting up just fine. More testing might be required but I think I found the culprit. I have absolutely no clue what causes this but if you happen to find this thread and have a similar problem: It was the keyboard in my case. That explains why turning off the power helps to not feed the CPU in the keyboard more electricity and therefore the PC booting up correctly.

Alright, thanks for your help.

But that would be weird. I've had that problem ever since I first built my PC. Needless to say that Crystaldisk doesn't show me any signs of trouble (although I do know that SMART doesn't necessarily mean anything):

Maybe one of you tech savys can help me with my problem here: I boot Windows 10 off of a regular 750 Evo SSD. Now sometimes when I go to start up my system instead of booting up Windows I just see a black screen and small blinking dash at the top right corner. Then nothing is happening. Usually that dash would wander down and Windows would boot up, dunno why it does that. Shutting the computer off and back on usually fixes the issue. I always thought "Hm, maybe my PC boots of any USB device for some reason and just gets confused, heck do I know" and went on my way. After all that only happens like 1/20 boots or so and has always sorta been there as a boot "issue" ever since I built my PC. Today it happened three times in a row though, which understandably made me freak out a bit. I am now certain that doesn't originate from any other device as I went into the BIOS and specifically told my PC to boot the SSD, still the same problem. It was only after shutting off the power and trying again that it booted just fine. What the hell is this sorcery and how do I prevent it? Is it bad? Is it "just a Windows thing"? In case you need specs or anything: i7 4790K, GTX 1070, Sabertooth Mark S MoBo, 256GB 750 EVO SSD (I only use it for booting, it literally is about 2/3rds empty), 2 other Harddrives for everything else, Windows 10 Professional. Built the system in mid 2016 so I highly doubt something is extremely broken that causes this. My SSD has 12TB of writecycles on it, and about 9500 hours of runtime. Crystaldisk says it's at 100% health. Thanks in advance!