Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About maestripieritimo

  • Rank

Recent Profile Visitors

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

  1. never used it, probably never will
  2. 48GB = 24GB to win 10 VM + 8GB arch VM + 16GB unraid and dockers.
  3. Since the devs didn't do it yet i guess its not coming, but i'd still like to see this feature. so a pretty please with a cherry on top for keyboard settings
  4. nevermind, stupid me forgot to edit the rom before the dump, everything is working fine now. sorry any the inconvenience
  5. Hi Squid and others, Thank you for the great video. I followed your guide to the T and it worked fine for my secondary GPU, but because i wanted to make some room for a nic i tried doing this with my primary GPU and i ran into the dreaded code 43, even though i inputted the bios i pulled from my own card and set hyper-v to no, i booted unraid in legacy and uefi, all to no prevail. Have you noticed this behavior on your system(s)? What should i do to fix this? Thanks in advance
  6. OK thank you, hope i can catch one between it happening and system freezing. It has been running for 28h error free, i've been messing around in the bios a bit and hope it runs smoothly now.
  7. So i uploaded my hardware info from were was said and i added the diagnostics. i'm using 6.5.2 still in trial. its a asrock x99 taichi with a i7 6800k and 48GB of ram. I'm sorry for my earlier reaction and do appreciate the help, i just thought someone might know what up with just the error i posted earlier. timo-nas-diagnostics-20180603-0029.zip
  8. I just checked, the hamster providing power died, need a new one. If you like info on the system from a newby you'll get more by giving exact location for that info instead of belittling them, i can't find a file named system event log. so i dont know what to give you. Allthough actual help is still appreciated.
  9. I get this error in my syslog, anybody any idea what this means? Jun 1 06:17:50 TIMO-NAS kernel: smpboot: CPU0: Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz (family: 0x6, model: 0x4f, stepping: 0x1) Jun 1 06:17:50 TIMO-NAS kernel: mce: [Hardware Error]: Machine check events logged Jun 1 06:17:50 TIMO-NAS kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 19: be200000000b110a Jun 1 06:17:50 TIMO-NAS kernel: mce: [Hardware Error]: TSC 0 ADDR c647b1080 MISC 84fe2050801a4086 Jun 1 06:17:50 TIMO-NAS kernel: mce: [Hardware Error]: PROCESSOR 0:406f1 TIME 1527826657 SOCKET 0 APIC 0 microcode b00002c Jun 1 06:17:50 TIMO-NAS kernel: Performance Events: PEBS fmt2+, Broadwell events, 16-deep LBR, full-width counters, Intel PMU driver. I started logging with "fix common problems" plugin set on trouble shooting because system kept locking up me out after a while resulting in a hard reboot. so is this the cause? is my cpu busted? Thanks in advance, Timo