Can anyone give me a hand with these bluescreens?

[Shaina]

Hi.

Recently I've been having random bluescreens, and I can't figure out why. It usually happens while playing a random game (It has happened in every game except WoW so far -- Starcraft II and Crysis in particular) and when watching movies (DivX, flowplayer and YouTube). First I thought it was because of my overclock, but after setting my BIOS to fail-safe standard settings I found myself encountering another bluescreen today, while watching a movie.

I've read the minidump file in WinDbg and it says the bluescreens are probably caused by memory_corruption. After searching around a bit it seems like this can come from all kinds of different applications so I don't really know which one it is.

The bluescreens vary in frequency but lately I've had more of them than what I had in the start. Some months ago I'd get one bluescreen every 2-3 weeks, but so far this week I've had 2.

Here's the full minidump read from WinDbg:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022711-18657-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`03052e50
Debug session time: Sun Feb 27 06:01:42.242 2011 (UTC + 1:00)
System Uptime: 0 days 4:07:46.678
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, a7ab, 3, 45ab9}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

Thanks in advance for any assistance.

[Nickle]

Download and run memtest86

I think your ram may have some problems...

[ayako]

Upload the minidump somewhere, I'll take a look

[Jurwi]

Download and run memtest86

I think your ram may have some problems...

^- Start by doing this.

[Deleted]

Memtest is certainly an option - would also make sure you're running the latest graphics drivers - had some major problems running NVidia graphics card with some of the more recent drivers and had to run RivaTuner software to make sure the Fans were operating at more than basic levels during graphic intensive zones.

[Erous]

Are you overclocking? I was overclocking my Phenom II 965 for awhile with no issues, then began receiving sporadic blue screens out of nowhere. And they would primarily happen while gaming, but would be few and far between, but noticeable. I stopped OC'ing and it cleared right away.

Although the above suggestion from the other posters may serve a better purpose.

[Deleted]

I have just been through the same thing so i will ask you one thing are you running any apps that use Java while this is happening? After every test and reinstall of OS i eventually found out it was Java that was screwing me over so i manually downloaded the newest version as for some reason MS has not released it for Vista/7 yet.

[Shaina]

Ugh, sorry for a slow reply, I've been very busy.

Anyway, I've ran memtest86 4 times and all tests passed with no errors. I've also ran Prime95 torture test for 10+ hours with no errors.

To answer some questions:

@ayako: I would upload it, but somehow I can't compress the minidump file to a .zip because it's write-protected or I lack privileges, even though I'm on the admin user. Any idea how to resolve it?

@Erous: I was, but I reset my overclock and my CPU/RAM is now at stock voltages and frequencies (Did it both through BIOS and by taking out the CMOS-battery). The issue is still here, though, and when I had the overclock I had tested it thoroughly and all signs pointed to it being stable.

@Romandix: Not always, but on some of the bluescreens yes. Thanks though, I'll try it out and report back if it resolves the issue.

If anyone else has any idea what it could be or how to fix it, please let me know. All the minidump files says that the issue is most likely caused by memory_corruption, and it doesn't happen while using any specific application, it happens while using a different application most of the time.

Edit: Here's the latest minidump with a bit more information than the old one:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030311-15272-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e50
Debug session time: Thu Mar  3 10:46:02.756 2011 (UTC + 1:00)
System Uptime: 0 days 1:24:49.192
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 3606c, 3, 14ae}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

0: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000003606c, page frame number
Arg3: 0000000000000003, current page state
Arg4: 00000000000014ae, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f5c38c to fffff80002ecc740

STACK_TEXT:  
fffff880`07c0e778 fffff800`02f5c38c : 00000000`0000004e 00000000`00000099 00000000`0003606c 00000000`00000003 : nt!KeBugCheckEx
fffff880`07c0e780 fffff800`02f3e6a9 : 00000000`00000000 fffff680`000ba978 00000000`00000000 fffff700`012a7ff8 : nt!MiBadShareCount+0x4c
fffff880`07c0e7c0 fffff800`02efd381 : fffff700`01080000 fffff680`000bad50 fffffa80`050ef270 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31ed3
fffff880`07c0e970 fffff800`02f0e0da : 00000000`00000000 00000000`175aafff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`07c0eb30 fffff800`02ecb993 : ffffffff`ffffffff 00000000`0014de10 00000000`0014de08 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`07c0ec20 00000000`7720f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014ddd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7720f89a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f5c38c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Also, if it matters, here are my computer specs:

CPU: Intel i5 750
GPU: Sapphire Radeon HD 5770
RAM: Corsair XMS3 DDR3 4GB 1600 MHz CL9
HDD: WD Caviar Black 750 GB
MOBO: Gigabyte GA-P55-USB3
PSU: Corsair TX 750W
OS: Windows 7 64bit

[ayako]

I'd only need the minidump. Copy it out and zip it up.

[Shaina]

I'd only need the minidump. Copy it out and zip it up.

http://www.mediafire.com/?x33i8qarfestrut

[ayako]

Ok narrowed down the cause to PFN_LIST_CORRUPT so either the location where pagefile.sys is corrupted or your memory has gone bad.

[Nickle]

I would run at least 6 passes of memtest86. Try running Prime95 on Large FFT's for a couple hours, or LinX (reboot your computer, close any applications that aren't needed and then run max memory for 20 passes)

I'm almost certain you got a bad stick in there.

[Deleted]

I had the same problem as the OP a year or so ago. I had it for a few months and decided to check it out. I had several different blue screen issues that always pointed to the memory. I did memtest many times coming up clean with no errors.

I took my PC apart cleaned it out of dust etc and put it back together again making sure everything was fully in and I haven't had a blue screen since (for a year). When putting things back I realised that my graphics card fitting (no-screw design) didn't keep the graphics card fully in the slot. I have no idea whether this caused or helped cause the problem but either way a simple dismantle and check stopped the BSOD from happening. I really hope if you do something similar the problem will go away.

It seemed that even though the BSOD was the warning they gave me the problem itself wasn't directly linked the memory. It could be that a component was faulty and paused sending information unexpectedly and the PC went BSOD to protect it.

but that is purely speculation. Either way good luck.