BSODs after upgrading to 16GB of RAM

onlywar

Posts: 13   +0
Hi
I upgraded my ram to 16GB than I started get BSOD
- I clean my computer weekly
- I test memorey using Memtest86+ but no errors
- I test ram slots it seems there are a problem with all four slots installed or with slot 4 some times
- I updated my drivers and software to latest versions
- My bios is the latest version

Operating System
MS Windows 7 Ultimate 64-bit SP1
Motherboard
BIOSTAR TA790GX A3+ Ver. 5.x
Processor
AMD Phenom II X4 965 BE Deneb 45nm Technology
Cooler
ASUS Silent Square EVO
PowerSupply
PC Power&Cooling Silencer 750W


CASE:
Asus Vento A1 gaming chassis
RAM

G-SKILL F3-12800CL9Q-16BZL
DDR3-1600 CL9-9-9-24 1.50V
PC3-12800 4GX4 INTEL XMP READY

Dual-Channel DDR3 @ 3400MHz (11-11-11-28)



Graphics
LCD SyncMaster (1920x1080@60Hz)
ATI Radeon HD 5800 Series (ATI)


Hard Drives
932GB Western Digital WDC WD1001FALS-00J7B1 ATA Device (SATA)
596GB Western Digital WDC WD6401AALS-00L3B2 ATA Device (SATA)

Minidump:
On Wed 01:50:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800EA54680, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 18:33:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-30201-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x4E (0x99, 0x3CC9A6, 0x2, 0x2F4868)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 16:48:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-23025-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0x814F001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


thanks in advance for any help or advice
 

Attachments

The attached file is corrupt.
932GB Western Digital WDC WD1001FALS-00J7B1 ATA Device (SATA)
596GB Western Digital WDC WD6401AALS-00L3B2 ATA Device (SATA)

Is this hard drive free space?
 
Attached the mini-dump files again, try it


932GB Western Digital WDC WD1001FALS-00J7B1 ATA Device (SATA)
596GB Western Digital WDC WD6401AALS-00L3B2 ATA Device (SATA)

hard disks space 1TB and 600GB
 

Attachments

PFN_LIST_CORRUPT (This error is typically caused by a driver passing a bad memory descriptor list)
and MEMORY_MANAGEMENT
So we could really be chasing a bad or errant driver. What antivirus program are you running?
 
:(
BSOD ( bad_pool_caller)
Than after restart during windows login I got this BSOD ( driver_irq_not_less_or_equal)
I tried to access safe mode but after login I got this BSOD ( problem has been detected )
I tried again to log into normal windows but no luck BSOD ( bad_pool_header) !

Please help !

Ok I tired to log into normal windows I got this (A problem has been detected
Stop 0x024
Ntfs.sys )???

After trying
no BSOD so far :) (y)
I tested ram with memtest86+ for over 10 hours with no errors
 
This "memory" problem is probably caused by a bad device driver. Do you see any yellow exclamation points in the device manager?
 
No I don't see any yellow points.

Today I installed my old Kingston hyperx 2x2Gb ram and it's work perfect without BSOD until now !

Also I found dmp file called memory ( 670 Mb ! ), do you need it to diagnose ..?
 
This file is 140MB... way too big! Go to C:\windows\minidump. Minidump files have a .dmp extension. Select all the files with a .dmp extension. Right-click and send to a compressed(zipped)folder. Upload that folder as a file here... simple and effective :confused:
 
I already attached minidump files in first post but it's
24.07.2012 - date modified - ??

it's not new as the memory problem (10.9.2012 - 15.09.2012)
 

Attachments

note : on Saturday I installed my old Kingston hyperx 2x2Gb ram ;
Until now I didn't get any BSOD !!
 
Back