win 10 memory mangement error

[Ork]

I am having a blue screen error for last few weeks. At first I thought it was because the windows.
So I have installed a new fresh copy of windows 10 enterprise 64 bit. But unfortunately the still having the error.
Sometimes the PC runs well for few days without any error, but all of a sudden it shows the error and restarts. Points to be noted- During gaming it never showed any error. Error comes only when before shut down or after few mins of boot up, sometimes when start working after idling for a while.
So today after googling I have ran the whocrashed and got a report which says- This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)

My config- Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: G1.Sniper B6, Gigabyte Technology Co., Ltd., G1.Sniper B6-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17066622976 bytes total (1- 8GB G-Skill 1600mhz and 2 – Avexir 4GB 1600mhz modules)
GPU- Asus Strix GTX 960 4GB – Driver version 385
PSU- Corsair VS650
There are two HDDs
Samsung 500 GB
WD 500 GB (Recently I am having a tick type sound from a HDD. I am not sure from which one)

There is no overheating issue as CPU is cooled by CM Masterliquid and the temp never crosses 45 under load. System and GPU temps are also good. (Running in a TT View 31 enough coolers)

Recent crash dump reports are as follows-

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 1/5/2018 11:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010518-13890-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B17282, 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

On Fri 1/5/2018 5:06:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010518-13546-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x18 (0x0, 0xFFFFE000553E2060, 0x10, 0x1)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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 REFERENCE_BY_POINTER

After installing the windows today I have setup the drivers using DriverPack_17.6.13_Offline.
Windows update is turned off for now. Not received any update in the new windows.

Now can anyone please take a look and tell me what to do?
Thank you in advance

 

[dextermat]

Hi,

download memtest86 burn to disk and test the ram: RMA if defective

 

[Ork]

Hi,

The problem is not the RAM I guess, because I have tried using three different ram sticks. Errors are coming with all of them, while the rams running without any problem in other PC. Also windows memory diagnostic found no problem in the memory.

Btw I have uninstalled the Intel display driver and running with only 8GB ram now. Now I am having some new errors- Unexpected_Kernel_Mode_Trap, Critical_Structure_Corruption and Attempted_Execute_Of_Noexecute_Memory.

 

[jr9]

Can you go to you minidump folder, gather as many .dmp files as you can, and upload them to somewhere like OneDrive so we can have a look at them. WhoCrashes doesn't dig deep enough, we need to use another debugger and compare the crashes to eachother. Right now it could be anything, hardware or software failure.

If you cannot see any files in C:\Windows\Minidump then you may have to enable logging although if whocrashed is picking up logs then they should be there.

Avoid using automatic driver programs, they cause more problems then they help. Windows 10 already has most drivers built in.

If I had this PC to work on and had no restrictions, I would

0. Safe mode malware scan

1. Confirm the motherboard has a video port that works with the display, Reinstall intel integrated video driver, restart PC, trigger a safe mode boot in Windows 10, boot into safe mode and use Display driver uninstaller to remove all NVIDIA drivers, shutdown PC and uninstall the graphics card and hook up the display to the monitor. Confirm system is functional with integrated graphics

1.5 Disconnect both the HDD drives

2. Clean install the OS again. When finished, immediately disable Windows update.

3. Shutdown and reinstall the graphics card, then boot up and reinstall the drivers. If anything crashes at this point, it's a hardware issue or an issue with drivers.

4. Reconnect the HDD drives and see if anything crashes

5. Create a system restore point then let Windows update off the leash. If it screws up the PC, restore to the restore point.