Author Topic: Tired of BSODs.  (Read 8865 times)

0 Members and 1 Guest are viewing this topic.

Offline matthijsdevries

  • Newbie
  • *
  • Join Date: Oct 2013
  • Posts: 5
  • Karma: 0
    • View Profile
Tired of BSODs.
« on: October 27, 2013, 05:14:17 am »
Hello Tweaking.com,

First let me introduce myself, I am a Dutch gamer (so my English isn't perfect) with a problem on my 6-year-old computer. When I open a program (like steam or smite) the computer will shutdown and will show me a blue screen.

I wanted my dxdiag.txt here, but guess what, a BSOD... So I have to do it myself.
- Windows Vista Home Premium (Service Pack 2) (32-bits)
- Intel Core2 Quad CPU Q6600 @ 2.40 GHz
- 4 GB RAM
- AMD Radeon HD 7700 Series 1GB GDDR5

I ran all the tests of tweaking.com widows repair and got a bit further in the smite running process, but eventually still got a BSOD. So what I want is a solution to play more games than just League of Legends and I want to run steam and other programs again.

I hope someone can help me, because I am getting sick of it.
Regards, Matthijs.

Offline chris635

  • Sr. Member
  • ****
  • Join Date: Nov 2011
  • Posts: 442
  • Location: USA
  • Karma: 11
    • View Profile
Re: Tired of BSODs.
« Reply #1 on: October 27, 2013, 11:28:12 am »
Hi,

    First you need to find out what is causing the crash. There is a tool called "WhoCrashed" you need to install it. After you have the crash, reboot and run this tool, it will tell you what happened.


Here is the link for the tool.
http://www.resplendence.com/whocrashed

This should help figure out what is crashing.

Good Luck  :wink:

Chris
Physical Science Technician
Avid Motorcyclist

Have a nice day - Chris

Offline matthijsdevries

  • Newbie
  • *
  • Join Date: Oct 2013
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Tired of BSODs.
« Reply #2 on: October 27, 2013, 03:15:41 pm »
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 27-10-2013 14:45:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102713-04.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0xDB5)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF807B0A65, 0xFFFFFFFFC350F784, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program 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: mpfilter.sys .
Google query: mpfilter.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Sun 27-10-2013 14:45:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0xDB5)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF807B0A65, 0xFFFFFFFFC350F784, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: mpfilter.sys .
Google query: mpfilter.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED



On Sun 27-10-2013 11:46:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102713-03.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0xDB5)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF807ABA65, 0xFFFFFFFFB713A784, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program 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: mpfilter.sys .
Google query: mpfilter.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Sun 27-10-2013 11:34:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102713-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xFFFFFFFFB8000060, 0x1B, 0x1, 0xFFFFFFFF82ABB5CE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Sun 27-10-2013 11:29:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102713-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98379)
Bugcheck code: 0x50 (0xFFFFFFFF97226000, 0x0, 0xFFFFFFFF82A7133D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 Sat 26-10-2013 21:26:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102613-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0xDB5)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF807A9A65, 0xFFFFFFFFB4771784, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program 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: mpfilter.sys .
Google query: mpfilter.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 25-10-2013 19:55:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102513-03.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0xDB5)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF807B6A65, 0xFFFFFFFFB69F0784, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program 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: mpfilter.sys .
Google query: mpfilter.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 25-10-2013 17:55:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102513-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x6C, 0x1B, 0x1, 0xFFFFFFFF82AC37B2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Fri 25-10-2013 17:51:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102513-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x23ADD1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C51DD1, 0xFFFFFFFF8C3CF91C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 21-10-2013 5:57:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102113-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3E588)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A5C588, 0xFFFFFFFF8C3BFB94, 0xFFFFFFFF8C3BF890)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 17-10-2013 12:23:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101713-01.dmp
This was probably caused by the following module: ksecdd.sys (ksecdd+0x3D688)
Bugcheck code: 0x50 (0xFFFFFFFF9EB70000, 0x0, 0xFFFFFFFF82A2E33D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 15-10-2013 12:28:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101513-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x23ADD1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C48DD1, 0xFFFFFFFF8C3D791C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 13-10-2013 9:22:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3E588)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A72588, 0xFFFFFFFF8C3C7B94, 0xFFFFFFFF8C3C7890)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 27-8-2013 10:52:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082713-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3E588)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A76588, 0xFFFFFFFF8C3CBB94, 0xFFFFFFFF8C3CB890)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 6-8-2013 6:50:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080613-01.dmp
This was probably caused by the following module: ksecdd.sys (ksecdd+0x3D688)
Bugcheck code: 0x50 (0xFFFFFFFF9E997000, 0x0, 0xFFFFFFFF82A3733D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

31 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:

dxgkrnl.sys (DirectX Graphics Kernel, Microsoft Corporation)
mpfilter.sys

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Offline matthijsdevries

  • Newbie
  • *
  • Join Date: Oct 2013
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Tired of BSODs.
« Reply #3 on: October 27, 2013, 03:17:49 pm »
Hello again,

I have tried to fix or identify these problems on Google with the links provided, but I don't really know what to do. I am not that handy with computers.
Someone who can give me an explanation of what is written above?

Matthijs

Offline chris635

  • Sr. Member
  • ****
  • Join Date: Nov 2011
  • Posts: 442
  • Location: USA
  • Karma: 11
    • View Profile
Re: Tired of BSODs.
« Reply #4 on: October 27, 2013, 03:55:54 pm »
Are you running "Microsoft security essentials" anit-virus?. Mpfilter.sys is part of that program. Try uninstalling this if you have it installed, then re-install it, or better yet, use the free version of avast.  Before you remove anything, perform a system restore back up. Always better to be safe in case something goes wrong.


Chris
Physical Science Technician
Avid Motorcyclist

Have a nice day - Chris

Offline matthijsdevries

  • Newbie
  • *
  • Join Date: Oct 2013
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Tired of BSODs.
« Reply #5 on: October 28, 2013, 01:33:18 am »
System restore backup is made.
Microsoft Security Essentials is installed on my computer.
Uninstalling + reinstalling it now...

BTW, I'm running in safe-mode now because if I reboot or start my computer I will get a black screen with cursor, but it won't load anything.

Matthijs

Offline matthijsdevries

  • Newbie
  • *
  • Join Date: Oct 2013
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Tired of BSODs.
« Reply #6 on: October 28, 2013, 01:54:26 am »
I can't find the solution on the internet so I will make a backup on an external hard drive. Delete Vista and install Windows 7, I'll let you know when it's done and if it had solved my problems.

Matthijs

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Tired of BSODs.
« Reply #7 on: October 28, 2013, 04:06:37 pm »
It may be hardware related. First thing to do is to test the memory and the hard drive.
http://www.memtest86.com/

Have you check the drive for bad sectors yet? And by any chance have you checked on what the CPU temperature is when you get the blue screen?

Shane

Offline chris635

  • Sr. Member
  • ****
  • Join Date: Nov 2011
  • Posts: 442
  • Location: USA
  • Karma: 11
    • View Profile
Re: Tired of BSODs.
« Reply #8 on: October 28, 2013, 04:53:56 pm »
Yeah  :tongue: That was going to be my next suggestion. I was trying to hope for the best LOL! :cheesy:


Chris
Physical Science Technician
Avid Motorcyclist

Have a nice day - Chris