BSOD STOP D1 - pci.sys

I have been testing since my last Post, but I have had to perform a Restart many times in the intervening time frame (not for this problem), which I have noticed in the past tends to "reset" the BSOD D1 situation, temporarily.

I was scared to incur Murphy's wrath before this, but I WAS hopeful that the issue had gone, although it went against all logic.

Unfortunately not, however, as I have just had my first BSOD D1 since reinstalling the newest Nvidia Drivers, whilst playing one of the legacy games.

Hence, I will now proceed with the following Win7 Updates:-
- April 2015 Servicing Stack Update for Win7
- KB3125574 - Win7 SP1 Rollup Update [SP2]

I DO know that one of the above Updates DOES modify the pci.sys file, so this may be a positive as far as fixing the problem goes.

After the above Updates are installed, if I still have the problem, my only recourse is to run the "MS ACT - Appln Compat Toolkit" & see what this finds.

More later.

Last wednesday (10th), I attempted to install KB3020369, the Win7 April 2015 Servicing Stack Update, but received the error message of "The update is not applicable to your computer."
I then successfully managed to install KB3125574, the Win7 Convenience Rollup Update, sometimes referred to as SP2, although never by Microsoft.

I have been, and still am, testing to see if the BSOD error still exists.

KB3020369 was a prerequisite install for KB3125574, so I must have already had it installed.
Interestingly, KB3125574 included a list of files that were modified in the update and pci.sys was one of them, unfortunately, I already had a higher version that was listed in KB3125574.

My pci.sys version is:- 6.1.7601.24441, dated 19/Apr/19 @ 13:45:00.

The pci.sys version from KB3125574 is:- 6.1.7601.23403, Dated 25/Mar/16 @ 19:09

My version of the file is obviously much newer than this KB3125574 [SP2] version.

After my testing is finished, I have nothing else to try; I have exhausted all avenues as far as I am concerned.

The only desperation idea I have is to replace the newer pci.sys file with the older version from the KB3125574 [SP2] and see what happens.
But it is not usually a good idea, to go back to a MUCH older file version.


Any new comments or ideas would be most welcomed at this stage.
If anyone DOES have any ideas, I am all ears.

I have received the D1 5 times in the last 2 weeks, on one occasion twice in one day.
I only mentioned the one that was relevant, showing that it still existed.
I didn't want to bore you with all the others!

As you can see from the list below (a list only, no actual Dumps), the last one prior to the start of Feb was on the 20th of Jan, which is nearly a 2 week gap.


I used the 2015 Update Pkg instead of Windows Update because it was the most recent Pkg I could find.
Since Win7 lost all Support, I used WSUS Offline Update by Torsten Wittrock, to download all Updates I was possibly missing.
I did this either just before, or just after Support was pulled.
I also used the same S/W to Update my Office 2010.
I have found it very useful.

Prior to the loss of Win7 Support, I used to have Windows Update set to "Chk for updates but let me choose whether to install them", as many friends who auto-downloaded them had many issues with individual & problematic Win Updates over the years.
I also have the Recommended Updates box ticked.

I kept Win Updates on for a while, but got sick of hiding & refusing all the "Windows Malicious Software Removal Tool" (WMSRT) pkgs, which I don't use & have only ever used once or twice.
Since the Support was lost, I have not received ONE Update.
My KIS, MBAM, etc has always been good enough, w/o the need for these pkgs.
So, I turned Win Updates off & only turned it back on every 6 months or so.
Since the end of Support, I have only ever been notified of WMSRT pkgs.

I have turned it back on for the moment, with the settings I mentioned above, but with no Support for Win7, I don't really expect to be notified that there will EVER be any Updates, except the aforementioned WMSRT pkgs.

RECENT DUMPS
---
DMP-20210120-Jan
---
DMP-20210203-feb-#1
DMP-20210203-feb-#2
DMP-20210205-feb
DMP-20210209-feb
DMP-20210213-feb
---

