power kernel event 41 task 63 crashes

[ttran]

Please perform a http://www.sevenforums.com/tutorials/433-disk-check.html and HD Diagnostic (download and hard drive diagnostic from manufacture's site).

After doing those 2 test, please enable Driver Verifier:
Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

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

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

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88002db64b8, fffff88002db5d20, fffff88001346dc1}

Probably caused by : Ntfs.sys ( Ntfs!TxfDeleteTxfFo+11 )

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

Let us know the result ASAP

Tuan

 

[webbchr]

Do you think if I exchanged the Hard Drive to new egg for a new one the problems would stop?

 

[webbchr]

from what you have seen in the minidumps and symptoms do you have any reason to suspect that any other part of the hardware is defective? My 30 days refund policy is almost up so if i might need to replace items I want to make sure I do it on tome.

 

[webbchr]

Hey ttran.

When you told me to run HD Diagnisic I thought you meant memtest86. I am currently running memtest86. I is on pass 2 and has 4096 errors. The err-bits all say 00800000. I dont know what this means or what to do about it. The first time I ran memtest86 a few weeks ago it did 7 passes with no errors.

I was planing on replacing my hard drive tomorrow but could these errors be the major issue?
please help and thanks in advance for any help you can offer.

 

[ttran]

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

 

[CarlTR6]

Hey ttran.

When you told me to run HD Diagnisic I thought you meant memtest86. I am currently running memtest86. I is on pass 2 and has 4096 errors. The err-bits all say 00800000. I dont know what this means or what to do about it. The first time I ran memtest86 a few weeks ago it did 7 passes with no errors.

I was planing on replacing my hard drive tomorrow but could these errors be the major issue?
please help and thanks in advance for any help you can offer.

As of yet, I see no reason to replace your hard drive. Troubleshooting hardware is a process of elimination. You have identified a problem with RAM - which is far more likely to be the cause than is the hard drive.

Now what you have to determine is if the RAM is bad or the Ram slot is bad. Pull all of your RAM except one stick and test that stick. If it passes, move it to another slot and test again. Do this until you have tested each slot.

If that first stick fails, test it in another slot. If it fails again, put it aside and proceed with the next stick. Your objective is to identify any and all bad RAM sticks as well as any bad RAM slot.

Get your RAM sorted out and then you can test your hard drive. You can use your good RAM stick(s) and run your system.

 

[webbchr]

All right. I started testing the ram slots with one good stick. The reason I was concerned about replacing my harddrive is because the last day for me to return it to newegg is on Thursday. But I suppose if i find out that the hard drive is to blame latter then I can always refer to the manufacturers warranty.

thanks for the help. I will update on the process when I finish the ram slot testing.

 

[CarlTR6]

We will be waiting.

 

[webbchr]

I tested all of the slots and both stick for at least 7 passes. No errors. Why would there have been so many before if i cant find any now?