[SOLVED] BSOD Error IRQL_NOT_LESS_OR_EQUAL (Includes All The Docs About Issue)

May 2, 2019
12
1
15
0
Hello everyone.
I was suffering with BSOD for 5 years with my laptop. The frequency varies, I really love my laptop and obsessed to solve this issue.
I am not too much into tech but checked and read a lot I have lots of information. Your help would be really appreciated.

  1. Current frequency of BSOD(s) in a single day : 2
  2. Memtest (Done)
  3. Detailed Driver Updates (Done) (except BIOS update, I am afraid a lot to do that update)
  4. Malware tests etc. (Done)
  5. Brand new OS Install
SYSTEM INFO:



ERROR SCREEN:



MINIDUMP FILE (DOWNLOAD)

DETAILED DUMP REPORT

  • Bugcheck Analysis *
  • *
***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000408855, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8040124da6a, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Acer

SYSTEM_PRODUCT_NAME: Aspire V3-772G

SYSTEM_SKU: Aspire V3-772G_0781_1.13

SYSTEM_VERSION: V1.13

BIOS_VENDOR: Insyde Corp.

BIOS_VERSION: V1.13

BIOS_DATE: 10/11/2013

BASEBOARD_MANUFACTURER: Acer

BASEBOARD_PRODUCT: VA70_HW

BASEBOARD_VERSION: Type2 - Board Version

DUMP_TYPE: 1

BUGCHECK_P1: 408855

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8040124da6a

READ_ADDRESS: 0000000000408855

CURRENT_IRQL: 0

FAULTING_IP:
nt!PpmUpdatePerformanceFeedback+da
fffff8040124da6a f6055588400021 test byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff804016562c6)],21h

CPU_COUNT: 8

CPU_MHZ: 893

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DESKTOP-B7CC09T

ANALYSIS_SESSION_TIME: 05-02-2019 14:38:25.0886

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: ffff898df466f4e0 -- (.trap 0xffff898df466f4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffa6819777def0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8040124da6a rsp=ffff898df466f670 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmUpdatePerformanceFeedback+0xda:
fffff8040124da6a f6055588400021 test byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff804016562c6)],21h ds:fffff804016562c6=00
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff804013c3c69 to fffff804013b30a0

STACK_TEXT:
ffff898d
f466f398 fffff804013c3c69 : 000000000000000a 0000000000408855 00000000000000ff 0000000000000000 : nt!KeBugCheckEx
ffff898d
f466f3a0 fffff804013c08e5 : 0000000000000000 0000000000000000 0000000000000000 ffffa6819777dec8 : nt!KiBugCheckDispatch+0x69
ffff898d
f466f4e0 fffff8040124da6a : 00000173ce12511d fffff8040124e4d2 000001a317c48728 0000001ef9bf7d6c : nt!KiPageFault+0x425
ffff898d
f466f670 fffff8040124ce27 : 0000000000000000 0000000000000000 ffffa6819777dec8 00000006a3be8713 : nt!PpmUpdatePerformanceFeedback+0xda
ffff898d
f466f720 fffff8040124c265 : 0000000000000003 0000000000000002 0000000000000000 01d500d8ec8d861c : nt!PpmIdleExecuteTransition+0xa37
ffff898d
f466fb00 fffff804013b67ac : ffffffff00000000 ffffa68197778180 ffffa68197788200 ffff9180cb0f4080 : nt!PoIdle+0x345
ffff898d
f466fc60 0000000000000000 : ffff898df4670000 ffff898df466a000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC: 7293b8a719eade9bf044bb08185d8d546f0cf608

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e89703eb7edf405287b613e78a584cb829287b59

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP:
nt!PpmUpdatePerformanceFeedback+da
fffff804
0124da6a f6055588400021 test byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff804016562c6)],21h

FAULT_INSTR_CODE: 885505f6

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!PpmUpdatePerformanceFeedback+da

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ca31432

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: da

