Solved BSODs while idle; Driver Verifier report report available

[SJesMe]

I'll try and make this concise: BSODs occur even while desktop is not in use. Memory_Management and PFN_LIST_CORRUPT is what I remember seeing.

Also: IE9, IE10 and IE11 all "stop working" randomly. Chrome - ditto. FF32 - ditto.

I've run Memtest86 (10 passes) no errors.

The last BSOD was deliberate insofar as I was running Driver Verifier. I'm not sure if I am posting in the right area since the browser crashes and BSODs may be two separate issues ... ?

Dump files(s) attached. Please let me know if I can provide any additional info and thank you in advance for any help with this.

View attachment 342090

 

[SJesMe]

*bUmP* Any wisdom out there please?

 

[Laith]

The program causing the BSOD is Avast. Uninstall avast and install kaspersky or avira as an replacement.

 

[SJesMe]

Thank you Laith. I uninstalled Avast per your advice. I had 2 more BSODs after it was uninstalled. As I was running the dump file to attach here, I also got an error dialogue box advising "WMI CommandLine has stopped working." Not sure whether that is significant to the BSOD but it certainly doesn't sound healthy!

Still looking for help!

View attachment 342160

View attachment 342161

 

[SJesMe]

And a third ... any help out there? Please?

View attachment 342189

I'm seriously ready to swear off computers ... or at least Windows 7 and go back to good old XP!

 

[Golden]

All 3 of your errors are typical memory errors. I noted that you said you ran MemTest86.......can you confirm that it was MemTest86+ that you ran?

Could you also run the following and report back? Please use the DOS version as explained:
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[SJesMe]

Thank you for your response Golden. It was indeed MemTest86.

The SeaTools thing sounds a bit complex. I wonder if you could be satisfied with chkdsk reporting no errors or bad sectors?

My understanding (however limited) is that these random memory errors are usually caused by some driver hogging space beyond what is allocated to it. I am continuing to run driver verifier and nvlddmkm.sys was mentioned somewhere along the line. I do suspect my NVidia driver as the culprit as I was (keyword: "was") receiving multiple "Display Adapter has stopped working ... " errors.

I don't mean to look a gift horse in the mouth since you're willing to help so if it's really important to get to the bottom of this I'll try the SeaTools thing.

Thanks!

 

[Golden]

Please confirm MemTest86+......not Memtest86.

I did see the NVidia reference in the .dmp, but the driver wasn't specifically blamed for a BSOD. None-the-less, you could try uninstalling it completely, then run a Windows Update and then install the Microsoft-certified driver that is offered. Don't update it any further, and monitor for further BSOD.

I still think the SeaTools test might be a good idea.

 

[SJesMe]

Yes it was MemTest86+ ... per Arc of this forum. You see, I have been fighting with BSODs, display driver and browser crashes for approximately 5 five weeks now. Yesterday I had 2 more BSODs after my last post to you. I have had nothing but trouble with that desktop since the day I plugged it in (new machine 5 weeks ago). I re-installed the OS 3 different times (with heidoc's digital river iso), swapped out the hard drive, tried re-seating the memory and graphics cards, etc etc ad infinitum, ad nauseum ... all to no avail. I had switched out Avast to MSE and was still having trouble; tried Panda ... same problems; tried Avira ... same problems; left off any AV program at all ... same problems. Whatever it is, it's beyond my ability to fix and my patience is worn to a nub.

Call me a wimp but I have gone back to my XP desktop. I do thank you for trying to help but enough is enough ... I'm done.