BSOD When upgrading from 2gb to 4gb Ram [moved from BSOD forum]

3244 Views 14 Replies 5 Participants Last post by Tyree, Mar 29, 2011

ihkbanks

Discussion Starter · Mar 27, 2011

Hello, I've been running 2gb DDR (1 stick) for quite some time now and everything is as smooth as butter but whenever I put in my additional 2gb DDR ram stick (same exact stick) I get blue screens, specifically when playing Starcraft 2. I've ran Memtest and the sticks seem to be in working order. my cpu specs are listed below and my Performance Report/BSOD File Collection info is also attached in zip format.

· Windows 7
· x64
· vista x64 was originally installed
· OS full retail version
· Age of system - 2 Years (hardware)
· Age of OS installation - 1 year

· CPU
AMD Phenom 9950 Quad-Core Processor 2.6ghz
· Video Card- ATI Radeon 3800 series
· MotherBoard- Biostar TA790GX A2+
· Power Supply - corsair 600w

· System Manufacturer - Biostar
· Exact model number I custom Built it

Status: Not open for further replies.

1 - 15 of 15 Posts

mgorman87

· #2 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

You have two dumps from today. One of them is a verifier enabled dump. Please disable driver verifier at this time. Driver Verifier - Enable and Disable - Windows 7 Forums

Please uninstall AVG as it was the cause of the driver verified crash. You may use Microsoft Security Essentials in its place. Use the AVG Removal tool to uninstall the program.

Please update to SP1 - How to update to SP1

Code:

sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)

Please uninstall Daemon Tools. It is a know BSOD maker in Windows 7. Make sure you select uninstall. Daemon Removal Tool

Code:

netr28ux.sys Mon May 25 00:38:17 2009 (4A1A20B9)

Update your Ralink Wireless LAN card - here

Code:

Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)

Update your Realtek network card drivers - here

Code:

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


Loading Dump File [C:\Users\Mike\AppData\Local\Temp\Rar$DI00.971\032711-36909-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50
Debug session time: Sun Mar 27 17:23:10.960 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:11.942
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 610, fffffa80055055b0, fffff88005b447d9}

