Jump to content

Lavonthomon

Member
  • Posts

    16
  • Joined

  • Last visited

Awards

Profile Information

  • Gender
    Male
  • Location
    New Jersey
  • Biography
    "Thinking of you, wherever you are.
    We pray for our sorrows to end, and hope that our hearts will blend.
    Now I will step forward to realize this wish.
    And who knows:
    starting a new journey may not be so hard,
    or maybe it has already begun.
    There are many worlds, but they share the same sky —
    one sky, one destiny."
  • Occupation
    Student

System

  • CPU
    Ryzen 1700x
  • Motherboard
    Asrock Pro B350 ATX
  • RAM
    DDR4 Ram 16 GB 2800 MHz (Dual Channel + Overclocked)
  • GPU
    EVGA Black RTX 2080 Super
  • Storage
    256 GB Samsung 960 Evo (NVME) 1TB Seagate Hard Drive
  • PSU
    750W Corsair module
  • Display(s)
    Dual (144hz + 60 hz)

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Lavonthomon's Achievements

  1. Anyone else having problems sending work unit back to 140.163.4.241? I guess the server ran out of storage to receive complete work unit. Now I am stuck with project 11746 and it's unable to send.
  2. Only four days left? Time to shift gears
  3. I don't know if anyone has helped you with your issue already but to solve your issue you have delete your the corrupted WU then restart the client to get a new WU. This is the F@H directory: C:\Users\windows\AppData\Roaming\FAHClient\work
  4. Yeah, either there is still issues or no one wrote up the post. A little disappointing, I didn't know what to drink last night.
  5. You can try updating to a older version of the bios first If nothing is working that mean you have the wrong bios. When I was flashing my bios I downloaded the update for Asrock Pro b350m instead of the Asrock Pro b350, and motherboard refuse to accept the mATX update. What I am saying is that could have the right model but wrong size (ATX, mATX, ITX)
  6. Can't say that ever happened to me but it's probably just a driver for AMD Apus. See if you can skip it if you can't, just install it. Asrock is probably just trying to keep your system up to date.
  7. If you're having trouble getting into the bios you're probably on fast boot. If that's the case in the download tab of the product page Asrock has an UEFI restart tool that you can use.
  8. Same process, now you only have to flash once with update 5.9
  9. Perfect I have an Asrock B350 Pro (ATX) Follow this link https://www.asrock.com/mb/AMD/AB350M Pro4/index.us.asp#BIOS >Support tab > Bios Download Bios 5.8 and 6.4 then load the files on to a flash drive and reboot into the bios. (Asrock recommends flashing into 5.8 before flashing into a new bios.) Once in the bios go into the instant flash and you will see update from flash drive. Select the flash option then select the bios update. If you don't see the bios update that either means it's not on the flash drive or you downloaded the wrong update.
×