BSOD During Registry Search to Remove Reference To Desktop Folder

usmcTop · 12 Apr 2015

Hello Friend.

In an effort to remove a desktop folder that will not go-away using "Delete," I tried to find its reference "...\Desktop\Forms" within the registry, using RegmagiK 64bit. During the search process, I received a BSOD PAGE_FAULT_IN_NONPAGED_AREA . On my limited analysis, minidump 041215-209119-01.dmp faults ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF8A0032AD000, 0x0, 0xFFFFF80003471A63, 0x0)

On opening the DM Log Collector data file, I found additional BSOD occurrences spanning the last several days, and are included in the data file for this thread's background analysis. Hopefully you will find them useful.

It is hoped expert analysis will be performed on the data provided to yield more of a full explanation on the provided data as to the cause of the BSOD occurrences, and identification of the offending driver(s), if any, causing this, and possibly my other, BSOD occurrences.

Please accept my appreciation for any help you provide, and your demonstrated professionalism.

Kind Regards,

David

marsmimar · 12 Apr 2015

Hello David. Welcome to Seven Forums and thanks for your service.

RegmagiK is listed as a Windows registry editor. Editing the registry can cause serious system problems. If you have a System Restore point that goes back to a date/time prior to using RegmagiK I'd suggest restoring your machine. That should return your registry to a pre-RegmagiK condition.

System Restore

I've had good luck using Malwarebytes FileASSASSIN to delete locked files.

https://www.malwarebytes.org/fileassassin/

And this tutorial offers some additional suggestions.

Undeletable File - Delete

Hopefully others will jump in with other thoughts.

Golden · 12 Apr 2015

I'll take a closer look at the. dmp files this evening after work.

Golden · 13 Apr 2015

The most recent BSOD .dmp files are all a mixture of different bugcheck codes, all usually suggestive of memory errors - 0x50, 0x1e, 0x124.

Thus, the first thing to do is to run a minimum of 8 consecutive passes, preferably overnight, or until errors occur using MemTest86+.

Reference:
RAM - Test with Memtest86+

An earlier .dmp seems to blame the Bitdefender Firewall. I recommend uninstalling it, and using the Windows Firewall instead, until the system is stable and BSOD-free.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88015052780, 0, 0}

*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys
Probably caused by : bdfndisf6.sys ( bdfndisf6+1c3c )

Followup: MachineOwner
---------

I'd also advise caution using these sorts of programs - I recommend uninstalling them:

Code:

Start Menu\Programs\CleanMem	Public:Start Menu\Programs\CleanMem	Public
Start Menu\Programs\Dll-Files Fixer	Public:Start Menu\Programs\Dll-Files Fixer	Public
Start Menu\Programs\DriverFinder	Public:Start Menu\Programs\DriverFinder	Public
Start Menu\Programs\DriverNavigator	Public:Start Menu\Programs\DriverNavigator	Public
Start Menu\Programs\System Mechanic Professional	Public:Start Menu\Programs\System Mechanic Professional	Public
Start Menu\Programs\System Mechanic Professional\Search and Recover	Public:Start Menu\Programs\System Mechanic Professional\Search and Recover	Public