BSOD, after I typed in wiNdows 10 pin: 0x0000000a

I am looking for some help attempting to find out what might have caused this BSOD. I have attached the appropriate file. Thank you!

• SNOWBUNNYPC-Tue_09_01_2015_210951_86.zip (237.8 KB, 2 views)

I see you made it, welcome to the forum.

This is being caused by your AV,

Code:

BugCheck A, {20, 2, 0, fffff8027ff18e53}  *** WARNING: Unable to verify timestamp for WRkrn.sys *** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys Probably caused by : WRkrn.sys ( WRkrn+253c )   Followup: MachineOwner --- Loaded symbol image file: WRkrn.sys     Image path: SystemRootSystem32driversWRkrn.sys     Image name: WRkrn.sys     Timestamp:        Wed Aug 26 13:49:34 2015(55DE265E)     CheckSum:         00021E9F     ImageSize:        0001F000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - WRkrn.sys

With that date, I doubt there is anything newer to update to.

You can try uninstalling Webroot and see how it acts.

I see you made it, welcome to the forum.

This is being caused by your AV,

Code:

BugCheck A, {20, 2, 0, fffff8027ff18e53}  *** WARNING: Unable to verify timestamp for WRkrn.sys *** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys Probably caused by : WRkrn.sys ( WRkrn+253c )   Followup: MachineOwner --- Loaded symbol image file: WRkrn.sys     Image path: SystemRootSystem32driversWRkrn.sys     Image name: WRkrn.sys     Timestamp:        Wed Aug 26 13:49:34 2015(55DE265E)     CheckSum:         00021E9F     ImageSize:        0001F000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - WRkrn.sys

With that date, I doubt there is anything newer to update to.

You can try uninstalling Webroot and see how it acts.

Thanks for the welcome

Hey! At the same time I submitted a thread here, I submitted a ticket to Xidax, and they just replied saying it was a driver issue with Intel. Not sure why you're seeing one thing and they're seeing another. They said they installed the driver and I should no longer have that problem.

What do you guys think? I'd like to bring back your suggestion to them.

Just spoke to Xidax. They concurred with you; however, they said they were leaning towards the Chipset driver potentially being an underlying issue. They said I should watch to see if the driver solves it and that worse case scenario, re-install webroot if necessary.

Oh! and one more thing, it only happened that one time. There isn't a BSOD each time or anything.

Thanks guys.

If it's just a single event, it could just be a fluke so no other action is needed until it's a recurring problem.

I'm just telling you what the dump file is blaming, it's not uncommon for a third party AV to cause BSOD's.

If you want to follow through with who ever you talked to that's fine, did you give them the dump to read?

If it's just a single event, it could just be a fluke so no other action is needed until it's a recurring problem.

I'm just telling you what the dump file is blaming, it's not uncommon for a third party AV to cause BSOD's.

If you want to follow through with who ever you talked to that's fine, did you give them the dump to read?

Yea, I had already followed up as soon as I noticed you replied. I gave them the link to this thread actually; they even remotely accessed my computer before I checked to see if someone answered me here. They said they seen how you came up with it and blamed AV too after you already did so first windowssh blog is just too awesome Lol.