Pc strange crash

[fiddy04]

Hello.

The last 2 days i've been having some issues with my pc. Mostly randomly but like every 30minutes or so it crashes but not like any other time. Most of the time im playing then it happens like this: the game continues to run without problem, but i cant move my cursor and the keybord literally stops working so i cant ctrl+del. I reinstalled win10, updated all my drivers, tried a bunch of repair programs but nothing seems to be working. I have clue its my old vga, but i dont know. My config: intel i5-2500k, sapphire radeon hd 7950, 8gb 2400hz g-skill ram, msi z77-a g41 plus mboard. Thanks in advance!

 

[Guest]

What's your PSU? Are all the temps fine? Have you tried running Whocrashed?

 

[fiddy04]

What's your PSU? Are all the temps fine? Have you tried running Whocrashed?

PSU is Approx 700W. Checked the temps already, its good. I've tried Whocrashed it says:
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
No valid crash dumps have been found on your computer.

I have to restart the pc manually, so i dont know if the program counts it as a crash.

 

[Grobe]

I would suspect capacitors on mobo going defect. Those caps don't live forever. Look at the top sealing and see if it's looking exploding or bulbing out slightly.

 

[fiddy04]

I would suspect capacitors on mobo going defect. Those caps don't live forever. Look at the top sealing and see if it's looking exploding or bulbing out slightly.

Every capacitor looks normal to me.

 

[fiddy04]

Finally whocrashed worked properly.
On Tue 2018. 02. 27. 0:20:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022718-24890-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0xDEADDEAD (0x1, 0x2, 0x19B963EC, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys MANUALLY_INITIATED_CRASH1

2 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

whocrashedex.sys
nt_wrong_symbols.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Grobe]

Does it ever crash when you're conducting other activities than just gaming on your machine?

 

[fiddy04]

Does it ever crash when you're conducting other activities than just gaming on your machine?

Maybe once but im not sure. Vga is dying maybe? Sometimes it crashed 10min into a game other times after 3 hours. I play old games that not really need performance.

 

[Grobe]

For further eliminating of failure sources I recommend you getting a program that can log GPU temperatures. Start the logging before starting the game.

 

[fiddy04]

For further eliminating of failure sources I recommend you getting a program that can log GPU temperatures. Start the logging before starting the game.

Checked:
RAM-memtest
CPU-Intel tool
GPU-Furmark
HDD:HD Tune
No error found by these programs. Gpu max temperature was 75c which is good.
Read on forums that maybe windows 10's new upgrade has some issue with AMD. Theres also a topic about Intel network problems. Im still clueless tho..
Whocrashed said, nt_wrong_symbols.sys is the problem, searched for these symbols, i found a file that was modified recently, maybe thats causing the problem, but i dont know what to do with it. Files name is: Symbols[1] Location:
C:\Users\szepe\AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\AC\INetCache\UVD26H5R

 

[Grobe]

Ok, so then you've pretty much ruled out GPU temperature problems.
What is left is just everything else, such as bad capacitors (you might not be able to spot one), bad soldering spot somewhere on the mobo or just an unstable psu.
Unfortunately that is not all - until you actually swap your GPU, or PSU and use the swapped component for a while, there is no way to say for sure where the fault is located.

 

[fiddy04]

Ok, so then you've pretty much ruled out GPU temperature problems.
What is left is just everything else, such as bad capacitors (you might not be able to spot one), bad soldering spot somewhere on the mobo or just an unstable psu.
Unfortunately that is not all - until you actually swap your GPU, or PSU and use the swapped component for a while, there is no way to say for sure where the fault is located.

You were kinda right before, two of the usb ports i've been using for like 6 years became trash. I tried reconnecting both the mouse and the keyboard when it "crashed" but they were totally faulty. Put them in new ports now everything is fine! I feel stupid but it was too easy to be true.. Thank you for your help Grobe, appreciate it!