Jump to content



Photo

[BSOD] Please help me diagnose this.

Answered Go to the full post win7

  • Please log in to reply
3 replies to this topic

#1 Axel

Axel

    --[Est. 1986]--

  • Joined: 05-August 03
  • Location: Milton Keynes, UK

Posted 28 May 2014 - 10:08

Hi all,

 

I built a computer for a friend about a year ago.  Suddenly, about a couple of mins after boot it's decided to start crashing with a BSOD.

 

Image%202014-05-28%20at%2011.00.44%20AM.

 

I've downloaded BlueScreenView but I'm not entirely sure what I'm looking for. Only trend I notice is ntoskrnl.exe is always involved somehow.

 

I'm attached the minidumps to this post if anyone's got a free moment to take a look.

 

I have run a memtest and this turned up nothing.

 

Cheers,

 

Alex

 

 

Specs:

Board: "Asus P8H61-MX USB3"
Processor: "Pentium"
Memory: "2 x 4gb Crucial Ballistix"
Gfx: "onboard"
SSD: "60gb OCZ agility 3"

Attached Files



Best Answer spikey_richie , 28 May 2014 - 10:20

WhoCrashed reports the following:
 
 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 27/05/2014 16:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7628-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800838A9D0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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/05/2014 15:33:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-8767-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8D9CC, 0xFFFFF88005E47E20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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/05/2014 15:29:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002CDDF1F)
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 Tue 27/05/2014 11:08:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7519-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x17E11)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C71AC5, 0xFFFFF88002FFD1B8, 0xFFFFF88002FFCA10)
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: mpfilter.sys .
Google query: mpfilter.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 20/05/2014 14:25:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-7441-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F70921, 0xFFFFF880053F0A70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 20/05/2014 14:07:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-7269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CBC9E3, 0xFFFFF88008483070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.




Conclusion
6 crash dumps have been found and analyzed. A third party driver has 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:

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.


Have some drivers been updated recently? Can you restore it from a system restore point?

Also have a look at this http://answers.micro...96-ec96deef1d51 Go to the full post



#2 spikey_richie

spikey_richie

    XXXIII

  • Tech Issues Solved: 5
  • Joined: 02-February 05
  • Location: Nuneaton, UK
  • OS: Windows 8.1u1 Pro 64-bit
  • Phone: Sony Xperia Z1

Posted 28 May 2014 - 10:20   Best Answer

WhoCrashed reports the following:
 
 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 27/05/2014 16:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7628-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800838A9D0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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/05/2014 15:33:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-8767-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8D9CC, 0xFFFFF88005E47E20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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/05/2014 15:29:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002CDDF1F)
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 Tue 27/05/2014 11:08:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-7519-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x17E11)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C71AC5, 0xFFFFF88002FFD1B8, 0xFFFFF88002FFCA10)
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: mpfilter.sys .
Google query: mpfilter.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 20/05/2014 14:25:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-7441-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F70921, 0xFFFFF880053F0A70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 20/05/2014 14:07:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-7269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CBC9E3, 0xFFFFF88008483070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.




Conclusion
6 crash dumps have been found and analyzed. A third party driver has 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:

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.


Have some drivers been updated recently? Can you restore it from a system restore point?

Also have a look at this http://answers.micro...96-ec96deef1d51

#3 OP Axel

Axel

    --[Est. 1986]--

  • Joined: 05-August 03
  • Location: Milton Keynes, UK

Posted 28 May 2014 - 12:47

Thanks for your reply. System restore appears to have sorted it.  Uninstalling MSE didn't do anything.  There's obviously some update that was applied and caused the issue, time will tell if it occurs again!



#4 spikey_richie

spikey_richie

    XXXIII

  • Tech Issues Solved: 5
  • Joined: 02-February 05
  • Location: Nuneaton, UK
  • OS: Windows 8.1u1 Pro 64-bit
  • Phone: Sony Xperia Z1

Posted 28 May 2014 - 13:07

Can you mark me as the correct answer then please? :)