BSOD on win10 (also 7) Multiple / day clean installs

AngryOne · 28 Dec 2015

Getting BSOD on Win7, Win10 both while gaming. replaced graphics card (twice) 2 different cards. ntoskrnl.exe was one I recall. Maybe causing memory corruption now. Typically only occurs using ArchAge Game. reinstalled game a few times as well. reinstalled windows 7 4 times, then upgraded to 10

Dropbox - STACY-PC-Mon_12_28_2015__51036_22.zip Requested files here. Also stressing card using Heaven for 8 hours caused no troubles at all. Prime 95 ran a 2-3 hours with no troubles also. Any other feedback greatly appreciated.

Edit: Neglected to mention have swapped drives as well from standard 1tb hd to SSD as well. Also replaced thermal paste on prior GTX 960 before replacing with current card. Temps seem okay at ~56c Any further info please request and happy to provide.

axe0 · 29 Dec 2015

For pre-caution.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

Please check MSI for BIOS updates.
MSI Global

Please update your Realtek ethernet driver
Driver Reference Table - rt640x64.sys

Code:

ffffd000`24777228  fffff800`e16c8c4cUnable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
 rt640x64+0x18c4c
2: kd> lmvm rt640x64
start             end                 module name
fffff800`e16b0000 fffff800`e1744000   rt640x64 T (no symbols)           
    Loaded symbol image file: rt640x64.sys
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Timestamp:        Wed Oct 07 17:03:55 2015 (5615345B)
    CheckSum:         0009543E
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
Attachment 55923

Code:

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
2: kd> lmvm atikmdag
start             end                 module name
fffff800`e18e0000 fffff800`e2def000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Nov 04 22:39:32 2015 (563A7B14)
    CheckSum:         014AB74E
    ImageSize:        0150F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

AngryOne · 29 Dec 2015

Thank you for the quick tutorial. I'm updating all drivers now and will run memtest overnight as instructed and post results in the morning.

AngryOne · 30 Dec 2015

First and foremost thank you, Very very much for the help.

https://www.dropbox.com/s/u1hl2q3v7o9ndom/20151230_075505-1.jpg?dl=0 memtest86 results.

Another crash last night sadly :S
Removed ALL drivers using ddu in safemode disabled windows driver finding with it as well. Then reinstalled using latest Amd Radeon drivers (The nvidia drivers were for a gtx960 that I thought was causing the bsod's)

From WhoCrashed:
On Wed 12/30/2015 3:20:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122915-8312-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFD00098153B30, 0xFFFFD0009B6F5EE0, 0xFFFFF80085169890)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 12/30/2015 3:20:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFD00098153B30, 0xFFFFD0009B6F5EE0, 0xFFFFF80085169890)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Re-Ran to collect newest logs after changes as well.

axe0 · 30 Dec 2015

Please run DDU again, remove everything of AMD but ONLY install the drivers using custom/advanced installation.
A driver known for causing bluescreens has been installed again on your system.

Code:

Event[2885]:  Log Name: System
  Source: Service Control Manager
  Date: 2015-12-29T20:12:13.777
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Stacy-PC
  Description: 
A service was installed in the system.


Service Name:  AODDriver4.3
Service File Name:  C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys
Service Type:  kernel mode driver
Service Start Type:  auto start
Service Account:

AngryOne · 30 Dec 2015

Ok reinstalled with only HDMI Audio and Same driver version and no other options. That being said without Catalyst control panel the screen is not showing about 1/5 of what it should. Any harm in installing CCC to under-scan?

axe0 · 30 Dec 2015

Let's hope there isn't any harm with CCC installed.

AngryOne · 30 Dec 2015

I checked coretemp @ time of crash thinking MAYBE an overheating issue but 51c under load hardly seemed too hot for graphics card.
Below seems to point at DX. Going to check upgrade on there JUST to cover my rear as it was AMD that installed DX on this system.

On Wed 12/30/2015 10:30:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123015-8437-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidSchiExecuteMmIoFlipAtISR+0x23)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF800340E2D33, 0xFFFFD000E5838DD8, 0xFFFFD000E58385F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Wed 12/30/2015 10:30:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidSchiExecuteMmIoFlipAtISR+0x23)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF800340E2D33, 0xFFFFD000E5838DD8, 0xFFFFD000E58385F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

axe0 · 31 Dec 2015

DirectX refers to the display drivers what usually means the graphics card drivers.
The DirectX driver is a Windows driver, what means that you get new version through Windows Update.

AngryOne · 31 Dec 2015

axe0 I'd like to thank you for the help! I went ahead reinstalled windows 7 just to see if it fixes the issues. Would it help you out in any way/shape/form if I marked this as solved? Going to see how win7 treats with HD wipe. Just some troubles getting sound drivers to work so far. but no gaming so no forced crashes yet.