Random BSOD's, seems to have to do with disk activity

[bluemouse]

Hi all,

I've been getting BSOD's for a while now. They mostly seem to happen when I'm processing/copying large amounts of files. It crashed when intellisense was parsing files in VS2010, and also crashes when I check out code. Rather frustrating.

I have a Kingston SSD that my OS is installed on, if that might be part of the problem, but I applied the most recent firmware upgrade for it. I *think* all the drivers are up to date.

Looks to be mainly ntoskrnl.sys and once fltmgr.sys? I had one crash from ataport.sys, but I think that was before I installed all the drivers fully, so I didn't include that one.

Everything before today was giving me PFN_LIST_CORRUPT, but I got a PAGE_FAULT_IN_NONPAGED_AREA one today.


Any suggestions? Minidumps are attached (I couldn't get the dump application to output). Thanks!

 

[Brink]

Hello bluemouse, and welcome to Seven Forums.

Looking at your dump files, it appears that your BSODs may be from bad/corrupted memory (RAM).

I'm a bit new with debugging BSODs, but for now you might use the tutorial below run Memtest86+ at boot to test your RAM to see if they may be bad or not.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
​

3 of your dumps show this:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffbd7e300001b, 0, fffff80002a70d7f, 7}
 
Could not read faulting driver name
[B][SIZE=3]Probably caused by : [COLOR=red]memory_corruption[/COLOR][/SIZE][/B] ( nt!MiAgeWorkingSet+425 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffbd7e300001b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a70d7f, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)

2 of your dumps show this:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, 1f6724, 1f04f, 0}
*** WARNING: Unable to verify checksum for win32k.sys
[B][SIZE=3]Probably caused by : [COLOR=red]ntkrnlmp.exe[/COLOR][/SIZE][/B] ( nt! ?? ::FNODOBFM::`string'+16b66 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000001f6724, page frame number
Arg3: 000000000001f04f, current share count
Arg4: 0000000000000000, 0

 

[bluemouse]

Thanks, I'll give that a try.