BSOD "Kernel Thread Priority Floor Violation"

B

ByteSlinger

Member
Joined
Jan 20, 2017
Posts
6
  • OS - Windows 10
  • 64 bit
  • Original OS / Win 7 (Upgraded during free update period / Fresh install)
  • Self built system, desktop, mostly 3 years old (No hardware changes in over a year)
  • Win 10 update approximately 4/5 months ago
  • CPU - Intel i7-4790K (@4GHz)
  • GPU - Nvidia GTX 760
  • RAM - 16GB (2x 8GB) Corsair Vengence 1600MHz DDR3
  • MoBo - Asus Maximus VII Ranger Z97
  • PSU - Corsair CS750M

My computer has always run fantastically up until just a few weeks ago.
The first thing I started noticing is once, maybe twice a day, I'd notice my primary monitor flicker. It would be less than a second and that was it.
Next I had a couple of times where my screens both restarted then when everything came back online, my primary monitor wouldn't until I restarted the computer.
Most recently (over the last week), I've had 4 blue screens. Usually just when browsing the web but twice I wasn't even actively using the computer, one of which it was locked and wasn't running anything in the background.

GPU driver is all up to date, as is everything else I can find.

Any help would be greatly appreciated.

Thanks
 

Attachments

I've just tried running Driver Versifier as recommended on the BSOD posting page and it resulted in me getting a bluescreen as soon as my desktop appeared after login every time I restarted.
Luckily I restored to a point just before running the versifier. Not sure if that helps at all?
 
ByteSlinger said:
I've just tried running Driver Versifier as recommended on the BSOD posting page and it resulted in me getting a bluescreen as soon as my desktop appeared after login every time I restarted.
Luckily I restored to a point just before running the versifier. Not sure if that helps at all?
Click to expand...

not at all, i picked up one dumpfile (biggest one) for a rush
Code: 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8030c6fa20a, Address of the instruction which caused the bugcheck
Arg3: ffffe101bc5cc7d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1104

BIOS_DATE:  07/16/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  MAXIMUS VII RANGER

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8030c6fa20a

BUGCHECK_P3: ffffe101bc5cc7d0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP: 
nt!ObpCaptureHandleInformation+82
fffff803`0c6fa20a 8a4028          mov     al,byte ptr [rax+28h]

CONTEXT:  ffffe101bc5cc7d0 -- (.cxr 0xffffe101bc5cc7d0)
rax=0000000000000000 rbx=00000000000008f4 rcx=ffffe101bf43e0c8
rdx=ffff99087a6f22c0 rsi=ffffe101bf400050 rdi=fffff8030c6fa188
rip=fffff8030c6fa20a rsp=ffffe101bc5cd1e8 rbp=ffffcd86c469d3d0
 r8=ffffcd86c469d3d0  r9=00000000000008f4 r10=ffffe101bc5cd278
r11=0000000000000434 r12=0000000000000000 r13=ffffe101bc5cd2b8
r14=ffffcd86c108aa40 r15=000000000017fffc
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObpCaptureHandleInformation+0x82:
fffff803`0c6fa20a 8a4028          mov     al,byte ptr [rax+28h] ds:002b:00000000`00000028=??
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa7

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR=#ff0000]CODE_CORRUPTION[/COLOR]

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  SKYLAKE1

ANALYSIS_SESSION_TIME:  01-20-2017 20:48:29.0165

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8030c73f94b to fffff8030c6fa20a

STACK_TEXT:  
ffffe101`bc5cd1e8 fffff803`0c73f94b : 00000000`000008f4 00000000`00000000 ffff9908`00000000 00000000`00000000 : nt!ObpCaptureHandleInformation+0x82
ffffe101`bc5cd1f0 fffff803`0c6fa100 : fffff803`0c6fa188 ffffe101`bf43e0c8 ffffe101`0017fffc ffffe101`bc5cd324 : nt!ExpSnapShotHandleTables+0x127
ffffe101`bc5cd270 fffff803`0c73d65b : ffffe101`bc5cd324 00000000`0003e090 00000000`0017fffc 00000000`00000000 : nt!ObGetHandleInformation+0x3c
ffffe101`bc5cd2b0 fffff803`0c65a5f9 : 00000000`00000010 00000000`00020000 ffffe101`bf400050 ffff9908`819243c0 : nt!ExpGetHandleInformation+0x53
ffffe101`bc5cd2f0 fffff803`0c51545b : 00000000`00000004 00000000`00000000 ffffffff`ffffffff 00000000`00000002 : nt! ?? ::NNGAKEGL::`string'+0x4e3b9
ffffe101`bc5cdac0 fffff803`0c1e7393 : ffff9908`7c3945c0 00000000`00000000 ffffe101`bc5cdad8 ffff9908`7c3255d0 : nt!NtQuerySystemInformation+0x2b
ffffe101`bc5cdb00 00007ffb`0d376794 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`09fce248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`0d376794


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8030c1371d2 - nt!MiResolvePrivateZeroFault+212
    [ f6:f3 ]
    fffff8030c1371fa-fffff8030c1371fc  3 bytes - nt!MiResolvePrivateZeroFault+23a (+0x28)
    [ 40 fb f6:c0 f9 f3 ]
    fffff8030c137218-fffff8030c137219  2 bytes - nt!MiResolvePrivateZeroFault+258 (+0x1e)
    [ 80 fa:00 81 ]
    fffff8030c1378b9-fffff8030c1378ba  2 bytes - nt!MiCompletePrivateZeroFault+519 (+0x6a1)
    [ 80 fa:00 81 ]
    fffff8030c13794f-fffff8030c137951  3 bytes - nt!MiCompletePrivateZeroFault+5af (+0x96)
    [ 40 fb f6:c0 f9 f3 ]
    fffff8030c15b926 - nt!MmMapLockedPagesSpecifyCache+106 (+0x23fd7)
    [ f6:f3 ]
    fffff8030c15b9c0-fffff8030c15b9c2  3 bytes - nt!MmMapLockedPagesSpecifyCache+1a0 (+0x9a)
    [ 40 fb f6:c0 f9 f3 ]
    fffff8030c1759fb-fffff8030c1759fc  2 bytes - nt!MiCoalesceFreePages+3eb (+0x1a03b)
    [ 80 fa:00 81 ]
    fffff8030c1a004d-fffff8030c1a004e  2 bytes - nt!MiPurgeZeroList+6d (+0x2a652)
    [ 80 fa:00 81 ]
