Various errors! The Saga Continues!

[KeyboardDemon]

Hopefully this brings an end to the saga.

I decided on using the links provided by aramil as that looked like less work than the suggestion offered by shaithis, though I'm grateful for all suggestions and the time people have taken to help me this far.

Now for the arduous task of playing many rounds of BF4 to see if I still have stability issues. Uhh! It's a tough job, but somebody has to do it!



***edit*** OCCT used to encouter an error and stop testing on Linpack after about 5 minutes, it's now been running for close to 10 with no errors and I'm using my PC to post this message while it runs. I think that's a good thing.

[aramil]

I know some boards are picky about upgrading the IME if the BIOS is below a certain point....and while you may have the latest BIOS, you probably don't have all the newest modules in it.

Might be worth upgrading the various parts using UEFI BIOS Updater (UBU)

It's a good tool to have, personally I like to do it manually (helps with the understanding of the how why what etc.)

Hopefully this brings an end to the saga.

I decided on using the links provided by aramil as that looked like less work than the suggestion offered by shaithis, though I'm grateful for all suggestions and the time people have taken to help me this far.

Now for the arduous task of playing many rounds of BF4 to see if I still have stability issues. Uhh! It's a tough job, but somebody has to do it!



***edit*** OCCT used to encouter an error and stop testing on Linpack after about 5 minutes, it's now been running for close to 10 with no errors and I'm using my PC to post this message while it runs. I think that's a good thing.

Hopefully

If not i can post up a reworked 2104 bios with fully up to date modules etc (as Shaithis stated, although in testing i have not noticed any issues so far with vanilla or updated 2104 with ME 8.1.52.***)

[Bonebreaker777]

Man, seems to me like a right pain in the back side. But I would love to 'have it' and sort it out (eventually).

[KeyboardDemon]

Man, seems to me like a right pain in the back side. But I would love to 'have it' and sort it out (eventually).

It was a complete royal PITA, but it has to be said that I learnt so much through this experience. I really hope it is sorted now. I still need to stop the driver verifier from running, I think that just means issuing a reset instruction through an elevated command prompt.

[satrow]

To turn Driver Verifier off - verifier /reset then re-boot

Is that easy enough?

[KeyboardDemon]

Is that easy enough?

Excellent, it was simply reset through an elevated prompt, but what's not so excellent is I had another Blue Screen this morning.

I got this minidump for it, but have to go to work now. I can't do much now till maybe early next week.

[satrow]

And the dump was Verified, indicating that DV was (still?) active with the 'faulting' driver being the Wdf01000.sys which is the WDF Dynamic - Kernel Mode Driver Framework Runtime. I very much doubt that it's the true cause of the crash.

I think it's best to ignore this one, check through this and ensure DV is not running: https://msdn.microsoft.com/en-us/Lib...=vs.85%29.aspx

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80323bcc929, ffffd0002262ed10, 0}

Probably caused by : Wdf01000.sys ( Wdf01000!FxDevice::DispatchWithLock+2a5 )

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

0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80323bcc929, Address of the instruction which caused the bugcheck
Arg3: ffffd0002262ed10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8]

CONTEXT: ffffd0002262ed10 -- (.cxr 0xffffd0002262ed10;r)
rax=00000002a92c0002 rbx=ffffe000a7f4caf0 rcx=ffffe000a9c11ec0
rdx=fdffe000ac080ac0 rsi=0000000000000000 rdi=ffffe000a9b05440
rip=fffff80323bcc929 rsp=ffffd0002262f740 rbp=ffffd0002262f7c9
r8=fdffe000ac080ac0 r9=ffffe000a7f4cf68 r10=ffffe000a9c11ec0
r11=ffffe000ab216b00 r12=0000000000000000 r13=ffffe000a9c11f48
r14=ffffe000a9be7530 r15=ffffe000a9c11ec0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault:
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8] ds:002b:fdffe000`ac080ac0=????????????????
Last set context:
rax=00000002a92c0002 rbx=ffffe000a7f4caf0 rcx=ffffe000a9c11ec0
rdx=fdffe000ac080ac0 rsi=0000000000000000 rdi=ffffe000a9b05440
rip=fffff80323bcc929 rsp=ffffd0002262f740 rbp=ffffd0002262f7c9
r8=fdffe000ac080ac0 r9=ffffe000a7f4cf68 r10=ffffe000a9c11ec0
r11=ffffe000ab216b00 r12=0000000000000000 r13=ffffe000a9c11f48
r14=ffffe000a9be7530 r15=ffffe000a9c11ec0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault:
fffff803`23bcc929 498b08 mov rcx,qword ptr [r8] ds:002b:fdffe000`ac080ac0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x3B

PROCESS_NAME: adventure-capi

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff8012ca5e4e5 to fffff80323bcc929

STACK_TEXT:
ffffd000`2262f740 fffff801`2ca5e4e5 : 00000000`00000080 00000000`00000801 00000000`00000508 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffd000`2262f750 fffff803`240ee911 : ffffe000`ab27cfe0 00000000`00000000 ffffe000`a9c11d00 ffffe000`ac00a801 : Wdf01000!FxDevice::DispatchWithLock+0x2a5
ffffd000`2262f830 fffff803`23e9a77f : 00000000`00000001 ffffd000`2262fb80 ffffe000`a7f4caf0 ffffe000`ab27cf40 : nt!IovCallDriver+0x3cd
ffffd000`2262f880 fffff803`23e99d22 : 00000000`00000000 fffff803`23e14915 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa4f
ffffd000`2262fa20 fffff803`23bd14b3 : 00000000`00000001 fffff803`23b3746d ffffe000`ab4c2080 ffffd000`2262fb80 : nt!NtDeviceIoControlFile+0x56
ffffd000`2262fa90 00000000`77212352 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b4e948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77212352


