PC Freezes and makes Buzzing Noise when Running Programs

Problem Devices:

Code:

Microsoft PS/2 Mouse	ACPI\PNP0F03\4&242CC0DB&0	This device is not present, is not working properly, or does not have all its drivers installed.

Security Software (just to check that you have it and it is working properly; nothing needs to be done with this information at this time):

Code:

avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	1188	8	200	1380	07/04/2012 09:30	12.0.0.374	197.55 KB (202,296 bytes)	25/04/2011 00:15
avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	2448	8	200	1380	07/04/2012 09:31	12.0.0.374	197.55 KB (202,296 bytes)	25/04/2011 00:15

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\sjc1138\Windows_NT6_BSOD_jcgriff2\040712-22261-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03e57000 PsLoadedModuleList = 0xfffff800`0409b650
Debug session time: Sat Apr  7 02:28:10.987 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:52.750
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8886, fffffa8001493550, fffffa80010fd9a0, 504}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008886, The subtype of the bugcheck.
Arg2: fffffa8001493550
Arg3: fffffa80010fd9a0
Arg4: 0000000000000504

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


BUGCHECK_STR:  0x1a_8886

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  wmi64.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003ee45cc to fffff80003ed3d40

STACK_TEXT:  
fffff880`072cf738 fffff800`03ee45cc : 00000000`0000001a 00000000`00008886 fffffa80`01493550 fffffa80`010fd9a0 : nt!KeBugCheckEx
fffff880`072cf740 fffff800`03eb4a74 : fffff8a0`01929488 fffffa80`01493550 00000000`00000000 fffff8a0`01929488 : nt!MiUnlinkPageFromLockedList+0x19c
fffff880`072cf7c0 fffff800`041aea21 : fffffa80`06b2e250 fffff6fc`40020bd0 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x244
fffff880`072cf870 fffff800`041aeb60 : ffffffff`ffffffff 00000000`00000001 fffff8a0`01a03410 00000000`00000001 : nt!MiSwitchBaseAddress+0x61
fffff880`072cf8a0 fffff800`041cf73f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`072cf8f0 fffff800`041ae2a6 : fffff880`072cfb40 fffff880`072cfc60 00000000`00000000 fffff880`072cfb38 : nt!MmCreateSection+0x2df
fffff880`072cfaf0 fffff800`03ed2fd3 : fffffa80`07f9bb60 00000000`0012de08 fffff880`072cfb88 00000000`0012dfd8 : nt!NtCreateSection+0x171
fffff880`072cfb70 00000000`77cc17ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012dde8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cc17ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+19c
fffff800`03ee45cc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+19c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c

BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c

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

Does point to memory problems.

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
  
  
• I would also recommend downloading and installing all available Intel, Realtek, and NVIDIA drivers from Download

So you have two modules of 2GB each? Are they both the exact same brand, timings, bought at the same time as a kit, etc.?

Have you tried removing one module and seeing if Windows runs stable on just one module at a time. The goal is to do the same thing as in Part 3 of the Memtest86+ tutorial except instead of testing each module and slot by running Memtest86+, you test by doing your normal routine in Windows and see if Windows still crashes. If it does, either the module or the slot being tested is bad. If Windows is stable, the module and slot are good.

Avoid Static Damage to Your PC when swapping memory modules.

Windows may be a better method to test the RAM. While Memtest86+ has effective testing, it does not stress the RAM in the same way that Windows does, so sometimes it does not catch errors as well as just doing your normal routine in Windows might. See if one module/slot allows Windows to run without crashing.