BSOD when replacing a new RAM

dragontiger · Dec 21, 2011

hello guys,

yesterday i was just replacing a new RAM into my pc, bcoz there was something wrong w/ it. (BSOD happen lots of time). Im using a 2x2Gb of DDR3 RAM.

But recently, BSOD keep happening again, so i switch the slot of the DDR ( from slot 1 to slot 2, and slot 2 to slot 1), and everything seems fine until now.
I had run the furmark, and the test completed without any interruption.

The question is why is this BSOD still occured while i'd replaced the RAM?
I would really appreciated your help..thx man

Jonathan_King · Dec 21, 2011

Hello,

Start by installing SP1: Learn how to install Windows 7 Service Pack 1 (SP1)

Next, uninstall Daemon Tools, and remove SPTD with this tool: DuplexSecure - Downloads

Also, run Prime95: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

If the BSODs persist, please run the jcgriff2 application again and upload a new report. The current one was terminated abruptly before it finished.

...Summary of the dumps:

Code:

[font=lucida console]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Dec 21 06:10:46.918 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:08.307
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+326 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsOpenAttribute+326
BiosReleaseDate = 09/26/2011
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 3790.srv03_sp2_gdr.111025-0634
Debug session time: Sun Dec 18 03:36:43.048 2011 (UTC - 5:00)
System Uptime: 0 days 1:07:47.642
Probably caused by : tcpip.sys ( tcpip!SendEcho+153 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_tcpip!SendEcho+153
BiosReleaseDate = 03/19/2009
SystemProductName = Virtual Machine
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Dec 17 23:35:58.090 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:18.869
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+241 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+241
BiosReleaseDate = 09/26/2011
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Dec 17 19:11:46.375 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:35.108
*** WARNING: Unable to verify timestamp for HIDCLASS.SYS
*** ERROR: Module load completed but symbols could not be loaded for HIDCLASS.SYS
*** ERROR: Module load completed but symbols could not be loaded for mouhid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS+54b6 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_HIDCLASS+54b6
BiosReleaseDate = 09/26/2011
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Dec 17 19:08:37.571 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:42.929
Probably caused by : discache.sys ( discache!DispGetObjectLru+73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_discache!DispGetObjectLru+73
BiosReleaseDate = 09/26/2011
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

dragontiger · Dec 21, 2011

do i have to go step by step like this? im downloading SP1 now,,
do u have any suggestion to replace daemon? i mean another progam that suit win 7 64 better and able to do disc imaging (create iso file) from disk

Jonathan_King · Dec 21, 2011

Give ISO Recorder a shot: ISO Recorder

Daemon Tools must be removed before SPTD; that is the only part of my instructions that matters chronologically. Other than that, follow those instructions in any order you like.

dragontiger · Dec 21, 2011

hi jon,

i've done downloading SP1, but there's another problem occured when installing:
View attachment 189339

i'd to download the sp1 manually, because the windows update couldnt download it, i have no idea about it.
Do I have to reisntal the windows? might fix the problem i thought....

Jonathan_King · Dec 21, 2011

You might try searching around for your error code, 0x800736b3. Here's a thread right here on SF where someone was able to fix it:

http://www.sevenforums.com/windows-...-windows-7-sp1-failed-install-0x800736b3.html

Don't spend too much time worrying about SP1. Play around for a little while, and if nothing is working, set it aside for a while and continue on with the hardware tests and Daemon Tools/SPTD removal. We can crack down hard on that SP1 installation error at the end of the thread, if nothing else fixes it along the way.

dragontiger · Dec 21, 2011

Yes guru!
then i'll skip it, and forward to next step.. i dump the daemon already and put the iso recorder (kinda classic but seems great, haha)

btw, since the 1st post on this thread, theres no BSOD happen yet..

dragontiger · Dec 22, 2011

Jonathan_King said:
Hello,

Start by installing SP1: Learn how to install Windows 7 Service Pack 1 (SP1)

Next, uninstall Daemon Tools, and remove SPTD with this tool: DuplexSecure - Downloads

Also, run Prime95: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

If the BSODs persist, please run the jcgriff2 application again and upload a new report. The current one was terminated abruptly before it finished.

..¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

hi there jon, How long should i run the prime95 exactly? it is written 6hours in your tutor..
i mean, its gonna stop itselft, or i should wait it for 6hours time? man thats long of waiting.... :sleepy:

Jonathan_King · Dec 22, 2011

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.

dragontiger · Dec 23, 2011

I got another BSOD again man..here's the report.
View attachment 189687

jcgriff2 · Dec 23, 2011

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:

[font=lucida console]
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 [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


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


  [/font]

dragontiger · Dec 23, 2011

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.

dragontiger · Dec 24, 2011

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?

jcgriff2 · Dec 24, 2011

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?

dragontiger · Dec 24, 2011

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: View attachment 189780

jcgriff2 · Dec 24, 2011

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:

[font=lucida console]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[/font]

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

Test Video - http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html?ltr=V

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:

[font=lucida console]
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 [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


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


  [/font]

dragontiger · Dec 24, 2011

Im using furmark 1.82 to do the test..
View attachment 189832

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

dragontiger · Dec 25, 2011

jcgriff2 said:
There were actually 7 new BSODs today alone, pointing to RAM, video and possibly HDD.
Mobo or other unknown hardware failure (like PSU...?) seems the likely cause.
Test Video - http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html?ltr=V
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

Hi jcgriff2,

I've run Video test with furmark, both 1.82 (as shown above) & 1.90 (using burn-in xtreme burn in, & post FX option) but only got 10 avg fps. Here's the s.shot:
View attachment 189888

For memtest86+, I'd tested both the RAM, alternate them, no errors found, until I changed the memory sizing into probed and errors occured. Here's the pic:
View attachment 189889
View attachment 189890

The HDD diags show no problems, and theres no BSOD when im running the verifier..
Is it supposed to mean that my RAM has a problem again? OR other hardware failure?

Plus, everytime I starup my pc BSOD occured, likely 3-5 times or more. Hereby I attach the report:View attachment 189946

dragontiger · Dec 26, 2011

If there anyone could help me with this please?

Dave76 · Dec 27, 2011

When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.

Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

BSOD when replacing a new RAM

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Account closed

My Computer

New member

My Computer

New member

My Computer

Account closed

My Computer

New member

My Computer

Account closed

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

Similar threads