BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.inf

[anthracis]

BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.inf

Whenever I shut down my computer, I'm met with a BSOD. There are two variations of the error message I don't remember exactly, something about a driver and something about the kernel. I ran a system file check, and in the CBS log I get what appears to be a common issue:

2013-12-07 08:05:57, Info CSI 000007ff [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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

SFC said it could not fix the errors it found. I ran chkdsk /r on the drive twice and repeated the SFC, but I'm still getting the error. The only time I get the BSOD is on shutdown. It wouldn't be a huge deal, but the drive can't shut down cleanly - when it doesn't shut down cleanly, I can't mount it from Linux, which is the OS I use most of the time.

I've attached the log, it had to be zipped because of the size. Any ideas?

 

[Tekno Venus]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

Hi,

This may not be the cause of the BSODs, but please see my tutorial for fixing the SFC corruption - www.sysnative.com/forums/windows-up...prncacla-inf-corruptions-windows-8-8-1-a.html.

Regards,
Stephen

 

[anthracis]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

That fixed the SFC error! But you're right, I'm still getting BSODs on shutdown. Can you suggest what I should try next?

Thanks!

 

[Tekno Venus]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

Fantastic!

For the BSOD, can you please follow the https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

I will do my best to assist you, but BSODs are (no longer) my speciality. I currently have no internet access until Monday, so cannot assist until then. Hopefully someone else can help you in the mean time. :)

Stephen

 

[x BlueRobot]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

I should be around most of tonight, and tomorrow morning. I'll should also be free tomorrow evening too.

 

[anthracis]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

I followed the link to prepare a BSOD post, and saw a link to the driver verification tutorial. I followed it, expect I selected every driver, not just those not made by Microsoft, and I don't get the BSOD! And I can mount the drive in Linux!

Thank you for helping a random internet stranger with their problem :)

 

[x BlueRobot]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

That's good news, please update us if you have any other problems.

 

[Patrick]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

It should be noted that Driver Verifier is a diagnostic tool, it doesn't solve anything. You not getting BSOD's is likely temporary unless you made any other changes to the system aside from enabling Verifier. However, now that you've enabled DV, the next crash will be detailed and help us find out what's going on.

Regards,

Patrick

 

[TomasD]

Re: BSOD on 8.1 - getting that "hash mismatch" for "Amd64\CNBJ2530.DPB" of prncacla.i

It should be noted that Driver Verifier is a diagnostic tool, it doesn't solve anything. You not getting BSOD's is likely temporary unless you made any other changes to the system aside from enabling Verifier. However, now that you've enabled DV, the next crash will be detailed and help us find out what's going on.

Regards,

Patrick

In addition, having Driver Verifier enabled on many drivers (especially the Microsoft ones), adds huge performance penalty on the system, making it sluggish. Therefore, Driver Verifier should be disabled as soon as the cause is identified.