HELP!! BSOD Windows 7 x64 - More Frequent

signosis said:

Hello everyone!

Having major issues with BSOD's!! Please Help?!

I never came across any BSOD's until installing a second set of memory sticks. Long story short: A little reading via SevenForums, memory test, driver checks, and trial 'n' error...Turned out that upping the memory voltage appeared to do the trick. Everything ran stable and smooth.

UNTIL TODAY! The system seems a little sluggish and has crashed 5 times within the past hour or so. 4 of which has something to deal with a "PFN_LIST_CORRUPT" error.

During the time of BSOD's, I wasn't doing anything intensive except for using a few Adobe Creative Suite CS5 products, Firefox, and FileZilla. Although, I have noticed Firefox crashing more often than usual of late. Could this be related?

All of these error and bug codes look like spaghetti to me. It would be great if anyone can help me in resolving this issue.

I've attached the files created by the "BSOD Dump & System File Collection app" but couldn't do a "perfmon / report" as it gave me a "The parameter is incorrect" message.

If any other information is needed, please let me know. Much appreciate everyone. Thank you!

System Specifications:

Windows 7 x64 Retail
AMD Phenom II X4 925
Asus M4A785TD-V EVO
Corsair XMS CMX4GX3M2A16008 (2x4GB)
BFG Geforce GTS 250
Creative SB Audigy Platinum

Note: Nothing overclocked except for memory voltage adjustment to 1.65v.

There is no DMP file in the folder. Can you

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.


BTW the PFN is memory related. I can tell you more when we have the DMP file.

To test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

zigzag3143 said:

There is no DMP file in the folder. Can you

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.


BTW the PFN is memory related. I can tell you more when we have the DMP file.

To test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Jonathan_King said:

Ken- his minidump folder is empty.

See this article: Tech Support Forum - View Single Post - Blue Screen of Death (BSOD) Posting Instructions

Sorry about that guys. Re-edited the post with additional info and minidump attachment files. Hope that helps.

Thanks!

Jonathan_King said:

The dumps are pointing to memory corruption, which is usually a bad driver. It didn't point to a specific one, unfortunately.

As a troubleshooting step, please remove Avast and replace it with Microsoft Security Essentials. 3rd party AV programs are famous for causing BSODs in Vista and 7, and they are not always blamed directly.

Avast removal tool: http://files.avast.com/files/eng/aswclear5.exe

MSE: http://www.microsoft.com/security_essentials

Enable driver verifier to hopefully point to the faulty driver: Using Driver Verifier to identify issues with Drivers

Memory corruption can also be caused by bad RAM. Your choice- want to run a memory test? If so, download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. It will take several hours, or run it overnight.

I may ask you to run the test later, if you don't do it now and the Verifier-enabled dumps don't point to a specific driver.

