Killer network manager update screwed up my PC

MarkChia

Honorable
Aug 5, 2017
19
0
10,510
So I updated killer network manager just now and I completely messed everything up. Now every time I boot up it just hangs, and I get WHEA_UNCORRECTABLE_ERROR. Tried uninstalling it in safe mode but it didn't work.

What can I do to fix this?
 
Solution
System Repair Disc is probably the most workable option at this point.

Reference:

https://www.howtogeek.com/131907/how-to-create-and-use-a-recovery-drive-or-system-repair-disc-in-windows-8/

(Link applies to Windows 10 also.)

The following link may be more applicable.

https://www.easeus.com/todo-backup-resource/create-windows-10-recovery-disk-for-another-computer.html

Requires EaseUs so that in itself may be another problem for you unless you have access to another system where EaseUs can be installed.

However, there are other factors and options. The following link is more comprehensive:

https://www.isunshare.com/windows-10/3-options-to-create-a-windows-10-recovery-disk.html

Take your time, look for additional links, and work...

Ralston18

Titan
Moderator
Hardware error per the error message.

Did you also just install a Killer network card? Or are you using an existing card? Either way, which card, what OS?

Start by taking a look at the following link:

http://killernetworking.com/driver-downloads/kb/faq/41-problems-with-killer-network-manager

Next, here is a recent and related link from within this forum:

http://www.tomshardware.com/forum/id-3573851/whea-uncorrectable-error-installation-cpu.html

Depending on what overall has transpired you may need to go a step further: Do you have a USB recovery drive?

Need to be able to get booted one way or another.
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510



I'm using a gigabyte z270x gaming k5 and windows 10 home. I'm just using whatever network card came with the motherboard.

No I don't have a recovery usb drive.

I got 3 different Bsod yesterday. Every time I restarted it gave a different error. First one was the whea-uncorrectable_error. Then I did a system restore to before I installed the update to the driver. After that i got irql_not_less_or_equal. The 3rd one was system_service_exception. Now it can't even boot properly, it just shows the aorus splash screen then goes blank although everything seems to be running. I can't even boot to safe mode.
 

Ralston18

Titan
Moderator
Possible that the varying failures may be a faulty/failing PSU.

Open the computer up (power off) and check all connections, cables, card, memory, chip, and jumpers. Make certain that all are fully and firmly in place.

Clean out dust, dirt, debris, hairs, etc.. Make certain that there are no air flow blockages.

If you can get the system to boot again then look at the Event Viewer logs. The logs are likely to be capturing some warning or error code just before or at the time of the BSODs.
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


Thanks, I'll try that later when I'm back from work. The PSU was recommended by the shop because I didn't have any preference and as far as I can tell it's pretty low end. Assuming it is the PSU, why would restarting after the update to killer control centre trigger it?


 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


Its getting worse. I opened it up and did what u suggested as far as i could, then plugged it in and tried again. Now it doesn't even get to the splash screen, the lights flash on and then die, and it keeps on doing this.

video: https://youtu.be/MAJvPwc00Ic

I'm inclined to think that you're right about the faulty PSU because its slowly getting less and less able to power up. My PSU is a seasonic ss-620gb. Any way to test it to make sure its the PSU before trying to claim my warranty?

 

Ralston18

Titan
Moderator
Well there is the "Paperclip Test". E.g.:

https://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59582

There are other similar links with videos. And you could do some more specific testing with a multimeter provided you have some reference documentation regarding expected voltages, etc..

However, intermittent behavior is likely to cause some misleading end results.

If possible borrow a PSU from someone and see if that PSU ends the problems. Otherwise, just claim the warranty.

Killer installation likely to just be a coincidence. Conceivable that the software may have caused some load change that pushed the PSU over the proverbial edge. Stretching things somewhat but I try to stay open minded....
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


I tried plugging it in and look at the PSU Fan, would that give the same results as the paperclip test? I want to keep everything inside as far as I can because I have a bad habit of messing things up more once I start messing with wires.

Anyway the fan in the PSU did start when I did that but then again, it's not completely dead yet.

I shall try borrowing one and see what happens...

Thanks for the help so far
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


As you know you normally can't uninstall via add or remove programs in safe mode. Even after I added a key to the registry it would start the uninstall process but then there would be an error and I forgot what it was.
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


I already did that, like I said it still gives an error probably cos of this "Please note that it is not always possible to uninstall software in Safe Mode because the corresponding installer program requires certain services to be running."

Anyway I already tried a system restore and I cannot boot up now.
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


Update:
I was getting a single beep on start-up which I believe means that the issue is with either the memory or mobo so I reseat my ram and now it's managed to get past the splash screen to a recovery screen that says: "your PC couldn't turn off properly. A required device isn't connected or can't be accessed". Now I'm scared to do anything cos it might go back to not being able to start at all. Where should I go from here? I don't think it will boot(normally or in safe mode). Should I try a recovery usb? I don't have one but I heard I can make one using another computer with windows 10
 

Ralston18

Titan
Moderator
System Repair Disc is probably the most workable option at this point.

Reference:

https://www.howtogeek.com/131907/how-to-create-and-use-a-recovery-drive-or-system-repair-disc-in-windows-8/

(Link applies to Windows 10 also.)

The following link may be more applicable.

https://www.easeus.com/todo-backup-resource/create-windows-10-recovery-disk-for-another-computer.html

Requires EaseUs so that in itself may be another problem for you unless you have access to another system where EaseUs can be installed.

However, there are other factors and options. The following link is more comprehensive:

https://www.isunshare.com/windows-10/3-options-to-create-a-windows-10-recovery-disk.html

Take your time, look for additional links, and work out the viable options with respect to your system.

If there is a hardware failure (or pending hardware failure) then that may make recovery all the more difficult.

Key is to protect yourself from data loss. Backup data if at all possible, first thing once the system is booted.


 
Solution

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


I'm currently running memtest86 to test the ram so if the ram is fine I'll try the recovery disks and assume it's a faulty mobo
 

MarkChia

Honorable
Aug 5, 2017
19
0
10,510


I used the recovery disk and managed to boot into safe mode. :D I still want to know what happened so I'm looking at the logs but there's so many. Any particular ones I should look at?
 

Ralston18

Titan
Moderator
Would be hard pressed to be specific with respect to any given log.

Windows > Setup, System

Applications & Services > Hardware.

Very good chance that whatever happens/happened generated multiple log entries. I would scan the logs for entries just before or at the time of the hangs.

One reason being that the hangs could be a result of some "perfect storm" of events.

No harm in exploring the logs - you may find some other things going on....

Always a learning experience.

Key is to just gather information at first and understand what you find. Be deliberate and focused. Change only one thing at time only if there is actually some negative impact taking place. Many errors are normal "business as usual" and of little consequence.

Such routine errors are used by telephone scammer's (AKA "Windows Services") who use those log entries to convince people that the system has a problem. Then the scammer asks the target victim to grant remote access to the victim's computer.

Supposedly to fix the problem....

All goes very bad thereafter.