[COLOR=#ff0000]19 errors[/COLOR] : !nt (fffff8030c1371d2-fffff8030c1a004e)

MODULE_NAME: [COLOR=#ff0000]memory_corruption[/COLOR]

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffe101bc5cc7d0 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2017-01-15T19:51:08.000Z

OSBUILD:  14393

OSSERVICEPACK:  693

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-12-21 07:50:57

BUILDDATESTAMP_STR:  161220-1747

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 126a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption

outdated AsIO AsIO.sys & not needed also in the System, driverdate 2012!
Asus Utilities, uninstall.

memtest should run
Memtest86+ - Advanced Memory Diagnostic Tool
run it several hours, 10 different tests take ~ 4 hours or more (overnight job)
 
MichaelB said:
outdated AsIO AsIO.sys & not needed also in the System, driverdate 2012!
Asus Utilities, uninstall.

memtest should run
Memtest86+ - Advanced Memory Diagnostic Tool
run it several hours, 10 different tests take ~ 4 hours or more (overnight job)
Click to expand...

Thanks for getting back to me!

Regarding your first line, "outdated AsIO AsIO.sys & not needed also in the System, driverdate 2012!", where do I go to get the updated versions? Do I just need to download the latest bits from here: http://www.asus.com/uk/Motherboards/MAXIMUS_VII_RANGER/HelpDesk_Download/

I've run MemTest86+ for 4 passes and everything was fine, should I run it for much longer then?
 
Hi ByteSlinger. :welcome:

There is indeed a newer BIOS: 3003 2015/11/23
Now you've got 1104, 16/07/2014.

What can you try before updating bios (that could be risky) and drivers?
1) Load optimized defaults (in your bios) and check if the problem reappears.
2) Try to switch the RAM sticks to the black slots (although the red slots are recommended) and check if the problem reappears.

I can't check the other drivers, see: MAXIMUS VII RANGER | Motherboards | ASUS Global
You have got a bios usb flashback port: check carefully your manual before updating the BIOS.
There are also other methods (chapter 2.2 and 3.11).
 
xilolee said:
Hi ByteSlinger. :welcome:

There is indeed a newer BIOS: 3003 2015/11/23
Now you've got 1104, 16/07/2014.

What can you try before updating bios (that could be risky) and drivers?
1) Load optimized defaults (in your bios) and check if the problem reappears.
2) Try to switch the RAM sticks to the black slots (although the red slots are recommended) and check if the problem reappears.

I can't check the other drivers, see: MAXIMUS VII RANGER | Motherboards | ASUS Global
You have got a bios usb flashback port: check carefully your manual before updating the BIOS.
There are also other methods (chapter 2.2 and 3.11).
Click to expand...

Thanks very much for the tips. I'll try loading optimised defaults in the bios and see what happens.
Failing that I will try swapping RAM but if that's the solution then I guess I'm going to need to buy a new Mobo as I'd like to add more RAM soon.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top