Solved Now I've gone and done it!!

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Status
Not open for further replies.
it ran a full test in REALLY BLOCKY letters Like COM 64 LOL I am so technical! Then it ran again, this time still in what I will call DOS but MUCH cleaner. It appears ti have run thru the entire set of tests, 4 times it was showing 1/4 and would complete 100% then go to another test like BLOCK test and run to 100% when it got to test 13 or maybe 18? It started over at 2/4 and did it all again. Both the extremely blocky and not so blocky 4 pass test came back with 100% no errors

So my answer is 5 times.
 
Rerun the MiniToolBox this time put a check into select all and Copy and Paste the info into the next post.

Is this after a clean install like you said you were going to try?
 
Yes. I just was tired so didnt want to write. I disconnected everything except ssd and wiped and installed from usb. Only hooked up ROM drive when I needed drivers. Ran all windows updates. Nothing else installed. It actually tried to run Furmark now. I can get 10 seconds in our so before it resets. My hopes at this point are that maybe it will be easier to trouble shoot with less clutter from other software.
 
Ok,

Thank you for helping!

I didn't see a select all option, so I am guessing that you meant list all programs bullet. Here is that log.
 

Attachments

Untitled.png


Copy and Paste the information into your next post. Not attached.

Thank you.
 
Ok, So I did the clean install. Only I think I botched it. I installed the suites for the GPU etc. I think I am having on eof two issues maybe. I see the easytune engine popping up alot in windows event viewer. So, The gigabyte hardware is conflicting with the gigabyte software? Hmmm. I also see entries for a driver that has to do with the multi card reader. Prolly not the problem. I am wondering if it isnt related to MHZ, like the gpu is 1025, ram is something else, and cpu is something else. Perhaps there is a setting I need to change. With this new install I am gettin gto oh 40 to 48% of Furmark test before restart hits again. That is an improvment from the immediate restarts we were getting.

So with the interest of KISS (keep it simple stupid) I am going to reset the pc, wiping contents as if I we giving the computer away. This is in the update and security options. Then I am going to Install ONLY the GPU drivers, not the software, like OC GURU and the like. At this point I am light years from needing it. I *think* all this hardware should work stock, but I can be wrong. (SHOCKER) My thoght process is simply, the less I have in here, the faster You, er I mean we *giggles* can maybe find the actual conflict here. I personally have ruled out bad hardware. I think this is a system issue. Either I have not set something that I should , or a conflict somewhere. Anyways, wish me luck....

I think it is odd that although the system is shutting down and restarting, it isnt creating a dump log......
 
No problem and would never say you were a dunce.

Question??
Whats the HP thing?

What order are you installing things in? Just thinks off all the experience and knowledge you are gaining.

Yes I am learning lots of things. So this isnt an all around bad time. Its actually more about the time. Anyways, the HP reference is from win 7. Sometimes on my old computer I would install HP drivers and it would open catalyst. so i want to install GPU before printers.

I have reset computer. all I have done at this point is install updates. I am going to run a MTB for reference. I am next going to install the cards before anything else, with only drivers for cards, No software like oc guru. And see how they run. I will run another MTB afterwards for comparison. so here we go, round three

(for my sake, everyone please look excited, anxious and on the edge of your seats, makes me feel like Im not alone, ROFL)
 
Here is MTB after fresh install. I installed Killer Network driver, so i could access web to run updates. Updates have been run. This record is after install, update, and the network driver.
 

Attachments

ok.
Fresh windows install.
installed network driver to access web for windows updates.
updated windows.
Followed AMD how to install r9 390 PDF guide. http://64.183.18.101/faq/files/r9390.pdf
Ran Furmark
Immediate shut down and re boot
*note* when I hooked monitor to top card, "plug" was still in hdmi slot. This indicates this was previously the "second" card. I am going to test each card individually again. Previously the test would run for a little bit before resetting system, perhaps the rest was occurring when calling for the second card in crossfire. Gonna try to run test with the now suspected bad card alone. I am sure I did this the other day, but I am going to do it again.
Here is MTB log run after the shut down with both cards installed.
 

Attachments

G'day Papa D. Here is a bit of trivia that may help calm your nerves in regards to reading these log files. The trick is knowing what should be in them, what should not be in them, what will be in them regardless of whether your PC is running right or not and what pertains to your issue. Most things will be harmless. Someone good with these log files can separate the fluff from the chaff. Not to worry. :)
 
Hi there,

Don't mind me, just chirping in here :)

I see in your log that "RzWizard.exe" faulted and rebooted your computer. I need you to remove it and try it again. My gut and brain still point to a overloaded PSU.

RzWizard.exe is related to Razer hardware, but I'm curious to see if you can remove it and run the benchmark without rebooting. If so, that was the culprit. If not, I'm leaning towards your PSU not being able to handle 2 R9 cards in a CF configuration without resetting itself in protection.
 
Status
Not open for further replies.