OTL did produce logs.
I have 32 bit and 64 bit logs.
Attaching logs soon.
Here are the logs.Two of no use anymore.
You appear to have had zero access at some stage but it looks to have been removed. Could you upload the last few minidumps to a file sharing site for me to collect
OK no problem but the minidump which I read was 2010. Searching right now.Be back with new reply unless I encounter no dumps at all.
Hello essexboy!,
Sorry to disturb you. Here is the attachment of the minidumps. All are ntoskrnl.exe problems.
My Win 7 is totally wrecked so it’s backup time and reformat for me.
Sorry to give you so much headache.
Thank you.
Tried to attach 3 minidumps ‘.dmp’ here.Failed.
I am not allowed to post .dmp extension files here. So what should I do?
Oops! Sorry my mistake.
“Could you upload the last few minidumps to a file sharing site for me to collect?”
Yes, I will upload the last few minidumps to a file sharing site for you to collect.
I tried ziddu and some other file sharing sites. These sites do not accept ‘.dmp’ files upload.
Try mediafire http://www.mediafire.com/
Thank you for telling me where to upload the .dmp files.
Here are the URL links for the three minidumps:
http://www.mediafire.com/download.php?we951aus7x83pk2
Hi,the files cannot be downloaded because " This file is currently set to private." and so you are the only who can download them from mediafire.
Oh! I am sorry about it .I will reset it again to public.
Thank you very much.
All dmp files have been set to public from private. Thank you.
crash dump file: C:\WINDOWS\Minidump\031813-27128-01.dmp This was probably caused by the following module: 51578899.sys (51578899+0x114FE) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000006, 0xFFFFF88000F634FE, 0xFFFFF880031BD678, 0xFFFFF880031BCED0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 51578899.sys . Google query: 51578899.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MNow the format for that would indicate that it is a Kaspersky driver causing the problem however, it is not showing on the logs so lets see if I can find it
For 32bit systems, please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2
For 64bit systems, download SystemLook from here.
[*]Double-click SystemLook.exe to run it.
[*]Copy the content of the following codebox into the main textfield:
:filefind
51578899.sys
:regfind
51578899.sys
[*]Click the Look button to start the scan.
[*]When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
Note: The log can also be found on your Desktop entitled SystemLook.txt
Hello. I ran the systemlook.exe
It’s empty.Attached is the log.
Is it still blue screening ?
Sorry about it. I forgot to tell essexboy that the SystemLook was ran in SafeMode.
Run again in Normal mode to see the log.
Safe mode or normal makes no difference as it searches the disc and registry irrespective
I have tried in Normal mode.It’s still empty.
The System Idle Process is running at 99% when ‘Not Responding’ kicks in.
No more BSOD as long as I don’t run any AV programmes.
When I ran ISO Kaspersky Rescue Disk 10 and chose Windows 7 GUI, the system freezed in the RAMDISK .
I had to press the on/off button.
Anyway, I have given up trying to repair this wrecked Windows 7.
I am checking if the HDD is failing and backing up before clean reinstalling the Windows 7.
If the system is running without ‘Not Responding’, then everything is fast but once I run a browser then the whole system is down.
Thanks for your time essexboy.
Have you ran a checkdisc to check for bad sectors ?
I going to do that now.