Multiple BSOD when I play music, memory issue?

[nos302]

Windows 7 Ultimate 64-bit
Gigabyte 880GA-UD3U
AMD Phenom 2 X4 950
Galaxy GTX460 768MB
ADATA DDR3-1333 2G*2
Maxtor 150GB SATA2
WD Caviar Blue 1TB SATA2
PSU: Antec 500W

A month ago I have added two more RAM sticks (ADATA DDR3-1600 4G*2) to my computer. No overclocking and didn't messed up any BIOS stuff, just made sure the dual channel ungauged mode still works.

I've also bought a new harddisk (WD Caviar Blue 1TB SATA3) and installed the current OS onto it.

Since then, I always get BSOD randomly when I listen to music on youtube(using chrome), WMP or VLC Player through the audio jack of my HD monitor.

Passed memtest 3 times, checked disk, ran driver verifier, still have no idea what is going on.

Here is the Minidump files all packed into a zip. The error titles vary but usually are "PFN_LIST_CORRUPT" or "MEMORY MANAGEMENT", and seems to involve ntkrnlmp.exe or ntoskrnl.exe.

Hope someone can help.

 

[Arc]

Hello nos302.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[nos302]

After 2 days of testing, finally got a BSOD.

On the first 24 hrs I checked all non-M$ drivers in Driver Verifier, and got a screen freeze (the cursor also freeze) while I was browsing internet with Firefox. No minidump file created.

After that I checked all except M$ drivers and <unknown> and Macrovision drivers, and got this BSOD with a minidump file. MSINFO32 is also enclosed below.

 

[Arc]

Still it is somehow silent about the cause.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck C1[/COLOR], {fffff9804cd68fd0, fffff9804cd68080, 5d0028, 32}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )

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

According to Carrona.org, STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Usual causes: Device driver, ?Memory

As no device driver is directly traced, we may opt for a memory test. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Also, update your display driver, and stop Nvidia auto update utility daemonu.exe.

Let us know the results.

 

[nos302]

I have done a clean uninstall of the older Nvidia driver and a clean install of the latest Nvidia driver (Nvidia Update is excluded in the installation option).

I have also done memtest, each RAM module got at least 8 passes.

A moments ago I got a BSOD again while I was closing some tabs on my chrome browser (which has 20+ tabs). Didn't run driver verifier after the reinstallation and the memtest anyway here's the dump file.

 

[x BlueRobot]

[B]PFN_LIST_CORRUPT (4e)[/B]

BugCheck 4E, {99, 22511d, 3, 112be4}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiBadShareCount+4c )

STOP 0x0000004E: PFN_LIST_CORRUPT

Usual Causes: Device Driver, Memory

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

How frequent are the BSODs now?

 

[nos302]

With the verifier on for a few days, here comes another BSOD.
Minidump file enclosed.

BSOD frequency: every 2-3 days

 

[Arc]

Uninstall MSE: How to manually uninstall Microsoft Security Essentials 1.0.1963 if you cannot uninstall it by using the Add or Remove Programs item

Then reinstall it: Download: Microsoft Security Essentials - Microsoft Download Center - Download Details
Update MSE regularly. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Scan the system for possible virus infection, with some other tools too.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Take some Disc Checks:

1. Update your SSD's Firmware (skip it, if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

 

[nos302]

Wow, just got another BSOD while I perform Full Scan by the reinstalled Microsoft Security Essential. Now I'm doing the full scan again. I'll scan computer with other softwares tools listed above soon after this.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8887, fffffa80000d7850, fffffa80000d7730, 205}

[COLOR=Red]Probably caused by : hardware_ram[/COLOR] ( ZEROED_PAGE_CORRUPTED )

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

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

[COLOR=Red]MEMORY_MANAGEMENT (1a)[/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008887, The subtype of the bugcheck.
Arg2: fffffa80000d7850
Arg3: fffffa80000d7730
Arg4: 0000000000000205

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


BUGCHECK_STR:  0x1a_8887

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`047cb0c8 fffff800`044ae7ce : 00000000`0000001a 00000000`00008887 fffffa80`000d7850 fffffa80`000d7730 : nt!KeBugCheckEx
fffff880`047cb0d0 fffff800`044ce3fb : fffffa80`000d7850 fffff800`046d0540 00000000`00000000 00000000`00000000 : nt!MiUnlinkPageFromLockedList+0x1de
fffff880`047cb150 fffff800`044bb02f : 00000000`00000000 16000000`047d7860 00000000`00000001 fffff800`046d0540 : nt!MiResolveTransitionFault+0x16b
fffff880`047cb1e0 fffff800`044ab00b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000008 : nt!MiDispatchFault+0x95f
fffff880`047cb2f0 fffff800`0449c0ee : 00000000`00000000 fffff800`047d7000 fffff800`047c8a00 00000000`00000000 : nt!MmAccessFault+0xe1b
fffff880`047cb450 fffffa80`1013cbcf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`047cb5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`1013cbcf


STACK_COMMAND:  kb

SYMBOL_NAME: [COLOR=Red] ZEROED_PAGE_CORRUPTED[/COLOR]

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: [COLOR=Red] hardware_ram[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[COLOR=Red]FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED[/COLOR] 

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

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Let us know the findings.