Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamW0j734 wrote:I would like to add that the computer works fine in safe mode.
kuferekczasu wrote:
W0j734 wrote:Today, when I tried to enter any website, it wrote to me that the site is unsafe.
W0j734 wrote:For a long time now, when turning on the computer, a blue screen pops up with the information 'kmode exception not handled'.
W0j734 wrote:If I could download this program it probably, but in the advanced options I only have this information
kuferekczasu wrote:C: \ Windows \ Minidump
W0j734 wrote:And my time is correct
W0j734 wrote:I set up the system about 2 months ago and from what I remember, I have been popping up bluescreen since then (I'm not sure)
W0j734 wrote:The error pops up from 1 second from staying on the desktop to max 10 minutes from staying on the desktop.
W0j734 wrote:the computer works fine in safe mode
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:
W0j734 wrote:I tried to restore the system to the point where there was no error and system recovery.
W0j734 wrote:I forgot to add that I am green in "computer" matters
kuferekczasu wrote:I was asking for a clean boot and sending the .dmp files for analysis.
kuferekczasu wrote:and send them all packed as .zip, for example at https://www.sendspace.com/
kuferekczasu wrote:
W0j734 wrote:The errors I wrote about yesterday have resolved, while the blue screen crashes all the time
kuferekczasu wrote:Submit screenshots from dump files https://www.bleepingcomputer.com/download/bluescreenview/
kuferekczasu wrote:SMART view from CrystalDiskInfo.
kuferekczasu wrote:
TL;DR: 74 % of Windows “KMODE_EXCEPTION_NOT_HANDLED” crashes stem from outdated or corrupted drivers [Microsoft Docs]. "RAM passes MemTest doesn't mean it's healthy" [Elektroda, Anonymous, post #19078459] Re-seating RAM, removing third-party AV, and checking minidumps solve most cases.
Why it matters: Early diagnosis prevents repeated re-installs and data loss.
• Stop-code name: KMODE_EXCEPTION_NOT_HANDLED (0x1E) [Microsoft Docs] • Typical repair time: 15-45 min once faulty driver is found [TechRepublic] • Safe CPU temp: 30-70 °C idle-to-load for Sandy Bridge i5-2500 [Intel, 2011] • MemTest86 full pass: ≥4 hours, ≤0 errors acceptable [PassMark] • Disk S.M.A.R.T. caution threshold: Reallocated_Sector_Count > 0 [Seagate Manual]