FYI, I have just been notified by Win Update of KB4536952, a Jan 2020 Servicing Stack Update!
Win Update took its time, as it has been turned back on for over 30 mins & I performed an initial Update check before I turned it back on.
Timing is everything!

I checked out Update KB4536952 (Jan 2020 Servicing Stack Update), which led me to a total of 4 Win7 Updates.

In addition to the above KB4536952, one of them was a much more recent Servicing Stack Update, dated Dec 2020.

This is:-
- KB4592510 - Win7 x64 Dec 2020 Servcg Stack Update.

There were 2 Prerequisite Updates for this Update, namely:-
1 - KB4474419 - SHA-2 Signing Support Security Update.
2 - KB4490628 - Win7 x64 Mar 2019 Servcg Stack Update.

Consequently, I attempted to install the above 2 KB Updates, only to receive a message stating they were both "ALREADY INSTALLED".

I then successfully installed:-
- KB4536952 - Win7 x64 Jan 2020 Servcg Stack Update.

After completion, I Restarted the PC.

After the Restart, I then successfully installed:-
- KB4592510 - Win7 x64 Dec 2020 Servcg Stack Update.

Again, after completion, I Restarted the PC.

I shall now see what happens over the next few days & I will also be watching Windows Update with interest.
The notification re: KB4536952 (Win7 x64 Jan 2020 Servcg Stack Update) was the first REAL notification I have seen in probably the last 12 months.
I don't really expect to see another non-WMSRT now, for at least 12 months, if ever.

I will get Testing and get back to you.

Unfortunately, I have to announce that the BSOD D1 problem still exists.


I will now have to delve into the 2x BSOD E7 I received when I ran the Driver Verifier.
This would suggest that a Driver is the definitive offender and is either corrupted or screwed up in some way.
Obviously I suspect pci.sys, but as it is a System file, I have no idea at this stage as to how I can possibly replace it.
Obviously, it is an importatn Driver.
None of the Ein7 KB Updates I have done have updated the pci.sys driver & my version # is higher than in those KB Updates.


I will post initial info when I have studied the E7 data.


If anyone can help with the E7 Dumps, I will post them too, if requested.

Apparently I made a slight error in my personal D1 Notes.
It would appear that the Driver Verifier did not die with an E7, but rather with an E6.
It would also appear that. for some unkown reason, I have not saved these particular Dumps.

Apparently, a BSOD E6 is "DRIVER_VERIFIER_DMA_VIOLATION"

Consequently, this means that I will have to run Driver Verifier again & record all the details of the BSODs that subsequently occur, as well as the Dumps.
As this previously crashed the PC every time, it may take a little while.


In the meantime, below is a table of the extracted more important data from all the D1 Dumps, obtained using the excellent Nirsoft BlueScreenView.
Items in braces ("{}") are extra & alternate values for the field.
Where there is a "{none} noted, it is probably due to the Dump not being a normal Dump, but being a Dump entitled "MEMORY.DMP".
ONLY these type of dumps have missing fields (I.E. "{none}").


DUMP TECH INFO
---
BUG CHECK STRING = DRIVER_IRQL_NOT_LESS_OR_EQUAL [ALWAYS]
---
BUG CHECK CODE = 0x000000d1 [ALWAYS]
---
PARM 1 = 00000000`00000064 [ALWAYS]
---
PARM 2 = 00000000`0000000b [ALWAYS]
---
PARM 3 = 00000000`00000001 [ALWAYS]
---
PARM 4 = fffff880`0100ce9b
{fffff880`015a5e9b}
{fffff880`00e76e9b}
{fffff880`01076e9b}
{fffff880`0101fe9b}
---
CAUSED BY DRIVER = pci.sys
{none}
---
CAUSED BY ADDRESS = pci.sys+ce9b
{none}
---
CRASH ADDR = ntoskrnl.exe+93ea0
{none}
{exe+93ca0}
{exe+93ba0}
{exe+939a0}
---