ntoskrnl.exe is the kernel on which a module crashes. When the dump recording mechanism fails to identify which module failed actually, it mistakenly blames the kernel itself. Whatever, it can never be the cause of a BSOD, whereas BSODs occur on it, BSODs affect it. Moreover, it is not any driver. Its the kernel..... an OS element. If you altering it will never help anyway, but will make the system even unstable.
Anyway, all your recent BSODs are either Stop 0xF4 or stop 0xA with partmgr.sys as failing module. As like ntoskrnl.exe, you cannot do anything with partmgr.sys. So the cause it to be searched in elsewhere.
Where? A stop 0xF4 is storage access error; partmgr.sys also related to storage devices. So the problem is somehow the storage access is being blocked.
Storage access may be blocked by either a SSD running with backdated firmware, or a failing storage device, or a bad cable/ port, or failing storage initializing drivers, or by the filter service of an antivirus, or by a virus. Let us check those one by one.
Check that your OCZ-AGILITY3 SSD is running with up to date firmware.
You dont use any SCSI driver, but the native ATA/ATAPI controller, which never causes any trouble, so we can take it out of list for the time being.
No antivirus installed? Or I am missing something? Use
Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and
free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
Moreover, there are reasons to do some deeper virus scan.
Code:
fffff880`076414e0 fffff880`010fd956 ataport!GenPnpFreePdo+0x68
fffff880`07641510 fffff880`010fe4ce ataport!GenPnpPdoRemoveDevice+0x86
fffff880`07641540 fffffa80`04fcb81c ataport!IdePortDispatchPnp+0x22
Scan the system for possible virus infection with the following programs only.
If these tow scans come clean, we have to search for the reasons of these errors elsewhere, in hardware. Might be the port to which the SSD is connected via a SATA cable is not the appropriate one or failing, or simply the SATA cable itself is failing.
Do these and let us know the results.
___________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80059b7b30, fffffa80059b7e10, fffff80003782470}
----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
Followup: MachineOwner
--------------------------------------------------------------------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {10, 2, 0, fffff80003466852}
Probably caused by : partmgr.sys ( partmgr!PmPnp+fe )
Followup: MachineOwner
---------
May be we have one more work pending in this thread ..... not sure right now.