FAILURE_BUCKET_ID: AV_nt!PpmUpdatePerformanceFeedback

BUCKET_ID: AV_nt!PpmUpdatePerformanceFeedback

PRIMARY_PROBLEM_CLASS: AV_nt!PpmUpdatePerformanceFeedback

TARGET_TIME: 2019-05-02T11:19:35.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-04-02 10:50:10

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 80d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!ppmupdateperformancefeedback

FAILURE_ID_HASH: {2cff52de-5a3f-765a-d6a1-cf4ebe07fdc5}

Followup: MachineOwner
---------

6: kd> !blackboxbsd
Stream size mismatch (expected = 168, read = 136)
6: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132012562917551863
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196}
VetoString :

6: kd> .trap 0xffff898df466f4e0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffa6819777def0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8040124da6a rsp=ffff898df466f670 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmUpdatePerformanceFeedback+0xda:
fffff804
0124da6a f6055588400021 test byte ptr [nt!PerfGlobalGroupMask+0x6 (fffff804016562c6)],21h ds:fffff804016562c6=00
6: kd> lmvm nt
Browse full module list
start end module name
fffff80401209000 fffff80401b5b000 nt (pdb symbols) c:\temp\ntkrnlmp.pdb\C76519BFA4E546A89109C76B141069311\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Timestamp: Tue Apr 2 00:50:10 2019 (5CA31432)
CheckSum: 008AF836
ImageSize: 00952000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
MEMTEST REPORT

Summary
Report Date2019-05-02 10:36:29
Generated byMemTest86 V8.1 Free (64-bit)
ResultPASS
System Information
EFI Specifications2.31
System
ManufacturerAcer
Product NameAspire V3-772G
VersionV1.13
Serial NumberNXM8UEY002351083087200
BIOS
VendorInsyde Corp.
VersionV1.13
Release Date10/11/2013
Baseboard
ManufacturerAcer
Product NameVA70_HW
VersionType2 - Board Version
Serial NumberNBM8S11001351042E67200
CPU TypeIntel Core i7-4702MQ @ 2.20GHz
CPU Clock2195 MHz [Turbo: 2893.3 MHz]
# Logical Processors8
L1 Cache4 x 64K (121152 MB/s)
L2 Cache4 x 256K (34083 MB/s)
L3 Cache6144K (25690 MB/s)
Memory32652M (15146 MB/s)
DIMM Slot #08GB DDR3 PC3-12800
Kingston / ACR16D3LS1KFG/8G / EC3AAA56
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
DIMM Slot #18GB DDR3 PC3-12800
Kingston / ACR16D3LS1KFG/8G / E93A0757
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
DIMM Slot #28GB DDR3 PC3-12800
Kingston / ACR16D3LS1KFG/8G / ED3AA756
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
DIMM Slot #38GB DDR3 PC3-12800
Kingston / ACR16D3LS1KFG/8G / E73A9F56
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
Result summary
Test Start Time2019-05-01 23:05:11
Elapsed Time9:03:37
Memory Range Tested0x0 - 85F600000 (34294MB)
CPU Selection ModeParallel (All CPUs)
ECC PollingEnabled
# Tests Passed48/48 (100%)


Test# Tests PassedErrors
Test 0 [Address test, walking ones, 1 CPU]4/4 (100%)0
Test 1 [Address test, own address, 1 CPU]4/4 (100%)0
Test 2 [Address test, own address]4/4 (100%)0
Test 3 [Moving inversions, ones & zeroes]4/4 (100%)0
Test 4 [Moving inversions, 8-bit pattern]4/4 (100%)0
Test 5 [Moving inversions, random pattern]4/4 (100%)0
Test 6 [Block move, 64-byte blocks]4/4 (100%)0
Test 7 [Moving inversions, 32-bit pattern]4/4 (100%)0
Test 8 [Random number sequence]4/4 (100%)0
Test 9 [Modulo 20, ones & zeros]4/4 (100%)0
Test 10 [Bit fade test, 2 patterns, 1 CPU]4/4 (100%)0
Test 13 [Hammer test]
 
