Random BSOD, multiple errors - 0xFFFFF8800CB48190 & 0xFFFFF8A229099FC0

capobello · 05 Jun 2014

Hello,

My PC is experiencing random crashes/freezes, and BSOD, typically at start up when I start browsing the web or at times at playing PC games. My WhoCrashed analysis seems to have multiple error codes indicating driver issues but I cannot recall installing any new software recently, some of the error codes are:

On Fri 6/6/2014 12:03:42 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8800CB48190)
Bugcheck code: 0xA (0xFFFFF8800CB48190, 0x2, 0x1, 0xFFFFF80002D050B2)
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.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL

On Thu 6/5/2014 11:50:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060514-14508-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8A229099FC0, 0x0, 0xFFFFF80002F960B9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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

Please see attached Debug report.

Thanks

capobello · 06 Jun 2014

FYI, I am gong to run Memtest to determine if RAM is an issue, does anyone else have any suggestions from bug report?

Golden · 06 Jun 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a229099fc0, 0, fffff80002f960b9, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiRelocateImagePfn+29 )

Followup: MachineOwner
---------

Bugcheck 0x50 is usually a memory problem, so go ahead and test that using MemTest86+ for a minimum of 8 passes

RAM - Test with Memtest86+

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DA2B960, {c0000005, fffff80002f43395, fffff8800ccb0430, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

Followup: MachineOwner
---------

I have never come across this bugcheck before

lets ignore it for now

Code:

fffff880`0917a5e8  fffff880`013ca010*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x9010

Ensure Windows is fully updated.

What anti-virus software is currently installed?

Just cautionary : can you please scan for rootkits using this tool:
http://www.bleepingcomputer.com/download/tdsskiller/

capobello · 06 Jun 2014

Thanks for the response. I ran memtest and got a failure very quickly, 4th test on 0 pass.
Assuming that is the issue? Do I need to run the rootkit test or should I just replace the RAM?

Thanks much

Golden · 06 Jun 2014

You can move straight to isloating the specific RAM DiMM, then replace it completely.

At some point it wouldn't hurt to do the rootkit check....its just a cautionary step given the odd bugcheck we saw earlier.

capobello · 06 Jun 2014

Got it, will replace RAM tomorrow then run rootkit test and post results.

Thanks!

capobello · 07 Jun 2014

So I installed the RAM and everything seems to be working fine (so far). I also ran the rootkit tool and everything came back okay as well. I will mark this closed, hopefully everything should be good with the new RAM installed.

Golden · 07 Jun 2014

Just post back here in the same thread if you have any other BSOD.