Blue Screen Crash, Error Kernal Power 41(63)

ZAXTHEGREAT · 19 Oct 2014

Every so often my computer crashes out with a debug error and I am struggling to find where the issue is coming from. Over the past few weeks I have tested my RAM which came out clean re-seated the CPU, power cables, graphic cards, tried with one or both graphic cards, have the most up to date drivers but have rolled back and tested with older drivers for many of the components but the same error still pops up.

Please see the error information I have provided as an attachment, as I require some help with eradicating the problem for good.

Thanks in advance
ZAXTHE "not so" GREAT with this one.

Arc · 19 Oct 2014

Hi ZAXTHEGREAT.

Click on the button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

ZAXTHEGREAT · 19 Oct 2014

Thanks for your reply, please find attached the results using the DM Log Collector,

Regards

Arc · 19 Oct 2014

Different bugchecks are there. But none of them are pointing to any finite probable cause.

It is also found that you have SPTD in your system.

Code:

fffff880`0104c000 fffff880`01167000   sptd       (deferred)             
    Image path: sptd.sys
    Image name: sptd.sys
    Timestamp:        Wed Sep 11 02:29:02 2013 (522F8816)
    CheckSum:         0006AD52
    ImageSize:        0011B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

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.

Wait and observe how it runs without SPTD. If it BSODs again, run the tool again and upload the result.

ZAXTHEGREAT · 19 Oct 2014

Excellent thanks, I will observe for a few days and will hopefully come back with some good news,

Kind Regards

ZAXTHEGREAT · 21 Oct 2014

Hello Arc,

well I got the same error after a crash about 5 mins ago so the daemon tools uninstall didn't resolve the issue, do you have any other ideas?? Oh my computer is not over clocked either

regards

Arc · 21 Oct 2014

As I said earlier that there are different bugchecks, it is difficult to frame a concrete idea. We have to take the way of trial and error here.

But, multiple bugchecks are often an indication of memory problems. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 continuous passes.

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

Let us know the result.