logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

[Solved] Bluescreen z info "kmode exception not handled"

W0j734 33840 47
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
| New topic
  • #31 19079797
    W0j734
    Level 5  
    If I already have the Windows Memory Diagnostics application on my computer, do I have to download memtest86?
  • ADVERTISEMENT
  • #32 19079811
    Anonymous
    Level 1  
  • #33 19079853
    W0j734
    Level 5  
    Memory Diagnostics with Windows Memory Diagnostics did not indicate any error. Now I will download memtest86 and check what comes out with the tdgo device

    Added after 4 [minutes]:

    and here is the report: Bluescreen z info "kmode exception not handled"
  • Helpful post
    #34 19079864
    Anonymous
    Level 1  
  • ADVERTISEMENT
  • #35 19079881
    W0j734
    Level 5  
    All the time

    Added after 33 [minutes]:

    Currently it looks like this: Bluescreen z info "kmode exception not handled"

    Added after 4 [minutes]:

    Could you please write me what should I pay attention to during this test?
  • Helpful post
    #36 19079989
    Anonymous
    Level 1  
  • #37 19080323
    W0j734
    Level 5  
    I did 4 tests for 2h and 46min which did not detect any memory error. Continue the test or not?

    Added after 18 [minutes]:

    Now I'm going to turn off the memtest, send you these Tempreatur Snapshots and turn on the memtest for the night again

    Added after 34 [minutes]:

    https://obrazki.elektroda.pl/7131423200_1606768591.png
  • #38 19081008
    Kolobos
    IT specialist  
    Have you installed a new system on that other drive? Have you changed Tasme Sata to another one? Did you connect to a different input on the board?
  • #39 19081039
    W0j734
    Level 5  
    I took the disk he is currently using from my brother. I did not replace the sata tape
  • ADVERTISEMENT
  • #40 19081065
    Kolobos
    IT specialist  
    Then replace the tape and check all sata ports.
  • #41 19082296
    W0j734
    Level 5  
    Inserting a different sata cable didn't help
  • #42 19082560
    Kolobos
    IT specialist  
    Have you checked all sata ports?
  • #43 19083058
    W0j734
    Level 5  
    I have checked all the ports and without any changes, the bluescreen is blowing all the time
  • ADVERTISEMENT
  • #44 19083806
    Kolobos
    IT specialist  
    Include in the attachment logs from FRST, from scanning (addition.txt and frst.txt).

    Also remove the drivers for the graphics card, sound card and other devices (one each) and test if something changes.
  • #46 19088114
    W0j734
    Level 5  
    The problem has not been solved all the time, if someone would like to help me, please
  • Helpful post
    #47 19088390
    Kolobos
    IT specialist  
    Uninstall Avast.
    Install the latest drivers for your graphics card.

    As for the rest, you have probably just swapped, checking the processor on a different board, everything you have with another board. Replacing the card with another one.
  • #48 19135988
    W0j734
    Level 5  
    After downgrading from w10 to w7, the problem was gone. It was most likely a problem with the drivers, but I couldn't find this faulty driver. now, after 2 weeks of normal use, the computer does not crash any errors. thanks to everyone for trying to help, best regards
| New topic
Report a violation of the law

Topic summary

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.
ADVERTISEMENT