Solved BSOD playing ESO, BCCode a.

[Requimatic]

Heyo! So as the title states, I was casually playing ESO a bit ago and ran in to a BSOD. (at quite a bad time, no less.) "IRQL_NOT_LESS_OR_EQUAL", BCCode a.

Googled the issue first, and everything I managed to come upon regarding this particular BSOD points to old drivers. I know my video driver is a bit out of date, but it's one I've had zero issues with, and I'm iffy about updating to the newest nVidia drivers right off the bat due to bad past experiences.

As for other potential drivers causing the problem, I honestly have no idea at this point which are severely out of date to the point that I should probably update them. A /cmd driverquery shows a lot of items that date back as far as 2009, so there's that.

So before I go ahead and do that, I thought I'd post me a thread here. Included is the zip file containing all the necessary files.

Thanks in advance!

 

[essenbe]

Hello, Requimatic. I will try to help you. You only had one dump file for me to examine, so we will have to go with that. Please make sure your computer is configured for Small Memory dumps, (http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html) and if you are using any disk cleanup tools, please do not use them any more until we get this straightened out. The majority of them delete error reports and dump files by default. This s what your dump file said.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff80002f95b6b}
[COLOR=red]Probably caused by : memory_corruption[/COLOR] ( nt!MiStoreSetEvictPageFile+b )
Followup: MachineOwner

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes during the same session or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes run at the same time to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.​

I would also suggest you update your drivers. Drivers tell a piece of hardware how to act. If they do not keep up with the changes in games, programs and coding, they will malfunction. Also, please make sure your Windows updates are current.​

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.​

Let us know the results of those tests and scans.​

 

[Requimatic]

I see, thanks for the reply!

Thankfully I've still got a bootable USB flash drive setup with memtest, so I'll give that a run tonight. Before I let it go all night, I'll give SFC a go and see what it has to say. I'll report back to the thread once I complete the memtest routine.

Until then, thanks and take care!

 

[essenbe]

No problem, just be sure the Memtest you have is memtest86+ downloaded from the link I gave. I look forward to hearing from you. The sfc scan won't take real long.

 

[Requimatic]

Sorry for the long reply, I've been overly busy the past few days.

While I've not had the system BSOD on me again, SFC did find things that it was unable to repair. It created a log, from which I plucked the error lines from using the following command prompt command:

findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt

Which created the attached text file. If need be, I could attach more from cbs.log, but the file in its entirety is almost 15MB. (Which I believe is well above the .txt limit.)

From what I read about that, and from what the system has been doing, it's looking almost like:

1. Faulty RAM module.
2. Faulty HD.

Both are quite possible, as the hardware is indeed old, and one of the RAM modules (3x2GB) failed in the past and had to be RMA'd.

What else that makes me think it's likely the HD is:

