BSOD when replacing a new RAM

Hi -

Why/ how did you know the old RAM was bad?
Are both 2x2 GB sticks new?
Same specs as old RAM?

The last 2 BSODs point to RAM and video; however, an earlier BSOD pointed to HDD.

Run HDD diags - SeaTools for DOS, LONG test - http://www.techsupportforum.com/2828431-post7.html

sptd.sys was loaded in RAM - last BSODs. Please remove it.

Run - Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011] - Microsoft Download Center - Download Details


Regards. . .

jcgriff2


`



BSOD SUMMARY

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-17316-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 23 20:25:52.206 2011 (GMT-5)
System Uptime: 0 days 0:03:39.985
Probably caused by : ntkrnlmp.exe ( nt!AlpcpCommunicationInfoDestroyProcedure+5d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpCommunicationInfoDestroyProcedure+5d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`035186f9 fffff880`05ebb080 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-17784-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 23 20:20:01.259 2011 (GMT-5)
System Uptime: 0 days 0:05:45.038
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`12b3ef08 fffff880`071cfe70 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by jcgriff2     
             
         J. C. Griffith, Microsoft MVP   
             
           https://mvp.support.microsoft.com/profile/Griffith   


           www.sysnative.com
             
           www.jcgriff2.com 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  

jcgriff2 said:

Hi -

Why/ how did you know the old RAM was bad?
Are both 2x2 GB sticks new?
Same specs as old RAM?

The last 2 BSODs point to RAM and video; however, an earlier BSOD pointed to HDD.

Run HDD diags - SeaTools for DOS, LONG test - http://www.techsupportforum.com/2828431-post7.html

sptd.sys was loaded in RAM - last BSODs. Please remove it.

Run - Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011] - Microsoft Download Center - Download Details

Hello there,

Thats exacty the same as my old RAM. First i thought i t was the mobo bad issue, because when i place my RAM (old one) to slot 1&2, then BSOD will appear less than 5 min, but everything goes pretty good when i stick it to another slots (3&4). BSOD never happen when im using this slot.
so i took it to the service center, claiming for guarantee, but they said the mobo was fine, they only upgrade the bios.

and then they using another RAM (different brand of mine), stick it into slot 1&2, I'd tested it with battlefield 3 and its working no bsod or such.
Then finally they take out my old RAM, and replacing me the same and brand new one. And its working as well. I asked them to put it into slot 3&4 also, just in case if there's incompatible with the slots, but everythings good, no bsod.
So i went home and then i retest it myself, i stick my new RAM to slot 1&2 again, and BOOM, Yeah right, BSOD occured.


im using Western digital hdd, is it ok im using that tools? (SeaTools for DOS)
sptd.sys removed.
i had that progam already (tools from windows for upgrade), has not run yet.

now i dunno what exactly happen.

Jonathan_King said:

The tests will run indefinitely - until you stop them. There are three different tests (Blend, Small FFTs, Large FFTs); run each of them for about an hour.

I've run all three of them, no error found so far.

anyone has a suggestion please?

SeaTools for DOS - OK to run on a WD HDD.

I'm a little confused here -

dragontiger said:

Thats exacty the same as my old RAM. First i thought i t was the mobo bad issue, because when i place my RAM (old one) to slot 1&2, then BSOD will appear less than 5 min, but everything goes pretty good when i stick it to another slots (3&4). BSOD never happen when im using this slot.
so i took it to the service center, claiming for guarantee, but they said the mobo was fine, they only upgrade the bios.

and then they using another RAM (different brand of mine), stick it into slot 1&2, I'd tested it with battlefield 3 and its working no bsod or such.
Then finally they take out my old RAM, and replacing me the same and brand new one. And its working as well. I asked them to put it into slot 3&4 also, just in case if there's incompatible with the slots, but everythings good, no bsod.
So i went home and then i retest it myself, i stick my new RAM to slot 1&2 again, and BOOM, Yeah right, BSOD occured.

What I'm 'missing' here - if all they did was a BIOS update, how does the new RAM fit in to the equation?

Did you replace the RAM simply because they said the mobo was OK?
Or. . . did the old RAM actually test bad?
--> Who tested the old RAM and concluded it was bad?

jcgriff2 said:

SeaTools for DOS - OK to run on a WD HDD.

I'm a little confused here -

What I'm 'missing' here - if all they did was a BIOS update, how does the new RAM fit in to the equation?

Did you replace the RAM simply because they said the mobo was OK?
Or. . . did the old RAM actually test bad?
--> Who tested the old RAM and concluded it was bad?

Actually I went to the PC store that I bought my PC, because i had one year guarantee for all hardware & services. First I claimed for the mobo slot for RAM, I told them that the slots was not working, everytime I stick my RAM into it BSOD happen...
then they took it to the mobo service center, and after a week I went back there and they said the mobo was fine nothing problem w/ the slots. ( There's a diffrent opinion between service center and my claim).

So they take out my old RAM and stick another (different type) RAM and stick it into the same slots and MAGIC HAPPEN! My PC running just like normal, no BSOD. Thats why they conclude that something wrong with my old RAM.
And thennn, they take out my Old RAM and replaced it with the same and new one (since I still have guarantee for all my hardware including RAM) to the PC.
I'm personally TESTED it(my PC) there and its working....Because it theres something wrong w/ my RAM, it would took less that 5 minutes before BSOD occured.

I've done installing the SP1, using the update readiness tool. AND just a moment ago, BSOD happen again. here it is: Attachment 189780

Hi -

There were actually 7 new BSODs today alone, pointing to RAM, video and possibly HDD.

System uptime before BSOD range from 33 secs to ~6 minutes -

Code:

System Uptime: 0 days 0:02:56.954
System Uptime: 0 days 0:01:53.432
System Uptime: 0 days 0:01:40.060
System Uptime: 0 days 0:00:33.720
System Uptime: 0 days 0:00:34.500
System Uptime: 0 days 0:03:39.985
System Uptime: 0 days 0:05:45.038

Mobo or other unknown hardware failure (like PSU...?) seems the likely cause.

Test Video - Video Card - Stress Test with Furmark

Run memtest86+ - 1 stick at a time; alternate the slots - http://www.techsupportforum.com/2863029-post5.html
Run HDD diags - http://www.techsupportforum.com/2828431-post7.html


Run Driver Verifier -- http://www.sysnative.com/0x1/Driver_Verifier.htm


*** If the system is still under warranty, I would contact them. The BSODs go back as far as July 2011.


Regards. . .

jcgriff2


`

