BSOD UNEXPECTED_KERNEL_MODE_TRAP (7f)

First thing you need to do is update your BIOS which is at MQ96510J.86A.1715 to MQ96510J.86A.1761

You can see from the release note that there are hell lot of updates


Second update the Chipset driver... as you haven't installed the PCI Communication driver

Thirdly download the 32bit Vista version of your Lan drivers from here and reinstall the it.

Fourthly reboot your system and run Autoruns and then click on File> Save.. Save the file in .arn format and upload here. Will have a look

I will update the BIOS when I get a chance. About the PCI Communicaton Driver - I will look at the URL in your reply. When I go to the Intel download site, I can download Win 7 versions of the drivers, but I cannot download Vista versions, as Intel says that I am not running Vista. And I could not find on the Intel web site a place to download a later version of the Vista driver that was implicated in the dump. I will have a further reply when I have followed the hyperlinks in your two replies. And it is my policy not to make two changes at once; I wait between changes so that if something goes wrong, I know what change might have caused it. When I was working with IBM mainframes, we made two big changes on one day, and a problem arose. I took about a month to determine what was happening. I spent a lot of time looking at the source changes in both components, but I never found the culprit.
--Barry Finkel

Install the Windows 7 version chipset driver, and then install the Vista version of the LAN driver.

I just updated the BIOS, so I will hold off on further updates for at least 24 hours. I am not sure what you mean when you write, "Install the Windows 7 version chipset driver, and then install the Vista version of the LAN driver." I believe that my version of the chipset driver is up-to-date, as far as Intel is concerned. From the URL https://downloadcenter.intel.com/Det...eng&iid=dc_rss I downloaded INF_allOS_9.1.2.1008_PV.exe . When I ran it (I had run it earlier), I saw the output:

"Please wait while the following setup files are extracted:"

Then a message window"

The computer currently contains software version 8.4.0.1017, which is newer than the version you are about to install. Are you sure you want to overwrite the current software with the older version 9.1.2.1008?

I replied "NO", and the install process ended. I have no idea if anything was installed; I also do not know what driver(s) would have been back-level if I had replied "YES". The install process terminated right after I replied "NO", so I do not
know if that reply terminated all of the installs, There was no output was to what was happening during the installs except for the initial list of files that were being extracted from the install package. I would like to install the latest version of e1e6032.sys, the Intel Ethernet driver for Vista, but I do not know where to get an official Intel version. My Win 7 version, e1e6232.sys, is up-to-date. Other than that, I have no idea what other Intel drivers I have installed are back-level. The UpdateMyDrivers software points to "9.3.1.1009 (9/11/2012)" and says that my installed version is "6.1.7601.17514 (06/21/2006)". This is for a number of system devices. One problem I have is this - the UMD software lists, for example, "Intel(R) ICHB Family SMBus Controller - 283E", but it does not tell me what is the name of the driver file. And, as I have written earlier, I am not sure where to find the 9.3.1.1009 driver files on the Intel website.

As is the case with much software these days, the authors assume that the end-user knows what is happening, and therefore the software does not give enough information to the end-user. I have experienced many Windows pop-up error windows where I have no idea what process produced the error window. The author assumes that his/her software is the only thing running, so the error message will easily be matched to the software.

--Barry Finkel

For god sake stop using "UpdateMyDriver" software... each divers have specific function and features for particular manufacturers. they are not always the same. uninstall them .

Update using the link provided in the previous post.

I am not sure to what link you are referring. There are a number of hyperlinks in previous replies. I am NOT using UpdateMyDrivers to do anything other than scan my drivers and (I hope) give me an accurate report as to which drivers need to be updated. Do you know of such a tool that I can use?

And, as additional information - I have experienced two seemingly random different BSODs in the past few days:

(50) PFN_LIST_CORRUPT (4e) [Saturday evening]

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. [Sunday evening a few hours after I updated the BIOS]

--Barry Finkel

Could you please upload the new BSODs with the same SF_Diagnostic Tool as before?

I would personally never recommend using any driver update programs, even for checking for driver updates, from my understanding, the only method they could use to check for any updates, is to check the timestamps of your drivers and then compare it to their own database of drivers.

I have just uploaded a new SF zip file. On Monday I experienced a BSOD "EXCEPTION_CODE: (NTSTATUS) 0xc0000005".

Yesterday, I experienced a BSOD "bugcheck (8e)", and the system would not reboot. I had to restore from a restore point created Monday by Windiws Update.

Then, after I left the computer last night I had another "MEMORY_MANAGEMENT (1a)" BSOD.

--Barry Finkel

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Enable the Special Pool option too, it will be listed under "Select Individual Settings" or something similar to that; enable all the options apart from Low Resources Simulation.