Last edited:

Colif

Titan
Moderator
Its all fairly alien to me too but Gardeman, the guy I asked to convert files, puts them into a format I can understand.

Yours seem to blame ntkrnlmp.exe which is part of windows, but that is normal for dumps. They don't always tell you what caused it right off, you have to look at what was running at time and work it out from there.
 
Reactions: Caloripher
May 2, 2019
12
1
15
0
Thanks a lot to follow my issue. ntkrnlmp.exe seems guilty for me too. I had checked all the threads about ntkrnlmp.exe but unfortunately almost all the forums and threads got same solution advices in all sort of BSOD threads with different *.exe files. Like reinstall the drives, check the memory, check the drive and update bios drives etc. But I need to find out the exact faulty part of my issue software (driver) or hardware issue . Than I can have the remedy.
I installed windows from the very fresh copy,
Re-installed all the hardware drivers by wiping old versions out.
Checked hdd(s) without any error
Checked memory sticks with memtest86, almost for 16 hours with 4 passes (which supposed to be more than enough) rams supposed to be ok too.
Than there might be 4 issues in my "noob" opinion
  1. I still got faulty drivers
  2. bios driver is not updated (which is too risky for me to do)
  3. Chipboard (MOtherboard) is faulty
  4. CPU is faulty
I can replace them as soon as I realize what is the problem.

But as I informed I am obsessed with that BSOD error I am gonna solve it at all cost. And hug my old (relatively) laptop like a virgin.
 

Colif

Titan
Moderator
I didn't mean for you to chase it, the fix is likely another driver. It is part of windows kernel, which sits between applications and hardware. it as well as ntoskrnl are always blamed for BSOD as they do so much. Often they crash from being asked to do the wrong thing.

We need to wait for gardenman, I should have mentioned he could be asleep still.
 
Reactions: Caloripher
May 2, 2019
12
1
15
0
Thanks a lot to follow my issue. ntkrnlmp.exe seems guilty for me too. I had checked all the threads about ntkrnlmp.exe but unfortunately almost all the forums and threads got same solution advices in all sort of BSOD threads with different *.exe files. Like reinstall the drives, check the memory, check the drive and update bios drives etc. But I need to find out the exact faulty part of my issue software (driver) or hardware issue . Than I can have the remedy.
I installed windows from the very fresh copy,
Re-installed all the hardware drivers by wiping old versions out.
Checked hdd(s) without any error
Checked memory sticks with memtest86, almost for 16 hours with 4 passes (which supposed to be more than enough) rams supposed to be ok too.
Than there might be 4 issues in my "noob" opinion
  1. I still got faulty drivers
  2. bios driver is not updated (which is too risky for me to do)
  3. Chipboard (MOtherboard) is faulty
  4. CPU is faulty
I can replace them as soon as I realize what is the problem.

But as I informed I am obsessed with that BSOD error I am gonna solve it at all cost. And hug my old (relatively) laptop like a virgin.
BTW; the conditions of the time when BSOD appears are quite stange. No press on CPU or Ram seems happen, the temprature of CPU cores are like 40-50 Degrees (in Celcius)
 
May 2, 2019
12
1
15
0
I didn't mean for you to chase it, the fix is likely another driver. It is part of windows kernel, which sits between applications and hardware. it as well as ntoskrnl are always blamed for BSOD as they do so much. Often they crash from being asked to do the wrong thing.

We need to wait for gardenman, I should have mentioned he could be asleep still.
:) Thanks a lot, then I will be waiting for Gardenman, I am not gonna sleep :)
 
May 2, 2019
12
1
15
0
shame I have to, its almost 3am but he might be in soon so i can wait another hour or so, and then I will look again tomorrow anyway.
Thanks a lot, I strongly suggest you go to sleep, melatonin is something we all need and we can get it only if we sleep well ;)
 

gardenman

