Blue screen Error ntoskrnl.exe+f3bf0

Hi The Coldest.

The crash dumps are not very explanatory about the probable cause of the BSOD.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

BTW, your system specs say you have 1 GB RAM only?

This is what you entered in your system specs.

Attachment 328994

Whereas you have 4X1 GB RAM sticks, running at 800 MHz.

Better you rectify it. And let us know for any further issue.

Code:

BugCheck 50, {fffff8a00d254278, 0, fffff800031d817b, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+9b )

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

Can you enable driver verifier for one more time?

uxstyle core causes BSODs that I have seen in a number of cases. You are not alone. :)

For applying custom themes, you may use another good alternative: Theme - How to Apply Custom Themes

And continue with Driver Verifier, IMHO.
____________________________________

Code:

BugCheck D6, {fffff98008151000, 0, fffff88005df7eb9, 0}

*** WARNING: Unable to verify timestamp for uxpatch.sys
*** ERROR: Module load completed but symbols could not be loaded for uxpatch.sys

Could not read faulting driver name
Probably caused by : uxpatch.sys ( uxpatch+1eb9 )

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