BSOD mainly when starting games, but also while multitasking

[jasonhanna]

I hope I am posting this correctly.

I thought I knew about computers until I started to read some of the SF DIAG Tool v4 logs... and then I realized I am in way over my head.

My sincerest gratitude to anyone who can help me.

I get the BSOD mainly when starting games, such as Eve Online or Call of Duty 3, using Steam, but I have also got it while reading email in Outlook in between typing in MS Word and using Firefox.

 

[jasonhanna]

Daemon tools is now removed.

 

[Anthony]

1. Uninstall Kaspersky Anti Virus (add remove programs)
2. Download & Install Microsoft Security Essentials - Free Antivirus for Windows
3. Clean start up with msconfig >go to start orb type msconfig hit enter>go to start up tab uncheck all except your anti virus (in this case MSE)
4. Reboot wait for BSOD then post it here.

Thanks Ant

 

[jasonhanna]

I followed each of these steps, and I will keep you apprised of any further BSOD incidents. Thank you kindly for the timely response!

 

[jasonhanna]

Another BSOD hit me late last night. Here is the new batch SF DIAG Tool v4 files.

 

[jasonhanna]

It happened again today. I was outside while Eve Online, 3 firefox windows windows, MS Word, MS OneNote, and windows explorer were idling.

Please see the attached minidump from the crash.

Again, thank you for all your effort in helping people like me deal with the frustration of a breaking computer.

FYI I have made no hardware changes to my system in about a year to a year and a half. I make software changes pretty regularly with the installation and removal of games pretty frequently.

When the BSOD got pretty bad, I ran Eusing Free Registry Cleaner and got rid of about 750 invalid registry entries. It didn't help -- but I did take the initiative to do that much

thanks again folks.

 

[Anthony]

Hello Jason, We seem to be getting a lot of memory corruption, Can you please follow this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Report back with your findings.

 

[jasonhanna]

i ran the mem test. no issues discovered.

i also ran malwarebytes anti-malware. no issues discovered.

I also ran HP Tune Pro and scanned my drive. no issues discovered.

I also ran the western digital hdd drive utility. no issues discovered.

i also ran WhoCrashed... but couldnt make sense of it. it labeled "unknown driver" as the cause of my crashes. that and kl1.sys, which was from kaspersky. so good call getting me to uninstall that.

perhaps the most productive thing i did was order a new SSD from newegg, i think i may reinstall windows on a new drive and pull over any files i want to keep from this HDD. think this is a good idea? i am at my wits end. i have tried nearly everything i can think of and that has been suggested here.

i am posting the WhoCrashed log here even though i dont know what good it will do.

[FONT=Segoe UI, Arial]Welcome to WhoCrashed (HOME EDITION) v 3.06 [/FONT]
[FONT=Segoe UI, Arial]This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
[/FONT]

[FONT=Segoe UI, Arial]To obtain technical support visit www.resplendence.com/support

[/FONT][FONT=Segoe UI, Arial]Click here to check if you have the latest version or if an update is available.

[/FONT][FONT=Segoe UI, Arial]Just click the Analyze button for a comprehensible report ...


[/FONT][FONT=Segoe UI, Arial] Home Edition Notice [/FONT]
[FONT=Segoe UI, Arial]This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
[/FONT]

[FONT=Segoe UI, Arial] System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: BEAST
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6440869888 total
VM: 2147352576, free: 1916186624
[/FONT]

[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Tue 8/21/2012 2:05:23 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0x593FDE61)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80065507C8, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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: Unknown .
Google query: [FONT=Segoe UI, Arial]Unknown KERNEL_DATA_INPAGE_ERROR[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Mon 8/20/2012 2:53:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-18969-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007628930, 0xFFFFFA8007628C10, 0xFFFFF8000377E510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 8/20/2012 12:52:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-20404-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0xEF1D0)
Bugcheck code: 0x7A (0xFFFFF6FC4000AA60, 0xFFFFFFFFC000009D, 0x9D22E860, 0xFFFFF8800154C1D0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 8/19/2012 7:08:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081912-24289-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0xEF0CC)
Bugcheck code: 0x7A (0xFFFFF6FC4000A9F8, 0xFFFFFFFFC000009D, 0x156E08860, 0xFFFFF8800153F0CC)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 8/18/2012 3:14:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081812-23883-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0xEF0CC)
Bugcheck code: 0x7A (0xFFFFF6FC4000D9A0, 0xFFFFFFFFC000009D, 0x1283DD860, 0xFFFFF88001B340CC)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 8/18/2012 2:34:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-26629-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006DBCB30, 0xFFFFFA8006DBCE10, 0xFFFFF80003785510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 8/15/2012 4:49:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081512-18876-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800780D910, 0xFFFFFA800780DBF0, 0xFFFFF800037DE510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 8/15/2012 3:49:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-23571-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800700B7C8, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 8/10/2012 5:22:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-23431-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8006BDD628, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 8/10/2012 4:58:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080912-20685-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x87CE9)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8007E31078, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 8/5/2012 9:17:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-22838-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800717D078, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 6/6/2012 8:00:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060612-30076-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x4E (0x9A, 0x1AE526, 0x6, 0x2)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 4/25/2012 11:52:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042512-22682-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x4E (0x9A, 0x1ADCEE, 0x6, 0x3)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 4/23/2012 9:43:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-18345-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80071BF7C8, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 4/23/2012 9:13:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-63554-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]kl1.sys[/FONT] (kl1+0x24B8E8)
Bugcheck code: 0x4E (0x9A, 0x3BB3, 0x6, 0x2)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: kl1.sys .
Google query: [FONT=Segoe UI, Arial]kl1.sys PFN_LIST_CORRUPT[/FONT]


[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]20 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]kl1.sys [/FONT]

[FONT=Segoe UI, Arial]unknown [/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.[/FONT]

 

[jasonhanna]

no more suggestions?