BSOD due to ntoskrnl.exe (it's back again)

[toucan8]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
repaired.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is OS.

Stage 1: Examining basic file system structure ...


420352 file records processed.

File verification completed.


7446 large file records processed.


0 bad file records processed.

Stage 2: Examining file name linkage ...


530572 index entries processed.

Index verification completed.


0 unindexed files scanned.


0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.


55111 data files processed.
CHKDSK is verifying Usn Journal...


37282104 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

966952959 KB total disk space.
137310152 KB in 245415 files.
166892 KB in 55112 indexes.
0 KB in bad sectors.
555487 KB in use by the system.
65536 KB occupied by the log file.
828920428 KB available on disk.

4096 bytes in each allocation unit.
241738239 total allocation units on disk.
207230107 allocation units available on disk.

C:\Windows\system32>

 

[zbook]

With sfc /scannow corruption fixed by restorehealth please run sfc /scannow again to see that it is a fix that held and to make sure that it was not a temporary fix.

2018-08-07 11:38:57, Info CSI 00000936 [SR] Repairing 1 components
2018-08-07 11:38:57, Info CSI 00000937 [SR] Beginning Verify and Repair transaction
2018-08-07 11:38:57, Info CSI 00000938 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
Found: {l:32 b:ivYjBSQfa2kMsoXhNF6PHD/QNXpNGrW8hLmTnsnlcVs=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2018-08-07 11:38:57, Info CSI 00000939 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2018-08-07 11:38:57, Info CSI 0000093a Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
Found: {l:32 b:ivYjBSQfa2kMsoXhNF6PHD/QNXpNGrW8hLmTnsnlcVs=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2018-08-07 11:38:57, Info CSI 0000093b [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2018-08-07 11:38:57, Info CSI 0000093c [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"
2018-08-07 11:38:57, Info CSI 0000093d [SR] Repair complete

 

[zbook]

See if you zip the latest memory.dmp.
If not then consider the windows 8 repair options.

 

[toucan8]

With sfc /scannow corruption fixed by restorehealth please run sfc /scannow again to see that it is a fix that held and to make sure that it was not a temporary fix.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

Guessing it was fixed. Going to try to zip the files again now. Is there a specific program I should be opening it with or zipping it with? Maybe I'm doing it incorrectly even with the "voidtool" program.

 

[zbook]

7zip is free

 

[toucan8]

Here it is:
MEMORY.7z

 

[zbook]

The memory dump that was posted had this time stamp:
Debug session time: Mon Oct 10 18:31:31.429 2016 (UTC - 5:00)
System Uptime: 0 days 0:01:09.104

Are you able to see whether it is or is not a memory dump from 2016 or 2018?

The DM log collector collected BSOD from 10/2016 but none on the same date.

Bugcheck code 00000139
Arguments 00000000`00000003 ffffd000`315cd350 ffffd000`315cd2a8 00000000`00000000

The debug time and uptime appear to be inconsistent.
When you view the right lower corner of the computer what do you see for the date and time?
Open the website: time.is and compare the two > post an image

If this was the dump for the latest crash then the misbehaving driver was a hardware driver:
Nvidia GPU drivers: nvlddmkm.sys

nvlddmkm nvlddmkm nvlddmkm Kernel Manual Running OK TRUE FALSE 7,344,128 7,163,904 0 6/24/2018 11:43:22 AM C:\Windows\system32\DRIVERS\nvlddmkm.sys 32,768

So at this time lets hold off until there is another BSOD.
When there is another BSOD perform the following steps:
1) Post a new DM log collector zip
2) Find the memory.dmp file and if the date is correct and if the size is < 1.5 GB then zip > post a one drive or drop box share link into the thread

 

[toucan8]

Strange. Is it possible I must have turned off collecting memory.dmp files? I've had dozens since 2016, so I'm not sure why it wouldn't be saving. It's the only one available from voidtools.

 

[toucan8]

Your clock is 0.5 seconds behind.
Accuracy of synchronization was ±0.005 seconds.
from time.is

 

[zbook]

1) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

 

[toucan8]

2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

Can't find this one.

Also note that CCleaner has my graphics card stated incorrectly.

 

[zbook]

For startup and recovery system failure:
a) change small memory dump to automatic memory dump
b) reboot

See if the computer has Windows clean options.
Settings > control panel > administrative tools > disk cleanup > select a drive > use the snipping tool to display the boxes that are checked or unchecked

 

[toucan8]

Done and done.

 

[zbook]

Please review all of the steps in post #62.
Report into the thread the progress with all of the steps.
Was the results of the hardware tests posted?
If there are any new BSOD then run the DM log collector and post a new zip into thread.

 

[toucan8]

I ran hardware tests earlier and the one through Dell, everything came back normal. Here's another BSOD from today.

 

[toucan8]

More BSODs, they're not being saved though (no idea why). The most recent one shows 3 weeks ago, but I had 3 just yesterday. Not sure what the heck is going on with this system.

 

[axe0]

Again sorry for the delay in response, my schedule changed a lot since I'm back in school.

Just to verify, in this post I suggested to try a clean install. Could you confirm whether you did this or not?

 

[toucan8]

Again sorry for the delay in response, my schedule changed a lot since I'm back in school.

Just to verify, in this post I suggested to try a clean install. Could you confirm whether you did this or not?

Hey axe0,

No I did not do a clean install because it hasn't worked previously (last time was a year or so ago), and I have some programs that I can't find the discs for and it would be difficult to reinstall. Is there no hope for fixing these issues without a clean install?

Of course after I did some Windows updates, this machine back to back BSOD about 6 times. It for whatever reason only saved the memory dump for two of them. A nice Christmas surprise from my computer I suppose.

 

[axe0]

Due to the frequence in posting it's very difficult to properly troubleshoot. Sometimes there's months in between posts, everytime there's a delay (more than a few days) I have to reanalyze everything in an attempt to pickup where I left off. Although it's no problem, it's too time consuming. That is why I suggested to do a clean install.

If licenses are an issue, you might want to consider backup software such as Macrium, Acronis or Paragon.
These programs allow you to make a backup of your system which make it possible to quite easily go back to the moment of the backup, that way you could test your system with a clean install.