Windows 10: 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!

:)

 

After updating to windows 10 my pc always Crash so help plz

Thanks for replay

• I meant the system (windows 10)
• I repeatedly get BSOD
• yes
• since I updated to windows 10
• No

these are example for error message I get:

KMODE_EXCEPTION_NOT_HANDLED

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

SYSTEM_SERVICE_EXCEPTION 0x0000003b

IRQL_NOT_LESS_OR_EQUAL 0x0000000a

DRIVER_OVERRAN_STACK_BUFFER 0x000000f7

I uploaded my dump files at my 1st post

 

I've been having BSOD errors with my Lenovo Yoga 2 13 over the past few weeks, BSOD IRQL_NOT_LESS_OR_EQUAL.

* Original Title: BSOD IRQL_NOT_LESS_OR_EQUAL

I've been having BSOD errors with my Lenovo Yoga 2 13 over the past few weeks with some freezing happening the other day (unresponsive to mouse and keyboard, hard shutdown required). Most of the BSODs have displayed a IRQL_NOT_LESS_OR_EQUAL error with the
bugcheck code 0x0000000a. Just trying to get some ideas here on whether it may be a faulty driver or hardware. I did a complete reset and fresh install of Windows 10 yesterday and it had been working fine until today when the same BSOD came up. After the reset,
I updated the following drivers: Intel HD Graphics version 20.19.15.4331, Lenovo ACPI-Compliant Virtual Power Controller version 13.52.34.549, BIOS build 96CN31WW(V1.17)

System Specs:

Lenovo Yoga 2 13"

Windows 10 Home

OS build 10586.218

Intel Core i5 4210U CPU

8 GB RAM

Here is the most recent BSOD dump file (Created from BlueScreenView)

Bug check string: IRQL_NOT_LESS_OR_EQUAL

BCC: 0x0000000a

Parameter 1: 00000000`00000008

Parameter 2: 00000000`00000002

Parameter 3: 00000000`00000000

Parameter 4: fffff803`2e9e9675

Caused by driver: hal.dll

Caused by address: hal.dll+1b675

Crash address: ntoskrnl.exe+142760

Any help is greatly appreciated, thanks.

 

I see you made it, welcome to the forum. *Smile

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: \SystemRoot\System32\drivers\WRkrn.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[/quote] 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.

 

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.[/quote] Thanks for the welcome *Wink

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?

 

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 *Wink Tenforums is just too awesome Lol.