Solved Blue Screen Of Death . . .

[njl1960]

I was playing a game online and left it on then watched a bit of TV, when I went back, I had a BSOD, so I rebooted but it kept doing it, I got told my vid card was no good any more, plus found a raised cap on my board, bought new board, cpu, ram, vid card & a fresh install of win 7 . . .

all has been well until today, it BSOD again so rebooted had a look around they say that the file that was making error was a ram related issue, so I pulled my 2 old sticks & rebooted, it just BSOD me again, im so ticked at it, virtually new comp & it pulling this nonsense . . .

I installed a prog called " Blue Screen View " ive found some info and am going to list it & see if any of you good people maybe able to assist me in this matter . . .

ntoskrnl.exe is the file, caused by address ntoskrnl.exe+73c40 & file version is-6.1.7601.19045 (win7spl-gdr.151019-1254

to me its gobbly gook, if any one can assist id be so very grateful . . .

thank you.

Peace & Blessings . . .

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[njl1960]

thank you for your reply Golden, I have done as you asked, please find attached the zip file produced . . .

Peace & Blessings. . .

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 439fd7, 0, 4432d7}

Probably caused by : [B][COLOR="Red"]memory_corruption[/COLOR][/B] ( nt!MiBadShareCount+4c )

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

Run a minimum of 8 consecutive passes, preferably overnight, or until errors occur using MemTest86+.

Reference:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[njl1960]

Thank you for the reply, I put my old ram in with my new ram when I put comp together, when I got first BSOD after replacing every thing I pulled my 2 old sticks out and am now only running on my 2 new sticks, shall I keep my old ram out or put them back in and run scan then ?

 

[Golden]

Do you still get a BSOD with only the new RAM? If so, run it with the new RAM only.

 

[njl1960]

it has happened since but only once, I will run it tonight and post tomorrow some time
I really appreciate your help with this, your truly a blessing . . .
thank you . . .

 

[njl1960]

I ran tests & got errors, I am having trouble finding the log files for the errors though, can you assist me and let me know where to find please . . .

thank you

 

[Golden]

Log files aren't created since the tests are run in memory only.

Since you got errors, one or more of the RAM sticks is faulty and needs replacing. You can determine which by testing one RAM stick at a time (physically removing the others). Run a minimum of 8 passes on each stick.

 

[njl1960]

ok, ty for your reply, I will get back to you, I appreciate your help

 

[njl1960]

Hello Golden, after running many passes it turns out the memory I bought new was faulty, I replaced it with new & installed my old with it and it hasn't missed a beat, so thank you very much for your help with this issue, you are truly a Blessing . . .

Peace

 

[Golden]

 

[njl1960]

I am still getting BSOD not often but it seems to be happening when I have a few browsers open with games going, I got one of the windows files that my machine put together for the report to microsoft, I don't know if it is any good to you but if you can give me a heads up it would be great . . .

 

[Golden]

I'll have a look at the .dmp file in a bit, in the meantime always follow this when you get a BSOD:

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[njl1960]

Hello Golden, thx for picking this up again, your a legend . . .
please find attached the zip file you requested

 

[Laith]

Since Golden hasn't responded yet i'll respond now

fffff880`031957d0  00000000`00000000
fffff880`031957d8  fffff880`04e860d0Unable to load image \SystemRoot\system32\DRIVERS\vsdatant.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
 vsdatant+0x860d0
fffff880`031957e0  fffff880`031957e0
fffff880`031957e8  fffff880`031957e0

fffff880`041674d8  fffff880`064b64e1Unable to load image \SystemRoot\system32\drivers\aswStm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
 aswStm+0x14e1
fffff880`041674e0  fffffa80`11e50a90

Uninstall avast! and Zone Alarm and install Microsoft Security Essentials(MSE) for testing purposes.

 

[njl1960]

[QUOTEUninstall avast! and Zone Alarm and install Microsoft Security Essentials(MSE) for testing purposes.[/QUOTE]

run the DM Log collector again once ive uninstalled the two items ? thx again for helping

 

[Golden]

No, just run the system as normal. If it BSODs again, then run the DM Log Collector tool.