Jump to content

Commander_Z

Member
  • Posts

    1,420
  • Joined

  • Last visited

Awards

This user doesn't have any awards

5 Followers

About Commander_Z

  • Birthday Oct 03, 1989

Contact Methods

  • Steam
    trachezoid
  • Origin
    merchenko
  • Twitter
    https://twitter.com/NickHeath

Profile Information

  • Gender
    Male
  • Location
    New Zealand
  • Interests
    Gaming
    Reading
    Music

System

  • CPU
    AMD Ryzen 7 3700X
  • Motherboard
    Asus X570-E Gaming Wifi
  • RAM
    4x8GB Corsair Dominator Platniums 3200Mhz
  • GPU
    EVGA RTX 3070 XC3 Ultra
  • Case
    Corsair Air 540
  • Storage
    1TB NVME drive (main), WD 2TB Green(secondary), Samung 500gb SSD, Samung 1TB SSD
  • PSU
    Antec HCP 1000W Platnium
  • Display(s)
    Corsair Xeneon 32QHD165 1440p Gaming monitor and 1x Samsung LS24C300HL 24 inch monitor and 1x HP V270 27 inch monitor (portrait)
  • Cooling
    Corsair 240mm AIO
  • Keyboard
    Corsair K70RGB
  • Mouse
    Logitec G500S
  • Sound
    Sony MHC-GT22 stereo as speakers
  • Operating System
    Windows 10
  • Phone
    Pixel 4 XL
  • Other
    Samsung Galaxy Tab S9 Ultra

Recent Profile Visitors

2,337 profile views
  1. So after being on all day, it's just 'locked up, so i had to restart to get things going again. My happiness/hope that this was fixed has been dashed. The floor is open to solutions again
  2. The car vbios version is 86.04.50.00.63. according to this website, that is the latest version? https://www.techpowerup.com/vgabios/?did=10DE-1B81-1043-8599
  3. I hadn't planned to. I've had enough stress updating bios/firmwares etc for one night. maybe later.. If i knew how to, i may consider it
  4. Hopefully, by fixing this issue, i have resolved the other. If i could give you an internet award, I would. Have a great day/weekend where ever you are. And have a drink on me, if that's your thing Cheers.
  5. Edit: a CPU fan error appeared, but I fixed this. Can now get into windows. Will reconnect other monitors. Thank you so much for your help. I was in full panic mode for a while there. Your help really means a lot to me, so thanks again.
  6. So potentially a good piece of news. I disconnected two of my monitors ( one that connects via display port, the other via HDMI) I can get into the bios on the third monitor (connected via HDMI) The code showing is A9 now. I can also see the is now the latest version. Next step, reset bios to default settings??
  7. So that didn't work. I also held the power button down to turn it off. Turning it back on, it is now showing 02 code. Also, the VGA light on the mobo is solid white and the boot light is yellow.
  8. Yep, it cycled through a few codes before being on code 64. To be clear, I can just press the restart button to see if that works first?
  9. I plugged the USB with the latest bios into the port labelled BIOS. Then went into the bios a ran the update tool. After a couple of minutes the progress bar was completed
  10. So I've gone ahead and installed the bios update via the drive. The code led has changed a few times, but for the last 10 minutes it's been stuck on code 64. Before that, it was on 02 (I think) for a few minutes before changing to code 64. Am I to leave this to sort its checks out, or can I remove the USB/press the restart button? No login page showing on the screen.
  11. Just installed the latest chipset drivers. Will sort the bios. got the drive ready to go.
  12. Hi, I've just run the uninstall tool, appears to have removed a few files etc. As to the BIOS, i am running version 1407, but according to the Asus website, the latest is version 4403. I'm a bit nervous to update the BIOS but i suppose it's worth doing in this case? As to the chipset drivers, i haven't updated those since i built the PC a couple years ago.
  13. Hi everyone, I’ve been running into this somewhat infrequent issue with my PC where it ‘soft locks’ essentially, and the only way to get the PC running fine is to hit the restart button. I hope you are able to suggest some things I can try to resolve this, so TIA. (Apologies for the long post ahead). System specs: CPU: AMD Ryzen 7 3700X Mobo: Asus X570 - E Gaming Ram: 32GB Corsair Vengence RBG Pro (4x8GB) GPU: Strix 1070 with the latest drivers M.2 boot drive Several additional SSD's for games etc Corsair AIO Corsair LL RBG fans Corsair Commander Pro The following is how I think the issue started, but open to other suggestions etc. A few months ago, I upgraded from GPU Tweak 2 to GPU Tweak 3. At the same time, I (foolishly) installed Armoury Crate, which is when the issues began to appear. Seemingly, at random, my PC would appear to soft lock. Visually, the pattern on my RGB fans would go back to the default colours that you see when it boots up (before getting into windows to load the pattern i selected). the taskbar clock would stop, but I would still be able to close windows/close out of steam etc, but i would not be able to shut the PC down via the start menu. The only way to get this running again (for weeks at a time too) is to click the reset button on my case. I went through uninstalling the software via the normal method which didn't seem to work (in terms of solving the issue). I also used the portable version of the Revo uninstaller to properly remove it, which 'has worked' compared to the first method. I've noticed also that the RGB on the ram works randomly, as in it either doesnt lit up or it gets stuck on partial colours. In Corsair iCUE, it tells me sometimes that "iCUE has stopped recieving data from DRAM. Please restart or power cycle your system to fix this problem". I have reinstalled iCUE several times, so im not sure it's the software that is causing the issue I have seen and watched several videos about the armoury crate software causing the issue i have run into, but this continues to be an occassional frustration. The only other thing i can say is that (i think) the armoury crate software installed a folder called PHISON which has a folder called Aac_PHISON HAL. i tried to delete the folder but i couldnt, but i was able to delete a file called Phison_x86.dll. A file called Phison_x64.dll is not able to be deleted. I'm not so sure about the PHISON folder, as the dll mentioned above has a modified date of 25/06/2021. Has me deleting the x86 version caused an issue? I'm open to all suggestions and am happy to provide additional info, should you need it. Thank you.
×