Hello, I have a problem with my pc. For a long time now, when turning on the computer, a blue screen pops up with the information 'kmode exception not handled'. The error pops up from 1 second from staying on the desktop to max 10 minutes from staying on the desktop. Sometimes it also happens that this blue screen pops up during the very start of the computer. I have read on this and several other forums how I can solve the problem but none of the ways have been able to help me. I would like to add that the computer works fine in safe mode. If one of the users was able to help me solve the problem, I would be grateful. greetings
Did you do the above or is your troubles gone? Put another SMART disk screen.
W0j734 wrote:
Today, when I tried to enter any website, it wrote to me that the site is unsafe.
It may be a question of expired certificates for certain websites, or problems with certificates, or you are entering the wrong pages and the system (possibly an anti-virus program) is blocking you. Upload a screen from the situation.
It happens. If you want to open a website at your own risk, you do so via Advanced. It is just that such websites may have, for example, an expired certificate and the system reports it. For example, an additional cover here is the full version of Malwarebytes Anti-Malware for real-time protection. Keep your browser up to date.
And when I try to enter the network and internet settings, it immediately throws me out of the settings
Added after 2 [minutes]:
Similarly, I can not enter anything in the magnifying glass next to the start because after typing anything, the magnifying glass disappears for a moment and then appears
Added after 5 [minutes]:
Enabling passive mode in avast did nothing, it keeps popping up that the connection is not private
Added after 5 [minutes]:
And when I enter avast, it says that I don't have internet, but it shows that the internet works. When I click on Fix the problem, something like this pops up:
Added after 13 [minutes]:
This is everything I tried before posting on the forum: I reinstalled the system. There is one and the same tutorial on youtube in order to fix the error, namely: msconfig> services> disabling the application management service in enterprises (in my case, the service does not turn off at all. After clicking "save" and "OK" the service still on). I replaced the graphics card - it did not help. I changed the Disk - it did not help. I tried to restore the system to the point where there was no error and system recovery.
Added after 3 [minutes]:
I have no idea. I am currently doing a Windows system restore to its initial state. I will see if the errors I wrote about today will disappear
I was asking for a clean boot and sending the .dmp files for analysis. You should also have a backup of some live Linux on a USB flash drive or DVD. Since
W0j734 wrote:
the computer works fine in safe mode
this partially rules out hardware problems. You make too much of a mess with your head reading the different opinions. Uninstall Avast itself or don't install it at all, it can introduce its own rules (Sometimes it can't even be uninstalled properly ... https://support.avast.com/en-in/article/Uninstall-Antivirus-Utility )
W0j734 wrote:
And when I enter avast, it says that I don't have internet, but it shows that the internet works. When I click on Fix the problem, something like this pops up:
In the device manager, uninstall the network card without removing the drivers and restart the computer.
W0j734 wrote:
I tried to restore the system to the point where there was no error and system recovery.
I have my system for 6 years without reinstalling it on this computer. I make restore points on a regular basis. Reinstalling the system is a last resort, but if you can't (can't) comply with my requests it makes sense, you can come back to the topic if problems recur.
So far you have written that:
W0j734 wrote:
I forgot to add that I am green in "computer" matters
and since some of the problems relate to network setup, you'll only be guessing without understanding the basic concepts. Yes, as a last resort - I emphasize - use programs like https://www.rizonesoft.com/downloads/complete-internet-repair/ (we make a restore point -> check options 6,7,8) it is quite effective, but it can lead to reinstallation of OS ...
So yeah. Today I did not speak up on the forum because I was putting the whole Windows 10 system up again. From now on, I will download / do what you write.
Added after 7 [minutes]:
The errors I wrote about yesterday have resolved, while the blue screen crashes all the time
Do you have one RAM die? Program indicates memory corruption. Turn off the computer, remove the CMOS battery, remove the RAM skeleton, put the bone back properly, and the battery as well - after about a minute. If the bluescreen appears again, perform the memory test with the Memtest program https://www.elektroda.pl/rtvforum/topic658189.html
You have everything displayed on a tray on the screen. Enter BIOS, set date and time (F2 or Del key). Save the changes. Then enter the system, see what the bluescreen situation is, or restart and enter the BIOS again; set the pendrive as the first bootable drive (Or with the F11 key when starting the computer). Save Changes. Memtest should start automatically after restarting your computer. If you want to try to enter the system right now, key F1.
The discussion revolves around a persistent "kmode exception not handled" blue screen error occurring on a Windows 10 PC. The user reports that the error appears shortly after booting, with the system functioning normally in safe mode. Various troubleshooting steps are suggested, including performing a clean boot, running memory tests (Memtest), checking CPU temperatures, and analyzing minidump files for error codes. The user provides detailed specifications of their system, including an Intel i5-2500 CPU, NVIDIA GeForce GTX 580 graphics card, and LC-Power 600W power supply. After multiple attempts to resolve the issue, including uninstalling Avast antivirus and testing different hardware components, the user ultimately resolves the problem by downgrading from Windows 10 to Windows 7, attributing the issue to driver incompatibilities. Summary generated by the language model.