Admirable
Herald
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/Prb3.html

File information:050219-7281-01.dmp (May 2 2019 - 07:19:35)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 3 Hour(s), 41 Min(s), and 43 Sec(s)

System page: https://www.acer.com/ac/en/US/content/support-product/4732?b=1
There is a BIOS update available for your system (version 1.15). You are using version 1.13. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: Caloripher
May 2, 2019
12
1
15
0
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/Prb3.html

File information:050219-7281-01.dmp (May 2 2019 - 07:19:35)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 3 Hour(s), 41 Min(s), and 43 Sec(s)

System page: https://www.acer.com/ac/en/US/content/support-product/4732?b=1
There is a BIOS update available for your system (version 1.15). You are using version 1.13. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Gardenman thanks a lot to you. I've been waiting for your precious comments. Also Colif (I really appreciate your help 👽 you are a great alien) . (don't know how to tag a user)
As far as I see I need to update my BIOS driver which is the most hardest decision for me. (Just imagine the preparation and stress before "The Long Night" in Winterfell, you might empathize with me. )

I already downloaded latest BIOS driver yesterday. I tried to install latest driver via windows 10 (not via BIOS opening screen and USB opening etc) the progress bar stucked. And not progressed (Although it is a progress bar). I had to restart my Laptop using Power Button. Just Imagine how many calories I might lost. I was thinking that my Laptop get "bricked"

Somehow nothing happened and then I tried for a second time, my Laptop freeze and I had to restart again via power button.

On BIOS opening I faced with some sort of "alien" screen, followed a couple of advises, like pushing multiple keys at once and releasing and plugging battery cable and unplugging.

Somehow managed to survive, (Like Samwell Tarly in GoT)

Now only option is to use USB version of BIOS update.

But don't know any idea I've been checking all the info online. But most of 'em are old or related with different sort of devices.

If you can guide me to a clear guide of BIOS update for my Laptop I'll be trying for the last time.

Thanks a lot for your great support!!

Best Regards
 

Colif

Titan
Moderator
The only way to update your BIOS is via windows

The BIOS updates provided are Windows-based only. We do not offer a DOS executable file for these updates. Perhaps other Community users here can provide suggestions on a work-around for you.
https://community.acer.com/en/discussion/463939/how-to-update-bios-without-windows-on-v3-372

what I would suggest you do is look at the 2nd post here and run Driver verifier as your PC has 5 old drivers on it, and the IRQ error could be one of those, instead of BIOS.
 
May 2, 2019
12
1
15
0
The only way to update your BIOS is via windows


https://community.acer.com/en/discussion/463939/how-to-update-bios-without-windows-on-v3-372

what I would suggest you do is look at the 2nd post here and run Driver verifier as your PC has 5 old drivers on it, and the IRQ error could be one of those, instead of BIOS.
Dear Colif, first of all in my calculations It supposed to be 5 am in the morning in your local time and you are still answering about my thread. You a great man / woman..

Before the last option which is BIOS update (as Gardenman suggested) And I will be checking to update my BIOS via Windows as you suggested.)

Meanwhile before the last option/step ı will be following the path you had described in your clearly prepared tutorial

Handy details to include in Blue Screen of Death posts

Especially the via the driver verifier tool et.

I'll be updating you with the result(s)

Thanks to you Colif also Gardenman about your helpful efforts.
 
May 2, 2019
12
1
15
0
Don't do the bios until we are sure it isn't a driver.
And yes, I am going now
Hi Colif and Gardenman hope you all are well!

Colif I do the driver check via (insidious) driver verifier tool.

Here is the story:

I had created a restore point and and a bootable USB as you suggested in case.

A warning for the readers who are gonna use driver verifier:
CREATING RESTORE POINT & BOOTABLE USB IS !MANDATORY!

1. As soon as I rebooted, my laptop went into BSOD loop before the opening of windows. With the error as follows:

DRIVER_VERIFIER_DETECTED_VIOLATION