...Summary of the Dumps:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 15:46:42.362 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:29.126
BugCheck 4E, {99, 1ce218, 0, 1cdd18}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 15:14:21.843 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:24.217
BugCheck 4E, {99, 1cb4aa, 2, 1cb4a5}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 14:43:34.660 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:18.033
BugCheck 4E, {99, 9ebea, 0, 9f1ea}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Dreamweaver.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 14:27:41.644 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:36.017
BugCheck 1E, {ffffffffc0000005, fffff880038024eb, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 14:15:28.509 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:47.883
BugCheck 4E, {99, 15d7f0, 3, 165975}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  plugin-contain
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

JK,

Will definitely start on the suggested steps as soon as I'm done with this post.

FYI: As far as bad memory? There seems to be no issues when installing either set of paired memory sticks. Nor is there an issue when installing any pair plus any additional one memory stick. But the issues do occur when all 4 sticks are installed. All properly installed in the correct slots and all matching pairs with the same latency.

Much appreciated. I'll post the results as soon as possible. Thanks again!

JK,

PROBLEM SOLVED: So far, so I am assuming.

Steps taken:
1. Uninstalled Avast (using control panel - not in safe mode)
2. Loaded Verifier per Link posted (rebooted)
3. Did a second reboot to access safe mode but crashed
4. System "initiated" a system restore (proceeded)
5. Did a "second" uninstall with Avast Removal in safe mode
6. Rebooted and started memtest86

*The test failed around test 5. I then noticed the memory settings during test. It turns out the memory settings were overclocked? How? Not sure. Something I overlooked and probably at fault, though I do not recall playing with these settings.

7. Started memtest86 again and passed all tests

*The system appears to be stable again so I'll probably reinstall Avast and see how everything goes.

But, as far as the initial BSOD errors that occurred after the additional memory installation? A simple up in voltage did the trick.

Lesson learned for me? Something as simple as overlooking your bios settings and using memtest86.

I'll definitely see how everything goes and keep you posted. I appreciate the help. Thanks again JK!

Cheers.

Jonathan_King said:

Thanks for the update. Glad it's all good now!

If you need anything else, we are more than willing to help.

~JK

Hey JK,

Just had another BSOD! Everything's been well until a few minutes ago. Same PFN_List_Corrupt error.

Where we left off and prior to today's crash:

1. Verifier loaded
2. Memtest86 Passed 100%
3. Avast still uninstalled
4. Firefox update to ver 3.6.8
*No major updates or installations*

During and after crash:

1. Firefox (Only "open" program in use)
2. Firefox crashed then BSOD'd
3. System rebooted
4. Restarted Firefox
5. Firefox crashed again but with no BSOD this time around
6. Restarted Firefox, again
7. Firefox then displayed a "Flash plugin error"
*During the crash, flash content was being loaded into the browser*

FYI: Adobe Flash and/or flash content was loaded and/or being loaded into the browser during the previous crashes as well.

Any known process conflicts with Firefox and flash that might be causing the BSOD's?

Current Firefox and Flash installed:

Current: Firefox 3.6.8 (Just installed prior to crash)
Previous: Firefox 3.6.6
Flash Plugin: Shockwave Flash 10.1 r53 (10.1.53.64)

I'll do another memtest and post the results. In the mean time ive attached the latest dmp file. Much thanks and cheers!

signosis said:

Jonathan_King said:

Thanks for the update. Glad it's all good now!

If you need anything else, we are more than willing to help.

~JK

Hey JK,

Just had another BSOD! Everything's been well until a few minutes ago. Same PFN_List_Corrupt error.

Where we left off and prior to today's crash:

1. Verifier loaded
2. Memtest86 Passed 100%
3. Avast still uninstalled
4. Firefox update to ver 3.6.8
*No major updates or installations*

During and after crash:

1. Firefox (Only "open" program in use)
2. Firefox crashed then BSOD'd
3. System rebooted
4. Restarted Firefox
5. Firefox crashed again but with no BSOD this time around
6. Restarted Firefox, again
7. Firefox then displayed a "Flash plugin error"
*During the crash, flash content was being loaded into the browser*

FYI: Adobe Flash and/or flash content was loaded and/or being loaded into the browser during the previous crashes as well.

Any known process conflicts with Firefox and flash that might be causing the BSOD's?

Current Firefox and Flash installed:

Current: Firefox 3.6.8 (Just installed prior to crash)
Previous: Firefox 3.6.6
Flash Plugin: Shockwave Flash 10.1 r53 (10.1.53.64)

I'll do another memtest and post the results. In the mean time ive attached the latest dmp file. Much thanks and cheers!

Hate to say this because you have run memtestx86, but this crash was caused by memory corruption. I wonder how many passes of memtest were run and if the memory was tested one stick at a time, and if the mobo slots were tested with a known good ram stick.

Ken
Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\072310-18907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`0329ce50
Debug session time: Fri Jul 23 16:17:13.824 2010 (GMT-4)
System Uptime: 0 days 0:59:17.572
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8eb65, 0, ac665}

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

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

3: 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: 000000000008eb65, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000ac665, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000315f2bc to fffff800030cf600

STACK_TEXT:  
fffff880`0a180f98 fffff800`0315f2bc : 00000000`0000004e 00000000`00000099 00000000`0008eb65 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a180fa0 fffff800`03141937 : 00000000`00000000 fffff680`000273c0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0a180fe0 fffff800`030a3b43 : fffffa80`06df2b30 fffff700`00001e57 0000007f`fffffff8 fffff8a0`0a68cc60 : nt! ?? ::FNODOBFM::`string'+0x3227e
fffff880`0a181070 fffff800`030a25a2 : fffffa80`06df2b30 fffffa80`00000000 fffff880`00001330 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0a181920 fffff800`033b5c4f : fffff8a0`0b751a10 fffff880`0a181c20 00000000`00000000 fffffa80`0730c060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0a181970 fffff800`0338e4d1 : 00000000`00000001 00000000`00000001 00000000`7ef92000 fffffa80`072f0760 : nt!PspExitThread+0x92f
fffff880`0a181a30 fffff800`030ac0e3 : 00000000`00000100 fffffa80`0730c120 00000000`00000001 fffff800`030d695d : nt!PsExitSpecialApc+0x1d
fffff880`0a181a60 fffff800`030ac520 : 00000000`00000000 fffff880`0a181ae0 fffff800`0338e5dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0a181ae0 fffff800`030ce8f7 : fffffa80`0730c060 00000000`00000294 fffff880`0a181bf8 fffffa80`06cf4b70 : nt!KiInitiateUserApc+0x70
fffff880`0a181c20 00000000`735a2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`03a4eae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x735a2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0315f2bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

old drivers needing update

Code:

LVUSBS64.sys        fffff880`06415000    fffff880`06421980    0x0000c980    0x45c4cedc    2/3/2007 14:05:16                        
wacommousefilter.sys        fffff880`045f0000    fffff880`045f8000    0x00008000    0x45d5f401    2/16/2007 14:12:17                        
Rt64win7.sys        fffff880`14bb7000    fffff880`14be9000    0x00032000    0x49a65b0d    2/26/2009 05:04:13                        
spldr.sys        fffff880`014e5000    fffff880`014ed000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`14be9000    fffff880`14bf6000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00fb1000    fffff880`00fbc000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
wacomvhid.sys        fffff880`04556000    fffff880`04558800    0x00002800    0x4a145fd3    5/20/2009 15:53:55                        
PxHlpa64.sys        fffff880`01102000    fffff880`0110de00    0x0000be00    0x4a416253    6/23/2009 19:16:35

zigzag3143 said:

signosis said:

Jonathan_King said:

Thanks for the update. Glad it's all good now!

If you need anything else, we are more than willing to help.

~JK

Hey JK,

Just had another BSOD! Everything's been well until a few minutes ago. Same PFN_List_Corrupt error.

Where we left off and prior to today's crash:

1. Verifier loaded
2. Memtest86 Passed 100%
3. Avast still uninstalled
4. Firefox update to ver 3.6.8
*No major updates or installations*

During and after crash:

1. Firefox (Only "open" program in use)
2. Firefox crashed then BSOD'd
3. System rebooted
4. Restarted Firefox
5. Firefox crashed again but with no BSOD this time around
6. Restarted Firefox, again
7. Firefox then displayed a "Flash plugin error"
*During the crash, flash content was being loaded into the browser*

FYI: Adobe Flash and/or flash content was loaded and/or being loaded into the browser during the previous crashes as well.

Any known process conflicts with Firefox and flash that might be causing the BSOD's?

Current Firefox and Flash installed:

Current: Firefox 3.6.8 (Just installed prior to crash)
Previous: Firefox 3.6.6
Flash Plugin: Shockwave Flash 10.1 r53 (10.1.53.64)

I'll do another memtest and post the results. In the mean time ive attached the latest dmp file. Much thanks and cheers!

Hate to say this because you have run memtestx86, but this crash was caused by memory corruption. I wonder how many passes of memtest were run and if the memory was tested one stick at a time, and if the mobo slots were tested with a known good ram stick.

Ken
Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\072310-18907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`0329ce50
Debug session time: Fri Jul 23 16:17:13.824 2010 (GMT-4)
System Uptime: 0 days 0:59:17.572
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8eb65, 0, ac665}

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

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

3: 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: 000000000008eb65, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000ac665, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000315f2bc to fffff800030cf600

STACK_TEXT:  
fffff880`0a180f98 fffff800`0315f2bc : 00000000`0000004e 00000000`00000099 00000000`0008eb65 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a180fa0 fffff800`03141937 : 00000000`00000000 fffff680`000273c0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0a180fe0 fffff800`030a3b43 : fffffa80`06df2b30 fffff700`00001e57 0000007f`fffffff8 fffff8a0`0a68cc60 : nt! ?? ::FNODOBFM::`string'+0x3227e
fffff880`0a181070 fffff800`030a25a2 : fffffa80`06df2b30 fffffa80`00000000 fffff880`00001330 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0a181920 fffff800`033b5c4f : fffff8a0`0b751a10 fffff880`0a181c20 00000000`00000000 fffffa80`0730c060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0a181970 fffff800`0338e4d1 : 00000000`00000001 00000000`00000001 00000000`7ef92000 fffffa80`072f0760 : nt!PspExitThread+0x92f
fffff880`0a181a30 fffff800`030ac0e3 : 00000000`00000100 fffffa80`0730c120 00000000`00000001 fffff800`030d695d : nt!PsExitSpecialApc+0x1d
fffff880`0a181a60 fffff800`030ac520 : 00000000`00000000 fffff880`0a181ae0 fffff800`0338e5dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0a181ae0 fffff800`030ce8f7 : fffffa80`0730c060 00000000`00000294 fffff880`0a181bf8 fffffa80`06cf4b70 : nt!KiInitiateUserApc+0x70
fffff880`0a181c20 00000000`735a2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`03a4eae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x735a2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0315f2bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

old drivers needing update

Code:

LVUSBS64.sys        fffff880`06415000    fffff880`06421980    0x0000c980    0x45c4cedc    2/3/2007 14:05:16                        
wacommousefilter.sys        fffff880`045f0000    fffff880`045f8000    0x00008000    0x45d5f401    2/16/2007 14:12:17                        
Rt64win7.sys        fffff880`14bb7000    fffff880`14be9000    0x00032000    0x49a65b0d    2/26/2009 05:04:13                        
spldr.sys        fffff880`014e5000    fffff880`014ed000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`14be9000    fffff880`14bf6000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00fb1000    fffff880`00fbc000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
wacomvhid.sys        fffff880`04556000    fffff880`04558800    0x00002800    0x4a145fd3    5/20/2009 15:53:55                        
PxHlpa64.sys        fffff880`01102000    fffff880`0110de00    0x0000be00    0x4a416253    6/23/2009 19:16:35

As much as I hate too, I'll test each stick alone. Thanks for the heads up Z.