BSOD errors when I installed new cpu + gpu

philc43 said:

Yes it is perfectly good enough, it's all I and many others on TenForums use.

I received another BSOD
the other minidump files went missing but I have the latest one:
Attachment 118251

Are you running CCleaner? It is probably set up to remove minidump files. Either change these settings or remove it while trying to troubleshoot.

philc43 said:

Are you running CCleaner? It is probably set up to remove minidump files. Either change these settings or remove it while trying to troubleshoot.

I exited out of it and have you found out the cause of the BSOD on the attachment?

The minidump shows that it is a KERNEL_SECURITY_CHECK_FAILURE (139)

There is no sign of which driver might be causing it.

philc43 said:

The minidump shows that it is a KERNEL_SECURITY_CHECK_FAILURE (139)

There is no sign of which driver might be causing it.

Another BSOD, this time it's different

This time the whole computer freezes and i get a WATCHDOGS_VIOLATION BSOD

Attachment 118254

Also another kernel security check failure

The analysis shows that you still have Bit defender drivers causing problems. gzflt.sys is from Bit Defender. Please completely uninstall Bit Defender.

Code:

BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for gzflt.sys
*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46470 )

philc43 said:

The analysis shows that you still have Bit defender drivers causing problems. gzflt.sys is from Bit Defender. Please completely uninstall Bit Defender.

Code:

BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for gzflt.sys
*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46470 )

Ok I deleted Bitdefender and I am now using Windows Defender as you asked.

I'm not confident this will work though.

Any clues for it being the hardware?

2 New BSOD's...

Both of them are Kernal security check failures....

Attachment 118347

The new BSOD information:

First one has a reference to the graphics driver misbehaving again.

Code:

fffff801`bbbac628  fffff808`20cc1efcUnable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3f929cc119e3b994\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xd1efc

The second is less clear but may be hardware related - I tend to think it is still a driver causing this but you have nothing to lose by testing aspects of your hardware.

Code:

BugCheck 139, {3, ffffd200251b56a0, ffffd200251b55f8, 0}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption

If you want to test the memory:

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

More BSOD errors..

This time its happening more frequently:

Attachment 118353