2. After a couple of loop windows went into recovery or repair mode automatically and managed to start as usual meanwhile it seems like the verifier also stopped automatically.

I had checked via following command on cmd:

verifier /querysettings

and see this:



Which supposed to show that verifier is not running, (Please confirm if you can, I don't want it to be running on background :) )

Here below I would like to share the minidump file created during Verifier Running and related with "DRIVER_VERIFIER_DETECTED_VIOLATION" error.

MINIDUMP FILE (DOWNLOAD)


Also I would like to share the report I get from MEMORY.DMP file via WinDbg Tool.

Code:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Page 2000013fa too large to be in the dump file.
Page 200002fd5 too large to be in the dump file.
Page 200002fd5 too large to be in the dump file.
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`dc29c000 PsLoadedModuleList = 0xfffff803`dc6492b0
Debug session time: Fri May  3 11:45:28.681 2019 (UTC + 3:00)
System Uptime: 0 days 0:00:07.670
Page 2000013fa too large to be in the dump file.
Page 200002fd5 too large to be in the dump file.
Page 200002fd5 too large to be in the dump file.
Loading Kernel Symbols
Page 2000013fa too large to be in the dump file.
.Page 20000277f too large to be in the dump file.
Page 200000516 too large to be in the dump file.
.Page 2000078f3 too large to be in the dump file.
Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
Page 200098e77 too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
Page 20000c0ea too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
.Page 2000013fa too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.Page 200000517 too large to be in the dump file.
..Page 200000516 too large to be in the dump file.
.
Page 20084003e too large to be in the dump file.
.Page 20084203f too large to be in the dump file.
.Page 200004d1b too large to be in the dump file.
.Page 200097d23 too large to be in the dump file.
.Page 200098f2e too large to be in the dump file.
.Page 2000008d7 too large to be in the dump file.
.Page 20009829d too large to be in the dump file.
.Page 200099d38 too large to be in the dump file.
Page 200005662 too large to be in the dump file.
.Page 2000975f1 too large to be in the dump file.
.Page 2000056f3 too large to be in the dump file.
.Page 200845598 too large to be in the dump file.
.Page 20000579f too large to be in the dump file.
.Page 20000579f too large to be in the dump file.
.Page 200096c85 too large to be in the dump file.
.Page 20000332f too large to be in the dump file.
.Page 20000570c too large to be in the dump file.
Page 200007d97 too large to be in the dump file.
.Page 20000570c too large to be in the dump file.
.Page 2000056ab too large to be in the dump file.
.Page 20000570c too large to be in the dump file.
.Page 2000032dc too large to be in the dump file.
.Page 20000333c too large to be in the dump file.
.Page 2000032bb too large to be in the dump file.
.Page 2000032bb too large to be in the dump file.
.Page 200003389 too large to be in the dump file.
.Page 200844878 too large to be in the dump file.
.Page 200007c6f too large to be in the dump file.
.Page 200096d86 too large to be in the dump file.
.Page 200096d86 too large to be in the dump file.
.Page 200096d86 too large to be in the dump file.
.Page 200003399 too large to be in the dump file.
.Page 200003399 too large to be in the dump file.
.Page 200003284 too large to be in the dump file.
.Page 200096d93 too large to be in the dump file.
.Page 20000327e too large to be in the dump file.
.Page 200094807 too large to be in the dump file.
.Page 200004d36 too large to be in the dump file.
.Page 2000080b7 too large to be in the dump file.
.Page 200008251 too large to be in the dump file.
.Page 200000261 too large to be in the dump file.
..Page 200008cec too large to be in the dump file.
.Page 200008c1a too large to be in the dump file.
.Page 20000c1ac too large to be in the dump file.
.Page 20000be42 too large to be in the dump file.
.Page 20000c144 too large to be in the dump file.
.Page 20000be42 too large to be in the dump file.
.Page 20000cc4c too large to be in the dump file.
.Page 20000c4ab too large to be in the dump file.
.Page 200007483 too large to be in the dump file.
.Page 20000e400 too large to be in the dump file.
.Page 20000c1f0 too large to be in the dump file.
.Page 20000e400 too large to be in the dump file.
.Page 20000eba2 too large to be in the dump file.
.
Loading User Symbols

Loading unloaded module list
.....
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80296e58d9c, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000646d6342, Pool Tag (if provided).

Debugging Details:
------------------

Page 200002d7e too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002ddb too large to be in the dump file.

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

DUMP_TYPE:  1

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff80296e58d9c

BUGCHECK_P3: 0

BUGCHECK_P4: 646d6342

BUGCHECK_STR:  0xc4_2000

CPU_COUNT: 8

CPU_MHZ: 893

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 24'00000000 (cache) 24'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-B7CC09T

ANALYSIS_SESSION_TIME:  05-03-2019 11:59:16.0390

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LOCK_ADDRESS:  fffff803dc6635a0 -- (!locks fffff803dc6635a0)

Resource @ nt!PiEngineLock (0xfffff803dc6635a0)    Exclusively owned
    Contention Count = 1
    NumberOfExclusiveWaiters = 1
     Threads: ffff9f0935f6d700-01<*> 

     Threads Waiting On Exclusive Access:
              ffff9f0932adb700       
1 total locks

PNP_TRIAGE_DATA: 
    Lock address  : 0xfffff803dc6635a0
    Thread Count  : 1
    Thread address: 0xffff9f0935f6d700
    Thread wait   : 0x1ea

LAST_CONTROL_TRANSFER:  from fffff803dcab9443 to fffff803dc4460a0

STACK_TEXT:  
Page 200002d7e too large to be in the dump file.
Page 200002d7e too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d7d too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d56 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002d55 too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
Page 200002ddb too large to be in the dump file.
ffffeb85`901db0c8 fffff803`dcab9443 : 00000000`000000c4 00000000`00002000 fffff802`96e58d9c 00000000`00000000 : nt!KeBugCheckEx
ffffeb85`901db0d0 fffff803`dc5463cb : fffff803`dc63917c 00000000`00002000 fffff802`96e58d9c 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf
ffffeb85`901db110 fffff803`dcab13fc : 00000000`646d6342 fffff803`dc63917c fffff802`96e58d9c 00000000`00000000 : nt!VfReportIssueWithOptions+0x103
ffffeb85`901db160 fffff803`dcaaf4a3 : 00000000`00000000 ffffeb85`901db2a9 00000000`00021000 fffff802`93bd8063 : nt!VfCheckPoolType+0x90
ffffeb85`901db1a0 fffff802`96e58d9c : 00000000`00000001 00000000`00000098 00000000`00000098 00000000`00010286 : nt!VerifierExAllocatePoolWithTag+0x53
ffffeb85`901db1f0 fffff802`96e6a324 : ffff9f09`3ad86000 00000000`00000098 ffff9f09`3ad9ce60 00000000`00000000 : k57nd60a!nd6x_on_hook_bcc+0x50
ffffeb85`901db220 fffff803`dc88ea79 : 00000000`00000000 ffff9f09`3ad9ce60 00000000`00000012 ffffffff`800002a4 : k57nd60a!DriverEntry+0x324
ffffeb85`901db310 fffff803`dc88ddbb : 00000000`00000000 00000000`00000000 00000000`00000004 fffff181`00000004 : nt!IopLoadDriver+0x4bd
ffffeb85`901db4f0 fffff803`dc86696e : ffffd981`d03d6001 00000000`00000000 ffff9f09`358b9900 ffffffff`800001b4 : nt!PipCallDriverAddDeviceQueryRoutine+0x1b7
ffffeb85`901db590 fffff803`dc86638b : 00000000`00000000 ffffeb85`901db6a0 ffff9f09`6e657050 00000000`00000012 : nt!PnpCallDriverQueryServiceHelper+0xd6
ffffeb85`901db640 fffff803`dc8659d1 : ffff9f09`358bd010 ffffeb85`901db8f0 ffff9f09`358bd010 ffff9f09`339b1d20 : nt!PipCallDriverAddDevice+0x40f
ffffeb85`901db7f0 fffff803`dc8eb9bd : ffff9f09`3ab6a260 ffffeb85`901dbb19 ffff9f09`3ab6a260 ffff9f09`3ab6a2b0 : nt!PipProcessDevNodeTree+0x1f1
ffffeb85`901dba70 fffff803`dc3e1e69 : ffff9f01`00000003 ffff9f09`3ab6a260 00000000`00000000 00000000`00000000 : nt!PiProcessStartSystemDevices+0x59
ffffeb85`901dbac0 fffff803`dc351b05 : ffff9f09`35f6d700 ffff9f09`32ad09b0 fffff803`dc661e80 ffff9f09`32ad09b0 : nt!PnpDeviceActionWorker+0x469
ffffeb85`901dbb80 fffff803`dc3cc2d7 : ffff9f09`35f6d700 00000000`00000080 ffff9f09`32abf440 ffff9f09`35f6d700 : nt!ExpWorkerThread+0xf5
ffffeb85`901dbc10 fffff803`dc44d516 : ffffd981`d06e8180 ffff9f09`35f6d700 fffff803`dc3cc290 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffeb85`901dbc60 00000000`00000000 : ffffeb85`901dc000 ffffeb85`901d6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  25d9f67fd78f0e194baf5e7bbc16596b9fc62a77

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  45c1d142e029b54ec9143675b5253fd8c3563e4c

THREAD_SHA1_HASH_MOD:  06a15979f7b2c9800f65b8e35c90528344ee72cd

FOLLOWUP_IP: 
k57nd60a!nd6x_on_hook_bcc+50
fffff802`96e58d9c 4889053df00000  mov     qword ptr [k57nd60a!g_bcc_ptr (fffff802`96e67de0)],rax

