BSOD during normal operation

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800582E8E0
BCP3: FFFFFA800582EBC0
BCP4: FFFFF800037D7470
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Please follow the Blue Screen of Death (BSOD) Posting Instructions

Ok to start please remove these two programs, chances are they have already done irreparable damage to your windows install:

Code:

Start Menu\Programs\Free Registry Cleaner	
Start Menu\Programs\Free Registry Defrag

next please run the system file checker to check for any file system corruption:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

And last please ensure that the firmware for your SSD is up to date and re-seat the data and power cables connected to it, then ensure that your BIOS is up to date. The firmware can be found on the SSD manufacturers webpage. And the Bios can be found on the motherboard manufacturers website.

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.

• OCZ Toolbox: Firmware & BIOS Updates
• OCZ Technology

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.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

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
---------

Just a FWIW, Arc .....

there are a couple of related events in the logs...

Code:

Event[487]:
  Log Name: System
  Source: atapi
  Date: 2013-04-30T13:48:04.443
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TheSecretLair
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.
Event[488]:
  Log Name: System
  Source: atapi
  Date: 2013-04-30T13:48:04.443
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TheSecretLair
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.

OK, now observe how the computer is working. Let us know the results after a few days ... say after seven days.

But if it BSODs, inform us then and there.

Noel, if I get the root of the issue in the dump, I dont see the extra data :) May be we have one more work pending in this thread ..... not sure right now.