power kernel event 41 task 63 crashes

First of all, please remove Norton/Symantec antivirus program, It was blamed in some of the crash dump
KB Article Not Found

Comodo appear in one of the crash dump, I would recommend to remove Comodo as well to eliminate the cause
Full Removal of Comodo Firewall Pro 3 with SafeSurf Toolbar (If Regular Uninstall Method Fails)

if you need an alternative program to protect your system, please try Microsoft Security essential, it is known for BSODs free. And make sure firewall is on.
http://www.microsoft.com/security_essentials

Please run a system file check, disk check and HD diagnostic:
SFC /SCANNOW Command - System File Checker
Disk Check
HD Diagnostic

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Code:

BugCheck 3B, {c0000005, fffff80002d69243, fffff88007d125d0, 0}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlInsertExtraCreateParameter+1b )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88002fc4728, fffff88002fc3f90, fffff880012eae51}

Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+61 )

Followup: MachineOwner
---------
BugCheck 34, {50830, fffff88002db6338, fffff88002db5ba0, fffff88000e42fa9}

Unable to load image \SystemRoot\system32\drivers\NISx64\1007000.01E\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : SRTSP64.SYS ( SRTSP64+2672b )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88008384218, fffff88008383a80, fffff880012b5613}

Unable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+e7d0 )

Followup: MachineOwner
---------
BugCheck 1A, {30, fffffa8003af6500, fffff88006f70000, fffff8a00287fef8}

Probably caused by : memory_corruption ( nt!MiApplyRawFixups+87 )

Followup: MachineOwner
---------
BugCheck 50, {fffff8a007037d80, 0, fffff80002adb053, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!FsRtlAddBaseMcbEntryEx+53 )

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

Let us know if you need help

Tuan

vinay8 said:

i ma using dell inspiron 14 machine and i am getting this error again n again . i even formatted my system twice but invain. hardware scans shows that hardware is ok . dell persons are not able to figure out . i need help .....please tell me a probable way out..

If you wish to have others assist you with your computer's BSOD symptoms, please upload your minidump following this instruction:

https://www.sevenforums.com/crashes-d...tructions.html
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

I will ask someone who are good at hard drive. But as long as it didn't fail any test, your hard drive may be ok
Let's work on driver verifier in the meantime:

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Ok, based on the newest dump file, hard drive is blamed mostly.

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION


KB 977178 You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you resume a computer that has a large SATA hard disk <--Check this article
STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

At this point, it's hard for me to deny that the hard drive is ok, as all of the stop code somehow are related to it.

Check the article that I listed above, as I can see you also have very large hard drive 1TB

BUGCHECK SUMMARY:

Code:

BugCheck 19, {22, 80000000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff800020f30e0
GetUlongFromAddress: unable to read from fffff800020611b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88002db08b8, fffff88002db0120, fffff880010513da}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a )

Followup: MachineOwner
---------
BugCheck 50, {fffffbf8000052d0, 0, fffff80002cf74c8, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!AlpcpFlushMessagesByRequestor+50 )

Followup: MachineOwner
---------
BugCheck F4, {3, fffffa80065e7b30, fffffa80065e7e10, fffff80002ddd540}

c0000005 Exception in ext.Analyze debugger extension.
      PC: 00000000`76cddec5  VA: 00000000`00000001  R/W: 0  Parameter: 00000000`0001003f
BugCheck F4, {3, fffffa8005a67b30, fffffa8005a67e10, fffff80002d97540}

Probably caused by : csrss.exe

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