FOLLOWUP_IP:
Wdf01000!FxDevice::DispatchWithLock+2a5
fffff801`2ca5e4e5 488bf8 mov rdi,rax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Wdf01000!FxDevice::DispatchWithLock+2a5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f850

IMAGE_VERSION: 1.13.9600.16384

STACK_COMMAND: .cxr 0xffffd0002262ed10 ; kb

BUCKET_ID_FUNC_OFFSET: 2a5

FAILURE_BUCKET_ID: 0x3B_VRF_Wdf01000!FxDevice::DispatchWithLock

BUCKET_ID: 0x3B_VRF_Wdf01000!FxDevice::DispatchWithLock

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_vrf_wdf01000!fxdevice::dispatchwithlock

FAILURE_ID_HASH: {348b091b-efa4-fbc2-9baf-d03d1166d7e2}

Followup: MachineOwner

[KeyboardDemon]

I haven't stopped DV yet, so I'll do that when I get home and keep testing from there.

[Jace007]

I blame the Russians they caused the Issue KD :S !

[KeyboardDemon]

I blame the Russians they caused the Issue KD :S !

They probably snuck in through my internet connection while I was playing on the US side in BF4, they're quite sneaky that way, either that or it was the Chinese.

[Jace007]

https://www.youtube.com/watch?v=dTcgaEfszTg Dam those BF4 Chinese sneaky ... I'm still playing BF3. any closer to your PC problem?

[KeyboardDemon]

https://www.youtube.com/watch?v=dTcgaEfszTg Dam those BF4 Chinese sneaky ... I'm still playing BF3. any closer to your PC problem?

Sorry to say no, not got any closer to fixing my problems. Still getting blue screens, not as frequent now but some weird poop all the same.

I found an app that's part of the Windows SDK that lets me read minidump files, when I get home I'll post some of the juicy highlights. lol.

I think I might have to raise a ticket for an RMA on the motherboard.

[aramil]

Last resort?

Fully updated 2104 sabertooth bios .CAP file http://d-h.st/uuZ

needs to be flashed via usb stick as per http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/

Acquire a USB Thumb Drive
Format the USB drive with a FAT32 file system, copy Cap file to usb

from powered off.

Refer to your user manual to make sure to us the USB port that support USB BIOS Flashback, and plug the USB storage device to the specific USB port. Then press the USB BIOS Flashback button for three/five seconds till the LED begins to blink, then release.

Wait till the LED stops blinking, indicating that BIOS flashing has been completed.

boot, reset bios, turn off.

Jumper reset bios,

Boot to bios (apply any setting you need)

save/reboot.

[KeyboardDemon]

This Z77ST.CAP file is 8192KB and the original Asus version is 8194KB so clearly they are different, do you know what changes have been made by any chance?

[aramil]

sorry header removed version (would not of flashed.)


usb flash version (correct size)
http://d-h.st/SIuX


before:


After

[KeyboardDemon]

sorry header removed version (would not of flashed.)

usb flash version (correct size)

Phew... good I thing I checked. I might not have bricked it, but I thought it would be good idea to see exactly what I'm installing and it looks like this correct file is a massive change, the Intel RST<e> ORMO and EFI SataDriver appear to have major revisions going from 11.x to 14.x, with another major revision further down the list for the EFI Intel Pro/1000 UNDI, which looks like it controls something networking related, everything else has had a minor revision update, very little appears to be unchanged, at least to my untrained eye.

I'll drop that in later, I have to go out at the moment.

BTW: How are you bringing up that BIOS information?