Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Tannah

Member
  • Content Count

    43
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About Tannah

  • Title
    Member

Profile Information

  • Location
    Canada BC
  • Gender
    Male
  • Interests
    Technology, Computers, Electronics
  • Occupation
    IT Technician IV

System

  • CPU
    Ryzen 7 2700x
  • Motherboard
    Asus ROG Crosshair VII Hero
  • RAM
    32 GB 3200 DDR4
  • GPU
    MSI 2070 Duke
  • Case
    Define R6
  • Storage
    Samsung M.2 970 EVO
    Samsung SSD 860 EVO
  • PSU
    RM 1000i
  • Cooling
    NH-D15-SE-AM4
  • Keyboard
    G910
  • Mouse
    G502
  • Sound
    Creative X-Fi Titanium HD
  • Operating System
    Windows 10 Pro custom

Recent Profile Visitors

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

  1. So I have learned that apparently on the Crosshair VII Hero Bios 4204 with the Matisse 3000 series, there is a CPU Overtempmax temp trip that is set too low. By 20c+ has been reported so far. This apparently this will cause a emergency shutdown. The only way to get around this (so far) is to set CPU Temp Monitoring to Ignore. Which seems like a bad idea.
  2. Hello ShrimpBrime, Thank you for replying. The interesting thing is this Bios 4204 is suppose to fully support the Matisse on the Crosshair VII Hero, and it does have a couple fixes for the Crosshair VII Hero running Matisse CPU's. The one notable one for me is it fixed the random cpu spikes that caused the fans to rev, this was a known problem with 3103. There are a few other minor fixes too. I've noted them all while running 4204. So just because the mainstay of Bios 4204 support is for Vermeer, doesn't mean Matisse on the Crosshair VII Hero isn't getting any tweaks b
  3. If its still working and not bulged, leave it alone. If your worried you can get a voltage tester, and test the voltage its putting out. I think it should be 3.3v DC
  4. A bit ago I tried upgrading the Bios on this Crosshair VII Hero WiFi from Bios 3103 to 4007 using the USB Flashback functionality, running Windows 10 pro 20H2. I noticed a few oddities, the biggest one was the computer intermittently hard rebooting. I looked though the settings tinkered with a few voltages and removing C-states, clearing the settings, loading optimized defaults. But it kept Randomly rebooting? I could not find any real rhyme or reason. I figured just a buggy Bios so I rolled back to 3103, and the computer went back to running fine. So the other day I thought I would up
  5. Not sure exactly which form this belongs in. I picked up a Google Chromecast with Google TV. I previously used a Amazon Firestick HD on my personal TV (no cable). I have found the Chromecast w/ Google TV is an all around better experience to work with. I found it much more usable than the HD Firestick, to be honest the HD Firestick feels neutered in comparison. Its not that the HD Firestick is bad, far from it, but the Chromecast w/ Google TV so far is just that much nicer to work with. Especially with the the Apps only option that take away all the clutter and much of the sup
  6. That's a bit of a tough one without some more information. The first thing I suggest doing is turn on verbose mode for shutdown and startup https://www.techrepublic.com/article/how-to-turn-on-verbose-booting-mode-in-windows-10-with-a-registry-edit/ This might give you a idea of where its hanging up. The other thing to look at is your Event Viewer: Right click on your start menu and select Event Viewer, expand Custom Views, and Click on Administrative Events. and look at the time where you were shutting down, Be aware there is normally a ton of warnings and err
  7. First computers x86 used DOS 2.1, 4.01, 5.0, 6.1, 6.2, 6.22. Looked at Windows 1.0 went back to DOS. Windows 3.1, Windows 3.11, Then Windows 95, 95 OSR1, 95 OSR2, 95 OSR 2.5. Windows98, 98se, Me, Windows XP, Vista x64, 7 x64, 8 x64, 8.1 x64, 10 x64. Windows NT 3.51, 4.0, 2000, 2003, 2008, 2008R2.
  8. Hi Vonavi, I've found pretty much the same thing. It appears somebody messed up when creating the original 20H2 ISO. I have not tried to tackle the virtual machines yet. So its nice to know that the problems are even worse there. I've been working on the 20H2 Image to create a new deployment. Unfortunately some of my users are the type that just know enough to cause a headache. So I would be inundated with questions regarding these hidden device drivers. Let alone the potential issues these could create in the Labs. Just not worth the trouble. But I have a few dev's buggi
  9. Um? Your Trolling right? Because it sure sound like you are.... Just on the off chance you are not: Fresh Install = Removal of all partitions from system drive, format, and install of a Operating System ISO (In this Case Windows 10) Imaging a System or re-imaging = removing all partitions from the system drive, installing a Pre-configured ISO of Windows 10 That is scripted to format the drive. This ISO is meant for quick deployment for a corporate or educational environment. Blow and Load = Removal of all partitions on boot drive, Format of drive and install from a O
  10. Ok I did a fresh reinstalled 20H2, I did some screenshots of device manager. 3 screen shots showing the additional stuff. Keep in mind the additional stuff does not show up in windows 10 2004. No Updates other than what comes with windows 20H2, only the drivers that come with 20H2.
  11. Clean Install of Windows 10 Pro 20H2 X64, Looking over Device Manager to check which driver need to be installed, Toggle Show Hidden Devices, and notice something weird, (Note this is a AMD System no intel parts at all), but for some reason under CPU its showing two entries for an Intel(R) Xeon(R) CPU E5-2673 V4 @ 2.30GHZ along side my my 8 core AMD CPU? Look around Some more and notice 2 floppy disk controllers (this computer does not have a floppy drive controller) Then Notice Hyper-V devices installed all over the place? Open up Programs and Features and Toggle Turn Windows Features on
  12. Easy to say, but a bit harder to do, especially when they apply can apply online updates before group policys takes effect.
  13. I really wish Microsoft would properly test their updates and not make the end users the beta testers. Makes me glad I postpone updates for a few days with Windows 10 pro. I was running into BSOD on fresh windows 10 installs, while having the computer plugged into the internet. As the update was being pushed on initial look for updates. This appeared to take place before the Group Policy's were pushed to the computer. To get around the issue swapped to using a USB stick to install, rather than network boot. While disconnecting from the net while installing windows 10. Its i
  14. At a guess: Its possibly the boost clock, Or depending in your motherboard vendor PBO. There have been reports on various forums of non X series Ryzen 2000 CPU's exhibiting this behaviour. Did you select load defaults after updating your BIOS? If your OS supports it I would try Ryzen Master to see if it reports the same Boost. Also try HWiNFO as well. Just to rule out it being a software error.
×