BSOD - Memory Management

ManOwar2 · 06 Feb 2010

pete256 said:

Yea, i thought there could be a problem there with the differing versions, however this is corsairs response,

These modules are compatible with your system. You should not have any problem running these modules together even they have different revisions; however, there will be a lot more stresses on the memory controller on the system when all memory slots are filled; to compensate for these stresses, memory controller will need to run these modules at a slower speed. There is a great chance that you will need to run them at DDR3 1333 speed. The best analogy is car performance; the more passengers you have, the slower the car goes. You will have to balance between performance and capacity when comes to adding more RAM to the system.

so far i have been 3 days with out a BSOD, so if the system stays stable with only 3 modules in, then that is the answer to my problem.

It has been 6 weeks of searching, and i hope this is the answer

ill keep you guys upto date with how the system goes

Hope this fix your problem too. I've been 8 days without any BSOD or program failure.

MY new ram really fixed the things ! hope this work for you too.

pete256 · 06 Feb 2010

yea, me too, i have learnt so much, also i found out that my memory timings werent set correctly, i checked them with CPU-Z and they were wrong, even if you set them to 9-9-9-24 in bios, you have to tell it to use the manual setting aswell.....

So far i have been 5 days with-out BSOD which is a new record for me, so now comes the day where i will put the other 2 modules of RAM back in to the PC, then hope that she works

pete256 · 09 Feb 2010

hey guys, just a quick update, my PC has been running very stable, im just leaving it a few more days to make sure it is stable, then i will test all my suppsions as to the cause of the BSOD, so far i have some good results

i hope the work of USASMA, Manowar2, and myself will help people who have a similar problem

pete256 · 17 Feb 2010

Well, it seems this problem is never ending............

I had the PC stable for a little while, but it has still fallen back in to BSOD's

The problems occour more frequently when SLI is enabled, but they still occour when it is dissabled. I went back to BIOS defaults, and manualy set the memory timings, and changed the Data rate from 2T to 3T, which has given me a drop in performance, but a huge huge increase in stabliity, but i still get a BSOD from time to time.

The good news is i found the a file that is causeing the issue, it is the CDD.DLL, in action centre after each crash, be it memory management, your pc is dead, etc.... it would always say windows has crash 13 times due to a device or driver, the wonderfull thing is that it didnt tell me what driver........ however this time, i saw CDD.DLL in the BSOD, and then went back into action centre and it said windows has crashed 14 times due to this driver.

After some reasearch, it has narrowed it down to 2 possibilities, faulty RAM, or Faulty Ram on my graphics cards, i just havent got the money to go buy more ram to test this, as the company i purchased the RAM from will charge me for all the postage and hanlding when they send it back to the manufacture if the ram is faulty, so testing the hardware is going to be difficult considering that the memory passes Memtest, i got it up to 20 passes over 2 days, and no fault, and furmark for several hours with no fault.....

My mate has a computer shop, so im hoping he will let me borrow and test some ram to see if there is a fault.

Ill keep you guys upto date on the issue

**cluberti** · 23 Jan 2015

This is just jumping all over the place - I am starting to suspect hardware, possibly RAM. These dumps indicate failure when attempting network connectivity (in Chrome.exe, again), and there's an active IRP to nsiproxy.sys:

Code:

0: kd> !thread
THREAD fffffa800d78b060  Cid 0354.0d60  Teb: 00000000fffdb000 Win32Thread: fffff900c3bb6010 RUNNING on processor 0
IRP List:
    fffff9802fe74ee0: (0006,0118) Flags: 40060000  Mdl: 00000000
Not impersonating
DeviceMap                 fffff8a001c44160
Owning Process            fffffa800d7d0b30       Image:         chrome.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      633246         Ticks: 0
Context Switch Count      2664208        IdealProcessor: 0                 LargeStack
UserTime                  00:36:13.062
KernelTime                00:09:26.205
Win32 Start Address 0x00000000013f66c4
Stack Init fffff8800ab5cdb0 Current fffff8800ab5c670
Base fffff8800ab5d000 Limit fffff8800ab54000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0ab5c9a8 fffff800`02d3f21e : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`000065dc : nt!KeBugCheckEx
fffff880`0ab5c9b0 fffff800`02cd8469 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x56bfe
fffff880`0ab5cac0 fffff800`02cc9fae : 00000000`00000000 00000000`192d0000 00000000`ff000001 00000000`18f4d42c : nt!MmAccessFault+0x359
fffff880`0ab5cc20 00000000`6a7db72d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0ab5cc20)
00000000`001bddd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a7db72d
0: kd> !io fffff9802fe74ee0
Irp is active with 1 stacks 1 is current (= 0xfffff9802fe74fb0)
 No Mdl: No System Buffer: Thread fffffa800d78b060:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
>[IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            0  1 fffffa800c3ed7f0 fffffa800db6bc60 00000000-00000000    pending
        \Driver\nsiproxy
   Args: 00000014 00000014 0012003f 001bf800
Notification Event: fffffa80`0d203560 
 [  e, 0] = IRP_MJ_DEVICE_CONTROL, IRP_MN_???
  IO Status: 0 : STATUS_SUCCESS
File Object: fffffa800db6bc60  Type: (fffffa8009796f30) File
    ObjectHeader: fffffa800db6bc30 (new version)
    HandleCount: 1  PointerCount: 2
Current Driver:
No.  MEMORY_RANGE                           CheckSum  TimeStamp                           Flag Author            Image Name       Dist Version                Path
  1  fffff880`04080000 - fffff880`0408c000  00013ed5  4a5bc15e  Mon Jul 13 16:21:02 2009  ???                   nsiproxy.sys          \SystemRoot\system32\drivers\nsiproxy.sys

There's an update to this file in KB2588507 that you don't have installed, but again, given how crazy this has been I can't say one way or the other if this will resolve behavior or not.