FAULT_INSTR_CODE:  3d058948

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  k57nd60a!nd6x_on_hook_bcc+50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: k57nd60a

IMAGE_NAME:  k57nd60a.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55d53872

IMAGE_VERSION:  15.6.1.3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  50

FAILURE_BUCKET_ID:  0xc4_2000_VRF_k57nd60a!nd6x_on_hook_bcc

BUCKET_ID:  0xc4_2000_VRF_k57nd60a!nd6x_on_hook_bcc

PRIMARY_PROBLEM_CLASS:  0xc4_2000_VRF_k57nd60a!nd6x_on_hook_bcc

TARGET_TIME:  2019-05-03T08:45:28.000Z

OSBUILD:  17134

OSSERVICEPACK:  706

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-04-02 10:50:10

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  6055

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc4_2000_vrf_k57nd60a!nd6x_on_hook_bcc

FAILURE_ID_HASH:  {c4ad4bb3-249b-6672-7173-9ab610edc072}

Followup:     MachineOwner
---------

1: kd> lmvm k57nd60a
Browse full module list
start             end                 module name
fffff802`96e00000 fffff802`96e71000   k57nd60a   (pdb symbols)          c:\temp\k57nd60a.pdb\F7A077AE24534B7CAC0ABF5E5192C0AD1\k57nd60a.pdb
    Loaded symbol image file: k57nd60a.sys
    Image path: k57nd60a.sys
    Image name: k57nd60a.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 19 19:16:18 2015 (55D53872)
    CheckSum:         0006F016
    ImageSize:        00071000
    File version:     15.6.1.3
    Product version:  15.6.1.3
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Broadcom Corporation
        ProductName:      Broadcom NetLink (TM) Gigabit Ethernet Driver
        InternalName:     k57nd60a.sys
        OriginalFilename: k57nd60a.sys
        ProductVersion:   15.6.1.3
        FileVersion:      15.6.1.3
        FileDescription:  Broadcom NetLink (TM) Gigabit Ethernet NDIS6.x Unified Driver.
        LegalCopyright:   Copyright 2000-2011, Broadcom Corporation.
 

