Jump to content

TOLeckn

Member
  • Posts

    3
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TOLeckn's Achievements

  1. I ran furmark again and actually got my first BSOD. So not just dead, but dead with BSOD. Progress! Yay? Code is: SYSTEM_SERVICE_EXCEPTION BlueScreenView Infos: says that there is an error with "Ntfs.sys" and "ntoskrnl.exe". Windows Debugger Infos: Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\082719-19750-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 18362 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff800`23800000 PsLoadedModuleList = 0xfffff800`23c46490 Debug session time: Tue Aug 27 16:00:44.795 2019 (GMT+2) System Uptime: 0 days 0:14:30.597 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {80000003, fffff80023deeeec, ffffdd832bbe6f00, 0} Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys *** WARNING: Unable to verify timestamp for hal.dll *** ERROR: Module load completed but symbols could not be loaded for hal.dll ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : ntoskrnl.exe ( nt+5eeeec ) Followup: MachineOwner --------- Minidump-File: https://www.dropbox.com/s/48xmecaxlq1q7dn/082719-19750-01.dmp?dl=0 And I know, I havn't tried DDU yet, but I will when I have the time. Thx, Oliver
  2. Ok, I havn't found a solution, but I figured out that deactivating HDR in Win10 results in killing the glitches. So, the PC doesn't die anymore when I run 3D Mark with SLI. BUT I still can't overclock, it almost immediate crashes as soon as I touch the sliders in MSI Afterburner. And I still can't run a CPU Stress Test in Furmark without the whole PC crashing. So the question still remains: Is there some piece of Hardware in my PC broken? The CPU? The Mainboard? Can anybody help? Thx, Oliver
  3. Hi, I tried to overclock my GPUs by using MSI Afterburner and 3D Mark Demo (Time Spy) and ran into the problem that my PC started crashing at an overclock of 50 MHz (I started overclocking with +50). Limit of Core Voltage, Power, and Temp to MAX of course. The Time Spy benchmark failed after the Demo. The screen glitched with purple/white/green distortions, I saw 3D Mark with way too high saturation, the screen went black, turned off, back on (black, but with backlight), off, on and then the PC died (didn't turn off on its own, but nothing happened anymore.) The next day I just wanted to play some games like, Need for Speed Payback, Dirt Rally or Project Cars (so newer titles that are graphic intense). And the games crashed after some minutes to half an hour. It actually did that before overclocking too, but I thought that it was just the game crashing. I only then realised now that It happens on every graphic intense game and not just one or two. (I havn't played graphic intense games lately just Anno 1602 or doing light work with my PC (browsing the web, and so on).) So I began troubleshooting: I figured out that the benchmark would only fail if I ran my GPUs in SLI. If i turned off SLI, or only put one GPU into my mainboard (I even tried a different PCI-Slot), the Screen would still have the glitches/distortions between the parts of the Time Spy benchmark, but the PC wouldn't crash. Then I downgraded my Nvidia Driver to an older Version (430.86) (with reinstall option in the setup activated). After that the Benchmark actually ran without crashing the PC with SLI on. But still glitches/distortions between the parts of the Time Spy benchmark. Then I downloaded Furmark. I ran the GPU Stress Test with Dynamic Background, Burn-in, Xtreme burn-in, Post-FX activated in 2560x1440 for 30 minutes. The Temperatures of the GPUs were 90°C for the first and 80°C for the second GPU. (propably because of the CPU cooler, not much space in between the Cooler and the GPU backplate) The PC didn't fail, no problems in the image, no distortions nothing. Everything fine. Then I tried the PC burner on all cores. PC freezed after 10 seconds. Restarted the PC tried again, freezed after 30 seconds, next day same test, freezed after a minute, max a few minutes. It allways freezes my PC. I'm kinda lost right now... Is the CPU broken and causes the GPUs to fail in games and Time Spy benchmark? I also testet Cinebench R15. The PC dosn't crash but I think the test just isn't long enough. Score is identical to my old score btw. The CPU always runs an 4.7 GHz, it's not slowing down. My PC: Win 10 Home V1903 Build: 18362.295 MSI Z370 godlike gaming (BIOS 7A98vA8) Intel i9 9900k (Be Quiet Dark Rock Pro 3) 2x MSI 1080Ti Gaming X Trio (stock cooling) (SLI bridge was included with the motherboard) Enermax Platimax 1700W I hope someone here can help me, thanks for reading. PS: I downloaded DDU and gonna report how that worked out tomorrow. Thx, Oliver
×