Windows 10: bsod caused by pci.sys?

Discus and support bsod caused by pci.sys? in Windows 10 BSOD Crashes and Debugging to solve the problem; 0: kd> !analyze -v********************************************************************************... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ProtoFreeze, Aug 25, 2020.

  1. PROTOFREEZE
    ProtoFreeze Win User

    bsod caused by pci.sys?


    0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_INTERNAL_ERROR 122Arguments:Arg1: 000000000000000aArg2: 0000000000000004Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5187 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-6DVTHCV Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 16460 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 122BUGCHECK_P1: aBUGCHECK_P2: 4BUGCHECK_P3: 0BUGCHECK_P4: 0BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: Discord.exeSTACK_TEXT: fffff803`60217d58 fffff803`5a940f3c : 00000000`00000122 00000000`0000000a 00000000`00000004 00000000`00000000 : nt!KeBugCheckExfffff803`60217d60 fffff803`5ddde884 : 00000000`00000001 00000000`00000001 ffff9b88`ec3bc1b0 ffff9b88`ec40b010 : nt!WheaReportHwError+0x21cfffff803`60217e20 fffff803`5dddf002 : ffffc280`bebafb40 fffff803`60217ec0 ffffc280`bebafbf0 000275f2`543f7e6d : pci!ExpressRootPortAerInterruptRoutine+0x270fffff803`60217e80 fffff803`5dddf0b9 : ffffc280`bebafb40 00000000`006ba000 fffff803`60217fb0 00000000`00000f32 : pci!ExpressRootPortInterruptRoutine+0x22fffff803`60217ee0 fffff803`5a657921 : 00000000`00000000 ffff9b88`ea770000 00000000`00000286 fffff803`00000002 : pci!ExpressRootPortMessageRoutine+0x9fffff803`60217f10 fffff803`5a62cc75 : fffff803`5dddf0b0 00000000`00005001 fffff803`60217fc0 00000000`00000008 : nt!KiInterruptMessageDispatch+0x11fffff803`60217f40 fffff803`5a7c3b9f : fffff980`289cf8e0 ffffc280`bebafb40 00000000`006ba000 ffffc280`bebafb40 : nt!KiCallInterruptServiceRoutine+0xa5fffff803`60217f90 fffff803`5a7c3e67 : 00000000`68cf416c fffff980`289cf8e0 ffffc280`bebafb40 ffff9b89`07115080 : nt!KiInterruptSubDispatch+0x11ffffff980`289cf860 fffff803`5a7c8a21 : 00000000`1edf80c0 fffff803`5a7c3ee1 00000000`68cf416c fffff980`289cfa80 : nt!KiInterruptDispatch+0x37fffff980`289cf9f0 fffff803`5a7c3ee1 : 00000000`68cf416c fffff980`289cfa80 ffffc280`bebafb40 00000000`00000000 : nt!KiDpcInterruptBypass+0x11fffff980`289cfa00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1SYMBOL_NAME: pci!ExpressRootPortAerInterruptRoutine+270MODULE_NAME: pciIMAGE_NAME: pci.sysIMAGE_VERSION: 10.0.18362.752STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 270FAILURE_BUCKET_ID: 0x122_NOERRORRECORD_PCIe_pci!ExpressRootPortAerInterruptRoutineOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {96e34f7a-17c3-823a-35a1-3be37aa47cd0}Followup: MachineOwner---------0: kd> lmvm pciBrowse full module liststart end module namefffff803`5ddc0000 fffff803`5de2f000 pci pdb symbols C:\ProgramData\Dbg\sym\pci.pdb\888F70FEEF955EE489C2976F40F6178C1\pci.pdb Loaded symbol image file: pci.sys Mapped memory image file: C:\ProgramData\Dbg\sym\pci.sys\1D5E3C2E6f000\pci.sys Image path: \SystemRoot\System32\drivers\pci.sys Image name: pci.sys Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 1D5E3C2E This is a reproducible build file hash, not a timestamp CheckSum: 0006CDDD ImageSize: 0006F000 File version: 10.0.18362.752 Product version: 10.0.18362.752 File flags: 0 Mask 3F File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: pci.sys OriginalFilename: pci.sys ProductVersion: 10.0.18362.752 FileVersion: 10.0.18362.752 WinBuild.160101.0800 FileDescription: NT Plug and Play PCI Enumerator LegalCopyright: © Microsoft Corporation. All rights reserved.

    :)
     
    ProtoFreeze, Aug 25, 2020
    #1
  2. HORUS-3-ECHO
    Horus-3-Echo Win User

    QCAMAIN1.SYS CAUSING BSOD

    This was probably caused by the following module:
    qcamain1.sys (Qcamain10x64+0x108678)

    Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

    Error: CUSTOM_ERROR

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

    Google query: qcamain1.sys CUSTOM_ERROR

    Using WhoCrashed I found this thread: https://answers.microsoft.com/en-us...37-error/3a99eb3e-3ba5-4937-a908-d4c478e266cd however without
    solution, locked.

    I did get BSOD almost everytime I moved the laptop.

    This worked for me:

    unscrew wifi module, push a little into the socket. Screw in. DONE
     
    Horus-3-Echo, Aug 25, 2020
    #2
  3. CINDRIX
    Cindrix Win User
    BSOD "IRQL_NOT_LESS_OR_EQUAL" caused by L1C63x64.sys Windows 10

    I am getting BSOD at iregular intervals with the same error code "IRQL_NOT_LESS_OR_EQUAL" caused by L1C63x64.sys, which is a driver for

    "Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30)".

    this seems to be a recurring theme with this driver but i havent been able to find my hardware ids in the other threads.

    hardware ids

    PCI\VEN_1969&DEV_10A1&SUBSYS_10A11849&REV_10

    PCI\VEN_1969&DEV_10A1&SUBSYS_10A11849

    PCI\VEN_1969&DEV_10A1&CC_020000

    PCI\VEN_1969&DEV_10A1&CC_0200

    Current driver version in my desktop is 2.1.0.21 and was published 7.16.2013. ive tried to do an automatic update to the driver, run windows update, tried to find a newer driver on the motherboards website, and other online sources, but havent been able
    to find something specific to this (can confirm from motherboard manual that part is the ar8171)

    thanks in advance for any help
     
    Cindrix, Aug 25, 2020
    #3
  4. INTERESTINGKID005140
    interestingkid005140 Win User

    bsod caused by pci.sys?

    wdf01000.sys and ntoskrnl.exe BSOD

    I'm on Windows 10, 64bit

    Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

    So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

    Have no idea which driver is causing them

    Please help!

    Here are my list of drivers and system info: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
     
    interestingkid005140, Aug 25, 2020
    #4
Thema:

bsod caused by pci.sys?

Loading...

  1. bsod caused by pci.sys? - Similar Threads - bsod caused pci

  2. BSOD caused by rtwlane601.sys?

    in Windows 10 Gaming
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  3. BSOD caused by rtwlane601.sys?

    in Windows 10 Software and Apps
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  4. BSOD caused by watchdog.sys and dxgmms2.sys

    in Windows 10 Software and Apps
    BSOD caused by watchdog.sys and dxgmms2.sys: Greetings, fellow Windows users!Yesterday, my computer had its BSOD while I'm using Adobe Premiere which was apparently caused by watchdog.sys and dxgmms2.sys.Here is a link to the dmp file: https://1drv.ms/u/s!AmT-xQXftxFWgiKU88vH7tRulzda?e=33kqdQThanks for any further help...

  5. BSOD caused by dxgmms2.sys and watchdog.sys

    in Windows 10 Software and Apps
    BSOD caused by dxgmms2.sys and watchdog.sys: I've tried reverting graphics drivers, windows updates, updating BIOS, resetting windows and other recommended methods such as chkdsk and DISM. I would like some confirmation on my issue being potentially video card related. Another pair of eyes/insight is the goal of this...

  6. BSOD caused by netwtw10.sys

    in Windows 10 Drivers and Hardware
    BSOD caused by netwtw10.sys: From a couple of days ago my machine has been frequently BSOD and showing the error to be caused by netwtw10.sys. I have attempted to reinstall network drivers, reset machine with content, reset to factory and the issue has persisted through all the changes I made. In...

  7. QCAMAIN1.SYS CAUSING BSOD

    in Windows 10 BSOD Crashes and Debugging
    QCAMAIN1.SYS CAUSING BSOD: This was probably caused by the following module: qcamain1.sys Qcamain10x64+0x108678 Bugcheck code: 0x1D3 0x333, 0x0, 0x0, 0x0 Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for...

  8. BSOD caused by Dot4.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by Dot4.sys: I have a BSOD problem caused by Dot4.sys very often but I have no idea what is causing it. SYSTEM_SERVICE_EXCEPTION Dot4.sys+e23f IEEE-1284.4-1999 Driver Windows (R) Win 7 DDK driver Windows (R) Win 7 DDK provider 6.1.7600.16385 built by: WinDDK x64 ntoskrnl.exe+1aab90

  9. BSOD caused by QCamain10x64.sys and IntelHaxm.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by QCamain10x64.sys and IntelHaxm.sys: My laptop crashed with STOP code DEVICE_IRQL_NOT_LESS_OR_EQUAL, stating that QCamain10x64.sys had failed, which according to Google, is the driver of my laptop's wireless adapter. Just to make sure before attempting to reinstall the driver via device manager, I saw this wiki...

  10. Random BSODs caused by cm11264.sys.

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs caused by cm11264.sys.: Hi, i recently started having issues with my computer crashing. I will provide the dump files. I've looked up what cm11264.sys was connected to and it was my pair of Sennheiser 363d. I have since then tried multiple driver versions, and now have switched to a different port....