Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Need Help ... BSOD nt_wrong_symbols.sys

  • Please log in to reply
1 reply to this topic

#1 alanhe


  • Members
  • 1 posts
  • Local time:02:26 PM

Posted 04 January 2018 - 02:10 PM



I've been getting this error for the last few days ... always looks to be the same diagnostic when analysed with WhosCrashed.


I'd appreciate of anyone could diagnose a possible error





Attached Files

Edited by alanhe, 04 January 2018 - 02:14 PM.

BC AdBot (Login to Remove)


#2 jcgriff2


  • BSOD Kernel Dump Expert
  • 1,109 posts
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:10:26 AM

Posted 04 January 2018 - 11:25 PM

I get invalid symbol errors as well. It could be that Microsoft just hasn't added the new symbols to the symbol server.

See if Driver Verifier can help here - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

If BSOD while Verifier is running, get the dump; zip it up and attach.

Driver Verifier must run for at least 24 hours - or until BSOD.

However, I suspect that we're dealing with UNKNOWN hardware failure here.

Regards. . .

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users