[SOLVED] BSOD at lock screen on startup - Windows 8.1 x64

[Trev]

Hi, I have relatively recently built a new computer, and it seemed to be settling, until I noticed I was getting BSODs at the lock screen.

It seems to happen every start-up, if left at the lock screen for long enough (Usually a couple of minutes). If I log in as soon as the lock screen comes up, it logs in fine, no BSOD. I can then lock, and leave the computer, do anything. It's only on the first lock screen.

Following a guide elsewhere I ran sfc /scannow in cmd, Which lead me to this thread: https://www.sysnative.com/forums/wi...prncacla-inf-corruptions-windows-8-8-1-a.html.
After running SFCFix, which seemed to do the first method suggested in the thread, as seen in the log file.
I am at a loss, and this forum seemed helpful.

I attempted to attach one of the BSOD dmp files, the log from SFC, and SFCFix, however the file size limits only allowed the SFCFix file to be attached?
Help would be greatly appreciated.

Sorry if this is posted in the wrong place.

 

[Trev]

I found the BSOD posting instructions, so figured I would follow those too.

I have attached the output from Windows7_Vista_jcgriff2.
The screenshot, is the output of running perfmon /report in an admin cmd.

My Specs are:
Desktop.
Running Windows 8.1 64bit, that I originally installed from a full retail version.
The system is now about 2 months old, as is the OS.

CPU: i7 - 4770
GPU: Gainward GTX760, and a Gigabyte GT 610
Mobo: Gigabyte z87-HD3
PSU: Seasonic G-650W

System Manufacturer: Custom Built.

 

[Patrick]

Hi,

I've moved your thread to the proper forum as this is a BSOD problem and not a Windows Update problem.

All of the attached DMP files are of the DPC_WATCHDOG_VIOLATION (133) bug check.

This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

7: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd001`e1fb1c98 fffff802`949adad6 nt!KeBugCheckEx
01 ffffd001`e1fb1ca0 fffff802`948cdf85 nt! ?? ::FNODOBFM::`string'+0x2f626
02 ffffd001`e1fb1d30 fffff802`94fab7b5 nt!KeClockInterruptNotify+0x95
03 ffffd001`e1fb1f40 fffff802`948e9363 hal!HalpTimerClockIpiRoutine+0x15
04 ffffd001`e1fb1f70 fffff802`9496f42a nt!KiCallInterruptServiceRoutine+0xa3
05 ffffd001`e1fb1fb0 fffff802`9496f80f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 ffffd001`e1faa740 fffff802`948e9663 nt!KiInterruptDispatchLBControl+0x11f
07 ffffd001`e1faa8d0 fffff802`948e9622 nt!KxWaitForSpinLockAndAcquire+0x23
08 ffffd001`e1faa900 fffff801`9acd1059 nt!KeAcquireSpinLockRaiseToDpc+0x32
09 ffffd001`e1faa930 fffff801`9abc42fa tcpip!TcpEnqueueTcbSend+0x79
0a ffffd001`e1faaa30 fffff801`9abc478f NETIO!StreamInjectRequestsToStack+0x24a
0b ffffd001`e1faab10 fffff801`9abc4859 NETIO!StreamPermitDataHelper+0x5f
0c ffffd001`e1faab40 fffff802`948741e0 NETIO!StreamPermitRemoveDataDpc+0x81
0d ffffd001`e1faabb0 fffff802`948733fb nt!KiExecuteAllDpcs+0x1b0
0e ffffd001`e1faad00 fffff802`949710d5 nt!KiRetireDpcList+0xdb
0f ffffd001`e1faafb0 fffff802`94970ed9 nt!KxRetireDpcList+0x5
10 ffffd001`e406d190 00000000`00000000 nt!KiDispatchInterruptContinue

7: kd> ub fffff801`9acd1059
tcpip!TcpEnqueueTcbSend+0x4a:
fffff801`9acd102a 48899c2410010000 mov     qword ptr [rsp+110h],rbx
fffff801`9acd1032 4889bc24d0000000 mov     qword ptr [rsp+0D0h],rdi
fffff801`9acd103a 4c89b424c0000000 mov     qword ptr [rsp+0C0h],r14
fffff801`9acd1042 4d85ed          test    r13,r13
fffff801`9acd1045 0f85a53f0b00    [COLOR=#ff0000]jne[/COLOR]     [COLOR=#ff0000]tcpip!TcpEnqueueTcbSend+0xb4010 (fffff801`9ad84ff0)[/COLOR]
fffff801`9acd104b 498bcf          mov     rcx,r15
fffff801`9acd104e 4c8d6c2462      lea     r13,[rsp+62h]
fffff801`9acd1053 ff1527b31600    [COLOR=#4b0082]call    qword ptr [tcpip!_imp_KeAcquireSpinLockRaiseToDpc (fffff801`9ae3c380)][/COLOR]

It looks like the Microsoft TCP/IP driver and an enqueue routine is in a loop/holding onto a lock. Something 3rd party is very likely causing NETBIOS conflicts.

---

1. Remove and replace AVG with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing NETBIOS conflicts:

AVG removal - http://www.avg.com/us-en/utilities

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

2. RTCore64.sys is listed and loaded which is RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Windows 7, 8, and 8.1). Please uninstall ASAP! If you were using MSI to control your fans, there are many working alternatives such as SpeedFan.

3. Do you have either - Razer GameBooster, Corsair Link, or RealTemp installed?

Regards,

Patrick

 

[Trev]

Hi, and thanks for the help.

I removed AVG.
After doing that, and stopping AB from starting with windows it seems to have fixed the issue.

I am not confident in relying on Windows Defender. I guess I'll look into using a different AV.

I use RealTemp, though it doesn't get installed.

Thanks,
Trev.

 

[Patrick]

Glad to hear it stopped, thanks for the update.

I've marked it as solved.

I don't blame you for feeling unprotected, it's your system and your choice. I recommend ESET, and I'd say away from avast!, AVG, Norton, and McAfee. I have gripes with Kaspersky, especially in 8.1 (causes pool corruption quite often on 8.1).

Regards,

Patrick