Unable to load image \??\C:\Program Files (x86)\AVG\AVG9\Identity Protection\Agent\Driver\Platform_WIN764\AVGIDSDriver.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.sys
Probably caused by : AVGIDSDriver.sys ( AVGIDSDriver+167d9 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000610, Handle value being referenced.
Arg3: fffffa80055055b0, Address of the current process.
Arg4: fffff88005b447d9, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  CurseClient.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031013dc to fffff80002c76740

STACK_TEXT:  
fffff880`0394d928 fffff800`031013dc : 00000000`000000c4 00000000`000000f6 00000000`00000610 fffffa80`055055b0 : nt!KeBugCheckEx
fffff880`0394d930 fffff800`03116ae4 : 00000000`00000610 fffffa80`055055b0 00000000`00000003 fffff800`02c7493d : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0394d970 fffff800`02ed1030 : 00000000`00000000 fffff880`0394db60 fffff880`0394dc00 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`0394da50 fffff800`02f24029 : fffff880`05b56200 00000000`00000001 fffffa80`0186cde0 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20b4e
fffff880`0394db20 fffff800`02c75993 : fffffa80`05506b60 00000000`00000000 00000000`00000001 fffff800`00000000 : nt!NtQuerySymbolicLinkObject+0xfc
fffff880`0394dbb0 fffff800`02c71f30 : fffff880`05b447d9 fffff880`05b565b8 00000000`80000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0394dd48 fffff880`05b447d9 : fffff880`05b565b8 00000000`80000000 00000000`00000000 00000000`000000ff : nt!KiServiceLinkage
fffff880`0394dd50 fffff880`05b565b8 : 00000000`80000000 00000000`00000000 00000000`000000ff 00000000`02000000 : AVGIDSDriver+0x167d9
fffff880`0394dd58 00000000`80000000 : 00000000`00000000 00000000`000000ff 00000000`02000000 fffff880`0394dde0 : AVGIDSDriver+0x285b8
fffff880`0394dd60 00000000`00000000 : 00000000`000000ff 00000000`02000000 fffff880`0394dde0 005c003f`003f005c : 0x80000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AVGIDSDriver+167d9
fffff880`05b447d9 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  AVGIDSDriver+167d9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AVGIDSDriver

IMAGE_NAME:  AVGIDSDriver.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be9fb28

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_AVGIDSDriver+167d9

BUCKET_ID:  X64_0xc4_f6_VRF_AVGIDSDriver+167d9

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

Code:

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


Loading Dump File [C:\Users\Mike\AppData\Local\Temp\Rar$DI03.754\032711-19593-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e3fe50
Debug session time: Sun Mar 27 18:41:29.823 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:13.758
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc500574e0, 6000000000f900, fffff68000000003}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc500574e0
Arg3: 006000000000f900
Arg4: fffff68000000003

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  2

TRAP_FRAME:  fffff880029cb0a0 -- (.trap 0xfffff880029cb0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000232
rdx=fffff8a00b524000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800518d135 rsp=fffff880029cb230 rbp=fffff880029cba40
 r8=fffffa8003952208  r9=0000000000000001 r10=0000000006525015
r11=0000000040008c80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x1e5:
fffff880`0518d135 48395f18        cmp     qword ptr [rdi+18h],rbx ds:a400:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c3970e to fffff80002c72740

STACK_TEXT:  
fffff880`029cad48 fffff800`02c3970e : 00000000`0000001a 00000000`00000411 fffff6fc`500574e0 00600000`0000f900 : nt!KeBugCheckEx
fffff880`029cad50 fffff800`02ca47ad : fffff8a0`0ae9ca18 fffff6fc`500574e0 0000007f`fffffff8 00000000`00000041 : nt! ?? ::FNODOBFM::`string'+0x6051
fffff880`029cada0 fffff800`02c8ed26 : 00000000`00000000 fffff880`029cb070 fffff880`00000000 fffff800`02dfeb40 : nt!MiResolveTransitionFault+0x38d
fffff880`029cae30 fffff800`02c8ccf1 : fffff880`029cb120 fffff800`02c787ef fffff800`02dece80 fffffa80`0411db60 : nt!MiDispatchFault+0x946
fffff880`029caf40 fffff800`02c7082e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000004 : nt!MmAccessFault+0x8f1
fffff880`029cb0a0 fffff880`0518d135 : fffffa80`04b2a978 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`029cb230 fffff880`051733e7 : fffffa80`0616c701 fffffa80`0395cb00 00000000`06c60208 fffff880`000000d4 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x1e5
fffff880`029cb320 fffff880`050ebf12 : 00000000`00000000 00000000`00000200 fffff880`029cba40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`029cb370 fffff880`050eb6d7 : fffff8a0`00000001 fffff8a0`03995b60 fffff880`029cb9f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`029cb980 fffff960`0018c9da : 00000000`07c7e6b0 fffffa80`00000200 00000000`07c7fd20 00000000`ffd11000 : dxgkrnl!DxgkRender+0x3e7
fffff880`029cbbf0 fffff800`02c71993 : fffffa80`02e28060 00000000`000002a8 00000000`00000000 fffffa80`02bac870 : win32k!NtGdiDdDDIRender+0x12
fffff880`029cbc20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5
fffff880`0518d135 48395f18        cmp     qword ptr [rdi+18h],rbx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x1a_411_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

BUCKET_ID:  X64_0x1a_411_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

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

Code:

fffff880`00e2f000 fffff880`00e86000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03b07000 fffff880`03b91000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`051da000 fffff880`051f0000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0489d000 fffff880`048e2000   ajslcx2k ajslcx2k.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
fffff880`05310000 fffff880`05324000   amdiox64 amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
fffff880`043ba000 fffff880`043cf000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`011e1000 fffff880`011ec000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`011ae000 fffff880`011b7000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`011b7000 fffff880`011e1000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`053cb000 fffff880`053eb000   AtihdW76 AtihdW76.sys Wed Nov 17 07:02:04 2010 (4CE3C43C)
fffff880`048e3000 fffff880`0511a000   atikmdag atikmdag.sys Tue Jan 04 21:48:52 2011 (4D23DC14)
fffff880`04408000 fffff880`04455000   atikmpag atikmpag.sys Tue Jan 04 21:19:38 2011 (4D23D53A)
fffff880`00ff2000 fffff880`00ffd000   avgfwd6a avgfwd6a.sys Tue Oct 06 18:04:57 2009 (4ACBBF09)
fffff880`05b2e000 fffff880`05b5b000   AVGIDSDriver AVGIDSDriver.sys Tue May 11 20:49:44 2010 (4BE9FB28)
fffff880`05b22000 fffff880`05b2e000   AVGIDSFilter AVGIDSFilter.sys Tue May 11 20:48:52 2010 (4BE9FAF4)
fffff880`017ee000 fffff880`017f8000   AVGIDSwa AVGIDSwa.sys Tue May 11 20:50:03 2010 (4BE9FB3B)
fffff880`0434d000 fffff880`04394000   avgldx64 avgldx64.sys Thu Jun 03 17:06:48 2010 (4C081968)
fffff880`04345000 fffff880`0434c080   avgmfx64 avgmfx64.sys Sun Apr 25 17:06:15 2010 (4BD4AEC7)
fffff880`017e1000 fffff880`017ed0c0   avgrkx64 avgrkx64.sys Wed Feb 10 22:52:44 2010 (4B737F0C)
fffff880`03a71000 fffff880`03ac2000   avgtdia  avgtdia.sys  Thu Jun 03 17:09:57 2010 (4C081A25)
fffff880`017f8000 fffff880`017ff000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`04334000 fffff880`04345000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`05db6000 fffff880`05dd4000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00700000 fffff960`00727000   cdd      cdd.dll      Wed Jan 26 01:31:34 2011 (4D3FBFC6)
fffff880`05a77000 fffff880`05aa1000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c89000 fffff880`00d49000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`015bc000 fffff880`015ec000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c2b000 fffff880`00c89000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0143c000 fffff880`014af000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`051ca000 fffff880`051da000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05aba000 fffff880`05ac8000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04293000 fffff880`04316000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`02336000 fffff880`02338f00   danew    danew.sys    Tue Mar 23 04:37:33 2010 (4BA87DCD)
fffff880`04316000 fffff880`04334000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04284000 fffff880`04293000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`017cb000 fffff880`017e1000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0523d000 fffff880`0525f000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05ad4000 fffff880`05add000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05ac8000 fffff880`05ad4000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05add000 fffff880`05af0000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05aae000 fffff880`05aba000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04455000 fffff880`04549000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 23:22:56 2011 (4D3FA1A0)
fffff880`0511a000 fffff880`05160000   dxgmms1  dxgmms1.sys  Tue Jan 25 23:22:12 2011 (4D3FA174)
fffff880`07000000 fffff880`07036000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`04873000 fffff880`04880000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`0104c000 fffff880`01060000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`05390000 fffff880`0539b000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`014c0000 fffff880`014ca000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01791000 fffff880`017cb000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0168e000 fffff880`016d8000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`05aa1000 fffff880`05aae000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`031e3000 fffff800`0322c000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`05160000 fffff880`05184000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05a1b000 fffff880`05a77000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`043cf000 fffff880`043e8000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`045f2000 fffff880`045fa080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05b14000 fffff880`05b22000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`05cee000 fffff880`05db6000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01788000 fffff880`01791000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04200000 fffff880`0420f000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`053bd000 fffff880`053cb000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bc3000 fffff800`00bcd000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`052cb000 fffff880`0530e000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013cf000 fffff880`013e9000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01663000 fffff880`0168e000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`052c5000 fffff880`052ca200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`0237d000 fffff880`02392000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`02339000 fffff880`0235c000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`05b0f000 fffff880`05b13980   Lycosa   Lycosa.sys   Fri Jan 18 03:51:42 2008 (4790689E)
fffff880`00c0a000 fffff880`00c17000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`02328000 fffff880`02336000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`052ae000 fffff880`052bd000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`053b0000 fffff880`053bd000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`01194000 fffff880`011ae000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`05dd4000 fffff880`05dec000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`05c00000 fffff880`05c2d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`05c2d000 fffff880`05c7b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`05c7b000 fffff880`05c9e000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00ea6000 fffff880`00eb1000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e86000 fffff880`00e90000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01060000 fffff880`010be000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`04279000 fffff880`04284000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01776000 fffff880`01788000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014ca000 fffff880`015bc000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`051f0000 fffff880`051fc000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`023e5000 fffff880`023f8000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`0456d000 fffff880`0459c000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0539b000 fffff880`053b0000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03bd6000 fffff880`03be5000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03ac2000 fffff880`03b07000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01603000 fffff880`01663000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02227000 fffff880`0231b000   netr28ux netr28ux.sys Mon May 25 00:38:17 2009 (4A1A20B9)
fffff880`00fe1000 fffff880`00ff2000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0426d000 fffff880`04279000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c06000 fffff800`031e3000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`0122c000 fffff880`013cf000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01428000 fffff880`01431000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02392000 fffff880`023e5000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`03b9a000 fffff880`03bc0000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`04880000 fffff880`0489d000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`010f7000 fffff880`0110c000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`010c4000 fffff880`010f7000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0117d000 fffff880`01184000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`01184000 fffff880`01194000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`014af000 fffff880`014c0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`07083000 fffff880`07129000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05200000 fffff880`0523d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c17000 fffff880`00c2b000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04549000 fffff880`0456d000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0459c000 fffff880`045b7000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`045b7000 fffff880`045d8000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`045d8000 fffff880`045f2000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0421c000 fffff880`0426d000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`043e8000 fffff880`043f3000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`01431000 fffff880`0143a000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`013f7000 fffff880`01400000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00e9d000 fffff880`00ea6000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0173c000 fffff880`01776000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02200000 fffff880`02218000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05184000 fffff880`051b6000   Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
fffff880`00e00000 fffff880`00e2f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`07129000 fffff880`07134000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04867000 fffff880`04873000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03a00000 fffff880`03a1d000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`052bd000 fffff880`052c5000   serscan  serscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`01734000 fffff880`0173c000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`00eb2000 fffff880`00fd8000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`05b5b000 fffff880`05bf1000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07173000 fffff880`071da000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`07134000 fffff880`07161000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`0530e000 fffff880`0530f480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`07161000 fffff880`07173000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`03a64000 fffff880`03a71000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03a46000 fffff880`03a64000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03be5000 fffff880`03bf9000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00590000 fffff960`0059a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`04394000 fffff880`043ba000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`05324000 fffff880`05336000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05af0000 fffff880`05b0d000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`05b0d000 fffff880`05b0ef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04856000 fffff880`04867000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05336000 fffff880`05390000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`051b6000 fffff880`051c1000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04800000 fffff880`04856000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00e90000 fffff880`00e9d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`013e9000 fffff880`013f7000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`051fc000 fffff880`051fdd80   vHidDev  vHidDev.sys  Mon Dec 21 08:49:58 2009 (4B2F7D06)
fffff880`01200000 fffff880`01225000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`016d8000 fffff880`016e8000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`0110c000 fffff880`01121000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01121000 fffff880`0117d000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`016e8000 fffff880`01734000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0231b000 fffff880`02328000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`03bc0000 fffff880`03bd6000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`02218000 fffff880`02222000   vwifimp  vwifimp.sys  Mon Jul 13 20:07:28 2009 (4A5BCC40)
fffff880`03a1d000 fffff880`03a38000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`011ec000 fffff880`011fc000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d49000 fffff880`00ded000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ded000 fffff880`00dfc000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03b91000 fffff880`03b9a000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00050000 fffff960`00360000   win32k   win32k.sys   Tue Jan 04 22:59:44 2011 (4D23ECB0)
fffff880`051c1000 fffff880`051ca000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00fd8000 fffff880`00fe1000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0235c000 fffff880`0237d000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`015ec000 fffff880`015fa000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`01400000 fffff880`0140c000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0140c000 fffff880`01415000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`01415000 fffff880`01428000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`01200000 fffff880`0122a000   cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0002A000

See less See more

ihkbanks

Discussion Starter · #3 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

thanks for the quick reply. I updated your list of drivers and updated to service pack 1, also deleted Deamon tools. After all the updates and everything i started up a game of SC2 and got another blue screen. So attached is the new reports. Also I'd like to add, this ONLY happens when i have 4 gbs of ram, when i just have the 1 2gb stick everything is fine.

Lcruz1989

· #4 · Mar 28, 2011

O would read the board specs to see if it handles it of not just try 3gb.

ihkbanks

Discussion Starter · #5 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

yeah it can handle up to 16gbs

reventon

· #6 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

So, no matter which of the 2GB sticks is in place it runs fine? Swap sticks and slots until you are sure that either stick isn't faulty (memtest is not 100% reliable).

ihkbanks

Discussion Starter · #7 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

Yes if i swap them everything is fine, as long as there is no more than 2gb of RAM. Also, for the first year that I had this cpu it ran 4gb no problem. Another things is... I get no picture if both the sticks are in the same channel, I have to have them in seperate channels (one in orange channel, one in green channel) for the cpu to actually boot up.

mgorman87

· #8 · Mar 28, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

Can you post a screenshot of the memory tab in CPU-Z? Or, what are the exact specs of your memory sticks? Having issues with both sticks in the same channel has to do with dual channel. I had issues on another computer where I got errors in memtest when it was dual channel and on single channel i didn't get errors.

EDIT: Have you tried the memory in another computer to see if there are issues? Have you tried different memory in your computer?

ihkbanks

Discussion Starter · #9 · Mar 28, 2011

2

Re: BSOD When upgrading from 2gb to 4gb Ram

Below is attached screen shots of my memory tab in CPU-Z. The first picture is with only 1 stick, the 2nd pic is with both sticks.

Both sticks have been tested in other other cpu's and they work fine, I've also tested other sticks in this PC (corsair 2gb DDR2) same specs as these sticks and I'll get no picture/no startup with that stick, not sure if that stick is bugged but it is brand new.

See less See more

ihkbanks

Discussion Starter · #10 · Mar 28, 2011

2

Re: BSOD When upgrading from 2gb to 4gb Ram

here are also 2 more pics of what the sticks look like while both seated in their respected slots (slots 1 & 3)

See less See more

mgorman87

· #11 · Mar 29, 2011

Re: BSOD When upgrading from 2gb to 4gb Ram

So other sticks of memory don't work in your computer either?

ihkbanks

Discussion Starter · #12 · Mar 29, 2011

I've only tried 1 other type, the corsair that has the same specs as the ones i use now, and no it doesn't seem to work with any combo of sticks, the cpu will fail to boot up if the corsair stick isn't seated by itself. However I can use 4gbs with my 2 main sticks but when I watch video's or try to play any game, I get blue screens. with just 2gb RAM everything is fine

Tyree

· #13 · Mar 29, 2011

Mixing RAM brands/specs often results in the problems you are having and Geil RAM can be very problematic own it's own.
For 4GB of RAM, a 2X2 GB matched pair of quality RAM is the best option for performance and to avoid problems.

ihkbanks

Discussion Starter · #14 · Mar 29, 2011

yes my Geil sticks are both matching, although I can only really use one since my motherboard doesn't really want to accept having more than 2gb RAM all of a sudden for some unknown reason

Tyree

· #15 · Mar 29, 2011

If the 2 Geil sticks were not purchased as a pair it is a possibility they are conflicting with each other. My best advice would be to borrow two sticks of any other brand and see how it goes.

1 - 15 of 15 Posts

Status: Not open for further replies.