Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent BSOD after installing new RAM

04 Jul 2014   #1
jayquicko

Windows 7 Ultimate x64
 
 
Frequent BSOD after installing new RAM

Hi,

I have been getting frequent BSODs after installing new set of 2 2gb ram sticks. I can't tell if the problem is on the memory or the motherboard. Can you help me out on this one.

Thanks.

Here are the details of the BSOD after installing the new RAM.

On Sat 7/5/2014 12:02:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070514-24273-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8006F5D0E0, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 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 that cannot be identified at this time.



On Sat 7/5/2014 12:02:30 AM 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, 0xFFFFFA8006F5D0E0, 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 that cannot be identified at this time.



On Fri 7/4/2014 7:42:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070514-26878-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFF680001228A0, 0x0, 0x0, 0xFFFFF80002EA4AE2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 7/4/2014 9:30:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-23992-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003195121, 0xFFFFF8800A0E9120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 7/4/2014 8:40:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-25178-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6ECD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000776ECD, 0xFFFFF8800381FAD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 7/4/2014 7:46:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-22464-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFF808031018F8, 0xC, 0x0, 0xFFFFF80002ED9115)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/3/2014 5:00:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-27690-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x17C6)
Bugcheck code: 0xD1 (0xFFFFFA802754C34C, 0x2, 0x1, 0xFFFFF88000C017C6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 7/3/2014 7:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070314-22822-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFFA801B1E97E0, 0x2, 0x1, 0xFFFFF80002ED2B4F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 7/2/2014 11:18:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070314-22276-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFA808A2039C0, 0x0, 0xFFFFF80002EE00A9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 7/2/2014 5:27:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-25896-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88010B60EBD)
Bugcheck code: 0x50 (0xFFFFF8A00E3890F0, 0x1, 0xFFFFF88010B60EBD, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



My System SpecsSystem Spec
.
04 Jul 2014   #2
jayquicko

Windows 7 Ultimate x64
 
 

Oh I forgot. Attached is the zip file for the files grabbed by the SF diagnostic tool.
My System SpecsSystem Spec
Reply

 Frequent BSOD after installing new RAM




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD more frequent
Hello Hope someone can help me before I tear out whats left of my hair. Three weeks ago while playing BF3 on line the screen would freeze and I would have to reboot and it will run fine. A few days the pc would reset and/or freeze. Now I get BSOD whatever task I'm doing. Blue screen viewer...
BSOD Help and Support
Frequent BSOD after installing Alcohol 120
The very moment I installed Alcohol and its virtual drive, I got a BSOD, and they have been frequent since then. I have managed to remove the program and the file SPTD.sys -- and updated all of my outdated drivers -- yet the problem persists. Sometimes when it crashes the HDD 'vanishes' and I...
BSOD Help and Support
Frequent BSOD playing SimCity / Frequent applications crashing
Hello, This has all started since installing EA's Origin in order to play SimCity and Battlefield 3, the later crashes with a BSOD Stop 0x0000001 within about 1 minute of starting, SimCity will give me up to an hour before BSOD'ing. It's 50:50 whether it's a BSOD or a 'SimCity has stopped...
BSOD Help and Support
Frequent and Various BSODs while installing/updating and on Youtube.
Computer Specs: CPU: AMD FX(tm)-8150 Eight-Core Processor Motherboard: Gigabyte Technology Co., Ltd. GA-970A-D3 BIOS: Award Modular BIOS v6.00PG RAM: 16.00 GB HDD: ST2000DM001-9YN164 ATA Device Sound Card: (1) ATI HDMI Audio (2) Realtek High Definition Audio Graphics Card: AMD Radeon HD...
BSOD Help and Support
Frequent 0x0000004 BSOD while gaming or installing or opening
So, I built myself this computer about 6-10 months ago and on initial setup everything was running smoothly, until I started getting BSODs left right and centre, I attributed this to my overclocking and downclocked. I then had trouble booting, as the Bios kept resetting the boot drive to the...
BSOD Help and Support
Frequent crashes (BSOD) on the new PC with BSOD Dump attached
Hi guys, can anyone please help my problem, I had my PC crashing almost everyday, and several times a day. Please find my attached collection of memory dump & PC Health report. Thanks very much! I am on Windows 7 Ultimate x64 - x64 - the original installed OS on the system - Ultimate -...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 12:07.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App