1. Missing textures in games. (Said game subsequently CTD'd without an Event Viewer entry.)
2. Overall sluggish performance.

I've yet to run memtest, and was considering a chkdsk /F after the next reboot.

Oh, also worth noting: I had WDM.exe crash last night before bed, and would not start again until the system was rebooted.

 

[essenbe]

Ok, I will have someone else look at the sfc file you uploaded. You can right click it and sent to > compressed Zi[ folder and upload that here. If it is still too large, you can upload it to a public file on Onedrive or Dropbox. But we will wait and see if it is needed. You can run this command to get the details text to your desktop

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

I'm not sure if it will be much different than what you ran.

If you want to check your hard drive, You can run Western Digital's Data Lifeguard for DOS (WD Support / Downloads / SATA & SAS / WD Black) or Seatools for DOS (http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3) run both the short and the long tests.

To test the ram

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes all run in the same session or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes run in the same session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[NoelDP]

Just the usual dross from KB3022345


SFCFix Script


Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.

• Download SFCFix.exe (by niemiro) and save this to your Desktop.
• Download SFCFix.zip from the below link, and save this to your Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
• download this version: SFCFix(x64version)
• Save any open documents and close all open windows.
• On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.

• Drag the file SFCFix.zip onto the file SFCFix.exe and release it.

• SFCFix will now process the script.
• Upon completion, a file should be created on your Desktop: SFCFix.txt.

• Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please – put tags around the log to break up the text.

SFC /SCANNOW

• Right click on the Start button
• Click on Command prompt (Admin) => Press Yes on the prompt
• Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
• post the new CBS.log file when complete

 

[Requimatic]

Thanks for the replies!

@essenbe: the WD tool just completed a long test, and both it and a short one passed. So I guess the HD is fine?

@NoelDP: I have the two files and am following instructions now. Closing this until the next SFC is complete, at which point I'll paste the log.

 

[essenbe]

When you finish the above, run the command I gave and upload the whole text, if not here then to Onedrive or Dropbox, whichever you prefer.

 

[Requimatic]

Ran SFC and it completed successfully this go around. Attached are the two requested files.

So I guess at this point, all that's left is memtest? The flash drive I used before (with memtest86+) is still setup and ready to go.

Edit: oh, this may be worth noting. When I ran the WD tool, I noticed that it said this drive has 136GB free, when Windows shows 126GB.

 

[NoelDP]

That looks a lot better!
SFC is now clear, and SFCFix shows exactly what it should.

I'll hand you back to Steve (essenbe) now

 

[Requimatic]

That looks a lot better!
SFC is now clear, and SFCFix shows exactly what it should.

I'll hand you back to Steve (essenbe) now

Cool deal, thanks!

 

[Requimatic]

Was in bed early last night and didn't run memtest. (again...)

Received yet another BSOD (PNF_LIST_CORRUPT; BCC 4e) just a bit ago, attaching the .zip containing logs and whatnot. Afterwards, I'm going to restart and run mentest despite how long it may take. Getting pretty tired of wondering when the next BSOD or crash is going to happen.

I'll get back to the thread once it's complete. (errors or otherwise)

Edit: Currently on the laptop while memtest runs. The good news is, I guess, that my memory is still under warranty (thanks, G.Skill lifetime warranty!), so if some/all of it is faulty, I can at least RMA it.

 

[essenbe]

here's what the dump file says.

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {2, 189c0, 1dffff, 1}
[COLOR=red]Probably caused by : memory_corruption[/COLOR] ( nt!MiUnlinkPageFromLockedList+8d )
Followup: MachineOwner

 

[Requimatic]

here's what the dump file says.

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {2, 189c0, 1dffff, 1}
[COLOR=red]Probably caused by : memory_corruption[/COLOR] ( nt!MiUnlinkPageFromLockedList+8d )
Followup: MachineOwner

Was afraid of that. Memtest is still running, though. It's almost through pass 3, with no errors so far.

Still got a long while to go, though.

 

[essenbe]

Let it run at least 8 passes, more if you can.

 

[Requimatic]

Day 47. Memtest still continues. Running low on supplies, send help.

But seriously, it's almost done with pass 9 (it's about 60% in to the final test of the pass) and it's found zero errors so far.

I'm not sure whether to leave it go over night (for a near-20 hour run; it's at just over 11 hours now) or stop it now and try something else, like cleaning the contacts on the memory with some isopropyl alcohol and reseating it.

 

[essenbe]

Let it finish the 9th pass. then take a picture of the screen and stop the test. Upload the picture here, please. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Requimatic]

Unfortunately, I didn't see your request for a picture before I had to end it. Storms rolling through forced me to stop it, shut down, and unplug things. Thanks to shoddy wiring in this house, I've lost various electronic devices to lightning (including half the I/O panel of the last PC), and I'm not willing to risk this. haha

But it was done with pass 9, 12% in to pass 10, with 0 errors. Over where it displayed the time it had ran (on the right) it said "0 Errors", and there were no changes below the SPD listings on the bottom half of the screen.

 

[essenbe]

No problems. We are having storms too, so I understand. Our electricity will probably go out too before long. If you are overclocking anything, please set everything back to default levels. I am not opposed to overclocking, just when your machine is unstable. Afterwards, you can overclock it again. If it becomes unstable then, you will know why. If you would, please download and install CPUz, if you don't already have it. (CPU-Z | Softwares | CPUID) Please post screenshots of the CPU, Mainboard, Memory and SPD tabs. On the SPD tabs, you can select each Dimm Slot using a dropdown on the upper left. Just post screenshots of the Dimm Slots that have ram installed. Please post them here. This will tell you how, if you don't know. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html