- Joined
- Mar 13, 2007
- Messages
- 856 (0.13/day)
- Location
- Eastern Tennessee
System Name | Firebird |
---|---|
Processor | Ryzen 7 1700X |
Motherboard | MSI X370 Titanium |
Cooling | Tt Water2.0 PRO (They use the same bracket as 3.0) |
Memory | G.Skill TridentZ 2x8GB 3200 15-15-15-35 B-Die (@3333 ATM) |
Video Card(s) | ASUS STRIX R9 390 8GB |
Storage | Too many. Samsung 750GB, 120GB 850 EVO, Seagate 1TB, Toshiba 1TB, OCZ 32GB Cache Drive |
Display(s) | Samsung 46" UN46D6050 1080P HDTV |
Case | Home-made tech bench. |
Audio Device(s) | ASUS Xonar Essence STX (I use HDMI though *cry*) |
Power Supply | CWT PUC1000V-S 1000W, Abee Supremer (import) 1200W currently used as primary. |
Mouse | Razer Copperhead (circa 2005) |
Keyboard | Tt Challenger Pro (AVOID! Keys wear super fast) |
Software | Win 10 Pro x64 |
Benchmark Scores | Meh. |
Alright, I got around to finally going through with this since I was done figuring out what was causing the crashes. I found that it most likely was driver related since defaulting my system to factory clocks.
I didn't follow the guide in exactly the right order, I'll admit :\ I did find a few things out. Mainly, it seems so far that deleting almost every trace of ATi from the system AND registry, might not be the smartest of moves lol I've been looking at the laptop here typing this, and twice the Windows Repair has loaded which means that there was a fairly large error in booting into Windows >_> PROBABLY should've done the deletions in stages, but it's (IMO) kind of hard since every reboot would result in the system trying to install drivers, thus creating more work to clean up making it a non ending loop heh So I may have taken my cleaning, a bit too extreme.
I'll just list basically all I can remember, so someone can possibly point out my error, but also so some of you don't exactly follow in my footsteps since it'll lead you off a cliff
Window's Repair finally finished doing whatever it thought it could, which it was unable to repair anything. Reason given: "Problem Signature 07: BadDriver" (verbatim). It did list some other stuff, but nothing seemed of much relevance. By that I mean there were Problem signatures 1-7, with #1&2 being "6.1.7600.16385", #3 "unknown", #4 "24", #5 "AutoFailover" and #6 "1".
Trying to boot under SafeMode and it seems that my above move of deleting System32\Drivers files would indeed be the "oops" moment :S It starts loading the files, which they are all coming from that directory, and then BSOD and reboot (sadly I have it set to auto reboot so I don't get to see what it says).
Last ditch effort is to do "System Restore" in Windows Repair. I'll edit back with the results, not that it REALLY matters since the important info is above for what NOT to do!
Me-><-Me
But while most people see this as a situation to get mad or frustrated over, I look at is as a learning experience that while it may have been my doing, I can easily undo it with a simple reinstall of windows Which I had set on the back burner as what I'd end up doing if this uber-cleaning didn't fix the stability issue I've been having Live and learn!
EDIT: Alright... First off, System Restore failed for some reason. Couldn't copy an ATi file. Which if it was in the DriverStore folders I can understand it. But I thought System Restore had it's own storage area and so that wouldn't matter? :\ I noticed also in the F8 boot options to not restart on BSOD, so I've got the very short and vague error screen o_0 Pretty much your typical idiot message that starts with "A problem has been detected and Windows has been shut down to prevent damage to your computer" following with "If this is the first time..." sentence and follows up with "Check for viruses..."
Only thing it gives is:
*** STOP: 0x0000007B (0x80786B58, 0xC0000034, 0x00000000, 0x00000000)
Never seen a solid 0 one before, let alone two! heh
So I think I'm left with reinstalling Windows, but I'm going to try a drastically radical idea first..... Erocker, check your PM lol
I didn't follow the guide in exactly the right order, I'll admit :\ I did find a few things out. Mainly, it seems so far that deleting almost every trace of ATi from the system AND registry, might not be the smartest of moves lol I've been looking at the laptop here typing this, and twice the Windows Repair has loaded which means that there was a fairly large error in booting into Windows >_> PROBABLY should've done the deletions in stages, but it's (IMO) kind of hard since every reboot would result in the system trying to install drivers, thus creating more work to clean up making it a non ending loop heh So I may have taken my cleaning, a bit too extreme.
I'll just list basically all I can remember, so someone can possibly point out my error, but also so some of you don't exactly follow in my footsteps since it'll lead you off a cliff
- Ran Cat Install Manager (CIM), uninstalled everything.
- Ran Driver Sweeper and removed nVidia everything (this Windows install was previously on a nF4 S949 system).
- Zipped up my Cat installers under a non ATi name, because the last time I ever used Driver Sweeper it would remove them too and I didn't want to have to redownload anything
- Compressed some items in the WinXS\Backup folder to save space (100mb saved, my HDD has less than a gig free )
- Went through the System32\DriverStore, DRVSTR and Drivers folders, deleting anything nV and ATi related. (this is the most likely move that could have been the error)
- Went through System32 also deleting anything ATi, AMD and nV related.
- Went through the Registry to see if indeed the entries in my previous post had been removed by CIM, they had not.
- Deleted every trace of ATi/AMD (had some residual AMD OverDrive items) and nVidia entries (this also could have been the error)
- Ran Driver Sweeper for ATi entries, none showed up.
- Went into Device Manager, uninstalled both 5770s and chose the "Delete drivers for this device" option
- Scanned for new hardware, the task tray popup appeared informing me it was installing new devices, then failed to do so. (probably why Window's isn't able to load, as a result of something above)
Window's Repair finally finished doing whatever it thought it could, which it was unable to repair anything. Reason given: "Problem Signature 07: BadDriver" (verbatim). It did list some other stuff, but nothing seemed of much relevance. By that I mean there were Problem signatures 1-7, with #1&2 being "6.1.7600.16385", #3 "unknown", #4 "24", #5 "AutoFailover" and #6 "1".
Trying to boot under SafeMode and it seems that my above move of deleting System32\Drivers files would indeed be the "oops" moment :S It starts loading the files, which they are all coming from that directory, and then BSOD and reboot (sadly I have it set to auto reboot so I don't get to see what it says).
Last ditch effort is to do "System Restore" in Windows Repair. I'll edit back with the results, not that it REALLY matters since the important info is above for what NOT to do!
Me-><-Me
But while most people see this as a situation to get mad or frustrated over, I look at is as a learning experience that while it may have been my doing, I can easily undo it with a simple reinstall of windows Which I had set on the back burner as what I'd end up doing if this uber-cleaning didn't fix the stability issue I've been having Live and learn!
EDIT: Alright... First off, System Restore failed for some reason. Couldn't copy an ATi file. Which if it was in the DriverStore folders I can understand it. But I thought System Restore had it's own storage area and so that wouldn't matter? :\ I noticed also in the F8 boot options to not restart on BSOD, so I've got the very short and vague error screen o_0 Pretty much your typical idiot message that starts with "A problem has been detected and Windows has been shut down to prevent damage to your computer" following with "If this is the first time..." sentence and follows up with "Check for viruses..."
Only thing it gives is:
*** STOP: 0x0000007B (0x80786B58, 0xC0000034, 0x00000000, 0x00000000)
Never seen a solid 0 one before, let alone two! heh
So I think I'm left with reinstalling Windows, but I'm going to try a drastically radical idea first..... Erocker, check your PM lol
Last edited: