Windows 10: L1C62x64.sys [0xD1] While Streaming with OBS

DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1

I'm tired, I've posted stuff before, somewhere. I've eben working all morning, and trying to uncover it on my own, I usually do.

I honestly think it's hardware. It could be related to the Scarlet UAC2Audio, but that's because, well a hunch. I've never had the blue screen ever occur without OBS running in some form, or shape while encoding. I suspect it's cpu related, in some form. That maybe crunching resources.

I honestly hope its software, I haven't tried reinstalling anything, I'm not a professional, sure I troubleshooted things. I found out the offender being Atheros suppoedly, I'm suspecting it isn't the direct offender, it also could be something unknown.

This computer was built in 2014, I honestly think it's about time for an upgrade. But who knows. I really dont want to take that route, I'd like to be able to solve the issue.

What I have noticed is, while casually playing things that were super super low resource usage, I played a lot of FF9, and FF8 steam edition, no problems during that frame. The BSOD had ocurred before hand, it was just rare. I do notice it frequently happening whenever I play extremely more aggressive things. More recently A PSP emulator, cause my psp battery sucks ass. (and not really convenient for streaming.)

Which I saw crashes very far apart, you'll see the older logs are nearly several days apart. There should be more, but I suspect windows may have obliterated them for being old. lol

during gameplay of a recently released game PREY I found it happened very quickly. as I suspected increased PC Stress. I rarely came across the issue even for games like Tomb Raider, JC2, any other PC Game I played. I suspect its tied mainly to as I said before a lack of pc resources, of some sort. I don't experiencer chugging, or even consume trhat much It seems it only happens while using OBS. So either there's a defect in the hardware while under stress, or something

i cant speculate. lol Someone give me better insight.

:)

 

Open Broadcaster Software suffers from recent update

The streaming community was affected by the 9/1/2016 Windows update KB3176938. After much trial and error, it has come to the attention of the Open Broadcaster Software (OBS) community that the aforementioned update has caused the streaming software to shut
down unexpectedly soon after a recording or stream begins. The error code in the OBS logs shows various D3D11 error codes. Many users took to the forums requesting support from the developers, but soon realized OBS was not the problem. Several users uninstalled
update KB3176938 and reported positive results.

I believe this update caused a problem with OBS, and am asking that the developers seek out a solution for future updates.

 

BSOD - Driver Power State Failure

Hi,

There are two drivers referenced in the crash, iacamera64.sys and igdkmd64.sys :

BUCKET_ID: 0x9F_3_iacamera64_IMAGE_igdkmd64.sys

The iacamera64.sys is an Intel camera drive and the igdkmd64.sys is an Intel video driver.

Try updating both of these driver:

HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

 

L1C62x64.sys is the driver for your Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20).

What is the version of your driver and is this one compatible with windows 10.

 

[2.1.0.21] is the version, and its not explicitly stated to be windows 10 compatible, I did not manually install these drivers either. Windows 10 did that when I reformatted it sometime after upgrading. Due to another driver issue, which got resolved.

 

So, It's been a few months and I dont know if I mentioned it. I narrowed it down to a temperature issue.

https://i.imgur.com/Aqz5BTI.png

nothing really has changed. I believe its hardware related. I've tried to stress test the cpu, and I've used far more crippling things with no repeat.

But I'm guessing a component on the motherboard is getting hot enough to crash the system. Since these crashes are exceptionally rare, unless I specifically, want them to happen , they happen. they only ever happen when I am uploading a great deal of data while under cpu load. Only when the system is uploading consistently a 0.5Mb/s upload for a long period of time while under load.

On really hot days I've noticed it happens within an hour if it takes that long, but the cpu also has to be under load. Likely to increase the temperature as well. I've had the mind to wonder if I should replace the mobo, and the cpu and just go ahead and upgrade.

But there are some other concerns as well. I am not a professional at debugging things. So I can only make speculation.

 

The last minidmp in the zip was from 5/11/2017.
Please post an updated zip: BSOD - Posting Instructions - Windows 10 Forums

 

Attachment 142477

 

There were 11 bsod mini dump files since 5/11/2017

Code: BugCheck D1, {0, 2, 0, fffff80b167e6c9b}*** WARNING: Unable to verify timestamp for L1C62x64.sys*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sysProbably caused by : L1C62x64.sys ( L1C62x64+6c9b )[/quote] L1C62x64.sys Atheros NIC driver Official site: Drivers | Qualcomm
Unofficial site: http://www.atheros.cz
Code: L1C NDIS Miniport Driver f NDIS Miniport Driver f Kernel Manual Running OK TRUE FALSE 0 102,400 0 7/16/2013 2:56:44 AM C:\WINDOWS\system32\drivers\L1C62x64.sys 4,096[/quote] Code: The IO operation at logical block address 0x2000 for Disk 2 (PDO name: \Device\0000015d) failed due to a hardware error.[/quote]
Code: Event[82]: Log Name: System Source: Service Control Manager Date: 2017-04-28T23:44:49.995 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AstralGate Description: A service was installed in the system.Service Name: NDIS Miniport Driver for Qualcomm Atheros AR81xx PCI-E Ethernet ControllerService File Name: \SystemRoot\System32\drivers\L1C62x64.sysService Type: kernel mode driverService Start Type: demand startService Account:[/quote]

All minidump displayed the same misbehaving driver after and before the last post on 5/11/2017.

Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread



5) uninstall/reinstall: Black desert
6) uninstall/reinstall: Dead cells
7) disable Windows from updating non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials
7) Uninstall: Atheros NIC driver
Install replacement driver: Select Qualcomm Atheros network driver
8) run one of the SMART tests on your drives:
CrystalDiskInfo - Software - Crystal Dew World: CrystalDiskMark - Software - Crystal Dew World
HD Tune: HD Tune website
Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring

 

Before I post while things do their stuff. I'll humour you, and incase I actually missed something. Hypothetically speaking what is my replacement driver for windows 10? Like what would I use in that link I dont know anything about my onboard nic stuff, and all that.

So whjich driver in the list do I use?

 

Version 1703 (OS Build 15063.413)

Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>winver C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 798976 file records processed. File verification completed. 15058 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 1038500 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 119763 data files processed. CHKDSK is verifying Usn Journal... 35072736 USN bytes processed. Usn Journal verification completed. Windows has found problems that must be fixed offline. Please run "chkdsk /spotfix" to fix the issues. 124799999 KB total disk space. 114713532 KB in 526477 files. 298648 KB in 119764 indexes. 0 KB in bad sectors. 914163 KB in use by the system. 65536 KB occupied by the log file. 8873656 KB available on disk. 4096 bytes in each allocation unit. 31199999 total allocation units on disk. 2218414 allocation units available on disk. C:\WINDOWS\system32>[/quote]



Edit: So I was reviewing some of the data in the Event Viewer and found something really interesting being reported every 1 second for a very long time.

Code: Failed to connect to the driver: -2147024894, retrying in 1000 milliseconds[/quote]
No idea if it's related, but it's definitely not normal, I'm still googling tho.

Edit2: the above message about the driver, I've found to be associated with DropBox, I don't think it's cause of anything. Although seems unhealthy. I'd disregard the little block from my first edit.
​

 

Make sure that you are all backed up with Macrium.
Please create a restore point.

Open administrative command prompt and copy and paste this command: chkdsk /spotfix

Please report results into the thread.


Open administrative command prompt and type or copy and paste: chkdsk /x /r
This may take many hours to run. Plan to run overnight.
Please post the result into the thread:
How to find chkdsk results in Windows 10 - Winaero uses 26226 find

 

Code: Checking file system on C:The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. Stage 1: Examining basic file system structure ... 798976 file records processed. File verification completed. 15057 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... The sparse flag in standard information attribute in file 0x26e40 should not be set. Correcting sparse file record segment 159296. The sparse flag in standard information attribute in file 0x37db7 should not be set. Correcting sparse file record segment 228791. The sparse flag in standard information attribute in file 0x4954b should not be set. Correcting sparse file record segment 300363. 1038510 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 6537 unused index entries from index $SII of file 0x9. Cleaning up 6537 unused index entries from index $SDH of file 0x9. Cleaning up 6537 unused security descriptors. Security descriptor verification completed. 119768 data files processed. CHKDSK is verifying Usn Journal... 37408152 USN bytes processed. Usn Journal verification completed. Windows has made corrections to the file system. No further action is required. 124799999 KB total disk space. 114449900 KB in 526310 files. 298728 KB in 119769 indexes. 0 KB in bad sectors. 916719 KB in use by the system. 65536 KB occupied by the log file. 9134652 KB available on disk. 4096 bytes in each allocation unit. 31199999 total allocation units on disk. 2283663 allocation units available on disk. Internal Info: 00 31 0c 00 99 da 09 00 b0 6a 11 00 00 00 00 00 .1.......j...... 27 0a 00 00 de 6e 00 00 00 00 00 00 00 00 00 00 '....n.......... Windows has finished checking your disk. Please wait while your computer restarts.[/quote] I'm sure as hell positive that you didnt have a link for the results. In anycase 26226 was not correct, as it linked prior to the previous data, identically linked earlier. This one is related to as I was peering for the specific timestamp when the computer had turned off. So It's the only thing I could find during that time. Unless its in another area, But I did give it a look.

I didnt find anything else using the above link. (Which wasnt there until I refreshed.. I feel like? Oh well)

Either way, the results are there. Ill edit in a second.

 

There are different methods to see the results from chkdsk in the eventvwr after boot:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

 

Yes, sorry, I already posted the logs above. I may have poorly communicated, I am not good communicating with people.