Colif

Titan
Moderator
Aug 19 2015k57nd60a.sysBroadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver

well, there isn't a new one on the Acer website since 2014, and its for win 8.

it seems there was problems with this driver last year - https://appuals.com/fix-broadcom-netlink-gigabit-ethernet-driver-stops-working-in-windows-10/

you might need to buy an ethernet card and use it instead, it appears to be answer many have done for this - https://www.windows10forums.com/threads/broadcom-netlink-tm-gigabit-ethernet.12976/

Driver verifier is always running, it just isn't always testing. I think you got it right.
 
Last edited:
Reactions: Caloripher
May 2, 2019
12
1
15
0
Aug 19 2015k57nd60a.sysBroadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver

well, there isn't a new one on the Acer website since 2014, and its for win 8.

it seems there was problems with this driver last year - https://appuals.com/fix-broadcom-netlink-gigabit-ethernet-driver-stops-working-in-windows-10/

you might need to buy an ethernet card and use it instead, it appears to be answer many have done for this - https://www.windows10forums.com/threads/broadcom-netlink-tm-gigabit-ethernet.12976/

Driver verifier is always running, it just isn't always testing. I think you got it right.
Dear Colif you are great man!

Thanks for all your supports / efforts / time.

I had progressed and learned a lot during our conversations.

