QuestioningGuy
-
Posts
90 -
Joined
-
Last visited
Recent Profile Visitors
687 profile views
QuestioningGuy's Achievements
-
nvm, it was a card, cable, monitor issue -
It all started when I was flashing my x79 Sabertooth bios with a user modified one that has nvme boot support. After flashing all was going well, I reconfigured all the settings in the bios (overclocks, boot orders, etc.), ran some stress tests without problems. Then I went into the bios again, disabled onboard audio (it doesn't work, i use a PCI soundcard, but I was hoping maybe the bios update will bring it back to life, it didn't), and I enabled some kind of usb 3.0 charge support. These were the last and only settings that I have changed, and after saving and rebooting, there was no video output at all. I have tried different slots, different gpus, resetting cmos, re-flashing the old and official bioses, nothing worked. The system seems to be working fine, only no video output. Judging by the onboard LED and shut off time after pressing the power button, the pc boots into windows, i can configure bios settings (obviously without seeing anything), I even managed to load optimized defaults, that didn't work. I'm thankful for any help I can get
-
Is my current system worth upgrading?
QuestioningGuy replied to HotRunes's topic in New Builds and Planning
Honestly, at 1080p your system will probably deal with even the newest games without problems at high-ultra -
The hard drive has no bad sectors, I've checked it about 3 times, formatted it at least 7 times in different ways. The system doesn't crash when installing games, even 2 or 3 at the same time, but as i try to start playing them, it's only a matter of time before it crashes (most consistent crashes are with assetto corsa, crashes as soon as it loads the track, though there wasn't a game that ran without crashing at least once). I have an Asus p6t deluxe v2 x58 motherboard, overclocked, but everything fully stable. I previously had 2x750Gb seagate drives in raid 0, only recently changed them to a 2tb seagate drive. That's when the problems started Any suggestions are welcome, I'm really desperate at this point. P.S. The last event in event viewer, system logs before crashing is id 98 (uploaded a picture of how it looks).
-
Graphic Artifacting at different IRL Locations
QuestioningGuy replied to Memezaa's topic in Troubleshooting
The first thing that came to my mind is that you have "dirty power" at your place. Can't think of anything else that could cause this issue. -
I've recently replaced my raid 0 setup of 2 seagate hard drives to one 2 tb seagate drive. I've also changed the setting in the bios from RAID to AHCI, following a guide how to do it without reinstalling windows. In windows logs, I've narrowed down a problem to be linked with event id 98 happening, which is some kind of a storage checking thing of Microsoft. It first checks my ssd, marked as drive C:, says that there are no problems, then it checks my hard drive, which is marked as D:, but shows up as a bunch of gibberish (" \\?\Volume{a98d1568-0000-0000-0000-100000000000} "). After it completes the check, it says that there are no problems, and the system freezes fully. It only happens when I'm putting load on the hard drive, mainly gaming. I have a x58 system, with all the software up to date. The S.M.A.R.T. says the hard drive is fine.
-
The phone is currently in download mode, the Samsung logo also shows up when the phone is turned on, with a non factory OS warning/error. It boot-loops if i don't enter download mode, which is pretty much the only thing I can do in it's current state. And Samsung recovery software on PC doesn't detect this phone as an actual Samsung phone, so it doesn't work as well.
-
Mine's SM-A105FN, and i have tried their ROM. Same problem
-
After doing some research (after, of course, flashing) i have nearly come to the same conclusion.
-
There are no official ROM downloads on their website, but i have tried some unofficial "stock" ROMs. Flashing those shows the same error
-
I used odin on my Samsung Galaxy A10, to flash twrp. I followed the guide, and ticked EVERY box from the options list (including nand erase and re-partition). Currently, the phone rejects all flash attempts I've tried (check fail device 2 binary 1 is the error I get) Is there anything I can do to recover it, or is it just an expensive-ish paperweight?
-
I bought some still in packaging ram (kingston hyperx predator ddr3 1866mhz 2x4gb (hx318c9pb3k2/8)). It doesn't seem to detect two particular sticks out of 6 that i bought. But it does detect all 24gb of it in cpu-z and aida 64, not in windows or the bios. Is the ram faulty, or am I missing something here? P.S I did test all of the sticks one by one, and two of them seem to be malfunctioning. I did test triple channel with some mismatch ram and the 4 functioning ones, and it did work, detected all 24gb in the bios P.S.S Asus p6t deluxe v2 with a Xeon x5675, not much else matters i suppose
-
Previously, my overclock failed, killed my cpu (i5-750, currently using an i5-660) and "injured" the motherboard (Gigabyte P55-UD3). The motherboard refused to stay on for more than 10 seconds, but with recovered bios (old, F3) it works fine. I tried updating a few times, but it doesnt help. Then i have to recover it again, for the motherboard to be usable. Is there any way I can make it work with any newer bios? (The reason for updating, is that with old bios, overclocking is very limited. There is no clue of xmp, and my cpu multiplier is not adjustable, and set at i5(?)).
-
Previously, my overclock failed, killed my cpu (i5-750, currently using an i5-660) and "injured" the motherboard (Gigabyte P55-UD3). The motherboard refused to stay on for more than 10 seconds, but with recovered bios (old, F3) it works fine. I tried updating a few times, but it doesnt help. Then i have to recover it again, for the motherboard to be usable. Is there any way I can make it work with any newer bios?
-
If it was working before you disassembled it, id check for dust on the connections. I personally had problems with dust in my ram slots, that prevented my system from booting. If there is no dust, I'd try doing a minimal boot, or even taking the motherboard out of the case, in case (no pun intended) something was shorting it. If nothing helps, just replace the graphics card with the one from your personal build, to see if the system works