BSOD SUMMARY

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-25256-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 11:21:30.721 2011 (GMT-5)
System Uptime: 0 days 0:02:56.954
Probably caused by : memory_corruption ( nt!MiRelocateImagePfn+29 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiRelocateImagePfn+29
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0356bb69 fffff880`0477bdc0 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-24164-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 11:13:26.825 2011 (GMT-5)
System Uptime: 0 days 0:01:53.432
Probably caused by : win32k.sys ( win32k!GreUpdateSpriteVisRgn+c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  speedfan.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!GreUpdateSpriteVisRgn+c8
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`001458f0 fffff880`080e2d40 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-20638-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 11:10:53.827 2011 (GMT-5)
System Uptime: 0 days 0:01:40.060
Probably caused by : win32k.sys ( win32k!xxxGetInputEvent+d0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxGetInputEvent+d0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`032a4348 fffff880`090461d0 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-21512-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 11:08:41.487 2011 (GMT-5)
System Uptime: 0 days 0:00:33.720
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WUDFHost.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
Bugcheck code 00000019
Arguments 00000000`00000003 fffff880`037e7a00 fff7f880`037e7a00 fffff880`037e7a00
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-20919-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 11:07:33.267 2011 (GMT-5)
System Uptime: 0 days 0:00:34.500
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+95a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  NisSrv.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+95a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0354b5ea fffff880`06982720 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-17316-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 23 20:25:52.206 2011 (GMT-5)
System Uptime: 0 days 0:03:39.985
Probably caused by : ntkrnlmp.exe ( nt!AlpcpCommunicationInfoDestroyProcedure+5d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpCommunicationInfoDestroyProcedure+5d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`035186f9 fffff880`05ebb080 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\122411-17784-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Dec 23 20:20:01.259 2011 (GMT-5)
System Uptime: 0 days 0:05:45.038
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`12b3ef08 fffff880`071cfe70 00000000`00000000
BiosVersion = V17.15
BiosReleaseDate = 09/26/2011
SystemManufacturer = MSI
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by jcgriff2     
             
         J. C. Griffith, Microsoft MVP   
             
           https://mvp.support.microsoft.com/profile/Griffith   


           www.sysnative.com
             
           www.jcgriff2.com 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  

Im using furmark 1.82 to do the test..
Attachment 189832

PSU? never thought of that. I hope nothing wrong with that.....
I'm gonna run memtest now, hope there's no any other hardware failure.

If there anyone could help me with this please?