I am checking to buy new ethernet card for permanent solution. Meanwhile I checked the links you had shared and realised people had used another driver which is right now not available on official support pages. I found it anyway and updated the driver, which is dated Nov 19 2015 (not quite) in anycase right now the file Broadcom Netlink Gigabit Ethernet is using changed as "b57nd60a.sys" :)

The Driver That I Downloaded (Click to Download)
!!! I shared the file in any case to help people with same problem. The file is ok right now (virus or maleware free) but I don't own the link and source please virus check before download in the future. !!!

But all the Ethernet and Driver issue is something ridiculous don't know if its the fault by Microsoft Windows or Broadcom.

I will be also updating later what happened after the change of the Ethernet Card.

THANK YOU! THANK YOU! THANK YOU! COLIF YOU ARE THE BEST!! (y)

P.S. Should I mark the thread as solved and wonder how can I make it :) ???
 
Last edited:

Colif

Titan
Moderator
May 2, 2019
12
1
15
0
https://forums.tomshardware.com/threads/how-to-award-best-answers.3450478/

its also in my sig :)

its likely Broadcom as they aren't supporting the hardware with drivers that work. Microsoft are lenient, they gave hardware makers years to update drivers, it seems every year or so older lan card drivers are added to list that shouldn't work anymore.

its also in my sig :)
Sorry! I am blind ASF.

AN ADDITIONAL UPDATE:

IRQL_NOT_LESS_OR_EQUAL problem seems solved with the great help of Colif.

After 6 hours a new BSOD appeared which is:

UNEXPECTED KERNEL MODE TRAP

Which happened for the very first time, I had checked all the DMP files etc. Problem seems like double error or some other issue. Anyway I checked the threads in here too, there are various scenarios.

I felt kind of frustrated and decided the last thing I haven't done. Which is BIOS Update and luckily I managed to done the BIOS Update via Windows 10 (as Colif suggested).


My laptop is open for 6 hours for now will be left open for 24 to 48 hour. There are no BSOD for now.

(I am also still aware, Ethernet card replacement with a new card who got an updated driver for Windows 10 is mandatory for me, I did not forget evil "k57nd60a.sys" file from Broadcom Ethernet.)

 
May 2, 2019
12
1
15
0
Hi again, I keep my laptop turned on for 48 hours for test possible BSODs and for the entire period I had not faced any of them, which is never happened for 5 years. (I was used to get BSODs twice a day).
My BSOD problem completely SOLVED! :)
 
Reactions: BringerOfTea

ASK THE COMMUNITY

TRENDING THREADS