New
#11
OK I have uninstalled Kaspersky and run the TDSSKiller and it came back clean. I am just running Eset Scanner now. Yes I used control panel and uninstall. Once again thank you for your help
OK I have uninstalled Kaspersky and run the TDSSKiller and it came back clean. I am just running Eset Scanner now. Yes I used control panel and uninstall. Once again thank you for your help
Hmm Ok.
When did you last reinstall windows?
How old is your PC?
Any hardware changes recently?
I last reinstalled Windows about a month ago on a different HDD but it was still behaving the same way so I bought new RAM hoping it would just be a memory compatibility problem and put the original HDD back in. It's not very old, I built it myself but have not benn using it as I have been having these problems with it and have not had the time to fix it. There has not been any hardware changes, it is the same as when I built it apart from RAM, which by the way I have just take the kingston out and left the G-Skill in there just incase it was that. Eset has not found anything so far!
Alright.
Perform these stress tests:
Hardware - Stress Test With Prime95
CPU - Stress Test Using IntelBurnTest
Video Card - Stress Test with Furmark
Monitor your temps with Speccy during these tests
Video Memory Test
Thank you I will do these tests now!
OK so I have run Prime95 for over an hour and no problems and I run intelliburn with no problems now I will run the furmark test!
Just ran furmark for 20 minutes and it never went over 80c which is very good I understand.
OK. BTW:
Code:fffff880`0101a000 fffff880`0102e000 winhv (deferred) fffff880`01030000 fffff880`01156000 sptd T (no symbols) fffff880`01156000 fffff880`0115f000 WMILIB (deferred)Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first, though I cannot determine it that with which particular program you have got it from the supplied MSINFO32.nfo. 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.
I just got three BSOD's in the space of two minutes
Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 26/12/2012 14:22:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122612-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xF4, 0x2, 0x0, 0xFFFFF80003EDF65B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 26/12/2012 14:22:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xF4, 0x2, 0x0, 0xFFFFF80003EDF65B)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 26/12/2012 14:20:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122612-22885-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003EEC248)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
This is really annoying me! I will uninstall that driver now my friend.
Edit: It is greyed out as I have already uninstalled it.