BSOD after upgrade memory

siwsy · 29 Apr 2011

Recently I have been replaced my current RAM to 4GB, 2 pc of Kingston with 2GB each (KVR800D2N6). However, ever since then, the display blink/flash occasionally and the PC BSOD very frequently.

Technical info:
*** STOP: 0x000000D1 (0x00A5F9B2, 0x00000002, 0x00000001, 0x9415A4B7)
*** RTL85n86.sys - Address 9415A4B7 base at 94022000, DateStamp 4b9d974c

What is this RTL85n86.sys? Before the upgrade of RAM there is no such problem. Could the new RAM incompatible with the system?

I had upload the dump report and perfmon report as instructed. Could somebody help to check.

My PC Spec:
ACER ASPIRE M5640
MS Window 7 Home Premium 32 bit
Version 6.1.7601 Service Pack 1 Build 7601
4GB DDR2 RAM (upgraded from 2GB)

SledgeDG · 29 Apr 2011

hi siwsy and welcome to SF!
I took a look at your dump and indeed it seems as if your Realtec wireless drivers are the probable cause here...

Code:

RTL85n86.sys Sun Mar 14 22:11:24 2010 (4B9D974C)

since they're over a year old, try updating them from here
Realtek

Code:

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


Loading Dump File [C:\Users\David\Desktop\Windows_NT6_BSOD_jcgriff2\042911-44257-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82a45000 PsLoadedModuleList = 0x82b8f850
Debug session time: Fri Apr 29 01:16:14.063 2011 (GMT-4)
System Uptime: 0 days 1:31:52.796
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {a5f9b2, 2, 1, 9415a4b7}

Unable to load image \SystemRoot\system32\DRIVERS\RTL85n86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL85n86.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL85n86.sys
Probably caused by : RTL85n86.sys ( RTL85n86+1384b7 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00a5f9b2, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9415a4b7, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82baf718
Unable to read MiSystemVaType memory at 82b8f1a0
 00a5f9b2 

CURRENT_IRQL:  2

FAULTING_IP: 
RTL85n86+1384b7
9415a4b7 6689912a020000  mov     word ptr [ecx+22Ah],dx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  82b6da9c -- (.trap 0xffffffff82b6da9c)
ErrCode = 00000002
eax=86a63000 ebx=86cef7d0 ecx=00a5f788 edx=0000000f esi=868e90e0 edi=00000000
eip=9415a4b7 esp=82b6db10 ebp=82b6db38 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
RTL85n86+0x1384b7:
9415a4b7 6689912a020000  mov     word ptr [ecx+22Ah],dx   ds:0023:00a5f9b2=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 9415a4b7 to 82a865cb

STACK_TEXT:  
82b6da9c 9415a4b7 badb0d00 0000000f 87ef6cf8 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
82b6db38 9414a152 86a63000 86ce7360 82b6db58 RTL85n86+0x1384b7
82b6db48 9414a2ba 86a63000 86ce7360 82b6db94 RTL85n86+0x128152
82b6db58 941248cd 86a63000 86ce7360 86ce7758 RTL85n86+0x1282ba
82b6db94 94125e4f 86a5f788 86ce76f0 86ced004 RTL85n86+0x1028cd
82b6dc04 9412965d 86a5f788 86a5f788 82b6dc50 RTL85n86+0x103e4f
82b6dc14 8beea89a 86a5f788 00000000 82b6dc40 RTL85n86+0x10765d
82b6dc50 8be95a0f 86cef7e4 00cef7d0 00000000 ndis!ndisMiniportDpc+0xe2
82b6dc78 82abd1b5 86cef7e4 86cef7d0 00000000 ndis!ndisInterruptDpc+0xaf
82b6dcd4 82abd018 82b70d20 82b7a380 00000000 nt!KiExecuteAllDpcs+0xf9
82b6dd20 82abce38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b6dd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTL85n86+1384b7
9415a4b7 6689912a020000  mov     word ptr [ecx+22Ah],dx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  RTL85n86+1384b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTL85n86

IMAGE_NAME:  RTL85n86.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9d974c

FAILURE_BUCKET_ID:  0xD1_RTL85n86+1384b7

BUCKET_ID:  0xD1_RTL85n86+1384b7

Followup: MachineOwner
--------

Report back with any new information
-DG

siwsy · 30 Apr 2011

Hi SledgeDG, thanks for replying.

In fact I had also checked the wireless driver, but found that my driver already the latest. The one on the Realtek website is version 1122 release on 25 Jan 2010, but mine is version 1123 release on 26 Feb 2010. I'm not sure where I got the driver already but this seems newer than the one published on Realtek, and it work fine for 1yr until recently.

Attached my driver screenshot.

marsmimar · 30 Apr 2011

I'd suggest reinstalling your original RAM and see if the BSOD continues to happen. If not, one of your new Kingstons might be bad. You could try running one stick at a time in Slot 1 to see if one of them causes the BSOD.

SledgeDG · 30 Apr 2011

Before you switch back memory, I would try this (if the memory is bad, this test will find it then you can just try and RMA it with Kingston)

RAM - Test with Memtest86+

If switching back the memory doesn't help, uninstall the wireless adapter via device manager and re install it. That is to ensure it's not the driver itself that has become corrupted somehow.
RTL85n86.sys is a 3rd party driver so a sfc/scannow wouldn't fix it.

-DG

siwsy · 30 Apr 2011

Had run Memtest86+ on new memory overnight and there is no error detected over 7pass. Now I had switch back the old memory and will monitor if it will give error. If it doesn't means the new memory got problem? But can't be detected by memtest86

.

marsmimar · 01 May 2011

siwsy said:

Had run Memtest86+ on new memory overnight and there is no error detected over 7pass. Now I had switch back the old memory and will monitor if it will give error. If it doesn't means the new memory got problem? But can't be detected by memtest86

.

As I understand it, the Kingston memory might not be bad. It just may not be compatible with your machine. Did you use the Kingston memory search (upper right of home page) before buying the new sticks to find out exactly what your machine needs?

http://www.kingston.com/

If the specs are correct then you might want to contact Kingston tech support to see what they have to say.

http://www.kingston.com/support/

siwsy · 02 May 2011

Ya.. I kind of suspect is compatibility problem as after I switch back my old memory last night, no BSOD till now. Before I bought the RAM, already check that my machine can support DDR2-800, and from the kingston website, the upgrade path stated: "Virtually any configuration up to 4GB can be reached using any combination of Kingston's 512MB, 1GB, and 2GB modules. ". Hence I see no reason why there is compatibility issue. Anyway will try to contact kingston support.

marsmimar · 02 May 2011

Kingston is pretty good about honoring their product warranties. If you hear back from them could you update this post to let us know what the final outcome is? It might help others with similar problems in the future.

siwsy · 15 May 2011

I had tried swapping different single Kingston RAM in different slot as instructed by Kingston support. It work perfectly fine as long as I put only 1 piece. However, when I put 2 piece together, the PC display start flickering and crash BSOD within 4hours. Does it means my PC cannot support 4GB RAM? According to the spec it should be able to.