📎 AI Summary:
The thread discusses a user experiencing repeated Blue Screen of Death (BSOD) errors on their Asus G74sx, likely caused by memory corruption. An expert recommends testing the RAM using Memtest86 or by removing and swapping RAM sticks to identify faulty modules, noting potential issues if multiple sticks are bad. The user plans to follow this advice, despite being unable to return the laptop under warranty due to deployment; overall, the conversation is helpful and troubleshooting-focused.
Z

ZakeriahWest

New Member
Member details
Joined
Mar 3, 2015
Messages
2
Thread Author #1
Hello Team,

I purchased my Asus G74sx in 2012, had nothing but problems with it with BSOD's, OS installed on purchase was Win7Ult, upgraded to Win8 then 8.1 had BSOD's on all OS's, I have now reverted back to Win7Ult and decided to finally do something about it and not just wish it away or wait for the fairies to magically fix it overnight.

I hope you guys can point me in the right direction, many thanks in advance.

If I have missed any attachments please let me know.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 32f5e5, 2, 32f5e4}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
Hi Zakeriah,
you have several different Bugchecks ranging from the above, Bugcheck 50 and Bugcheck 3B. Almost all of them relate to a memory issue and it...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 32f5e5, 2, 32f5e4}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
Hi Zakeriah,
you have several different Bugchecks ranging from the above, Bugcheck 50 and Bugcheck 3B. Almost all of them relate to a memory issue and it could be that you have a bad stick of RAM or the RAM settings are out and testing will see which. Even if you bought the RAM from new it's still possible to buy RAM which is faulty.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.


Just as a side note, if you don't have a spare disk or USB stick to hand you can still test your RAM by removing all RAM apart from one stick. Run on one stick until you see a bsod. Keep changing the stick over and see if you can find one which doesn't bsod.

Edit:
I forgot to ask..... Why didn't you return the machine to the place of purchase or invoke the warranty?
 
Upvote 1 Downvote
Solution
Z

ZakeriahWest

New Member
Member details
Joined
Mar 3, 2015
Messages
2
Thread Author #3
Hello,

Thank you for the speedy response, I had a gut feeling it was the memory, I was not able to return it under warranty as I was deployed oversees for a long period of time.

Reference your advice on removing RAM sticks, will it also work if I just remove one RAM stick and see if it runs okay, then swap it over continuously until I find the culprit RAM? (i.e leaving 3 sticks of RAM inside)

I will give it a shot on the weekend and will let you know how its progressed, many thanks for the advice!

Have a great day!
 
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#4
ZakeriahWest said:
Hello,

Thank you for the speedy response, I had a gut feeling it was the memory, I was not able to return it under warranty as I was deployed oversees for a long period of time.

Reference your advice on removing RAM sticks, will it also work if I just remove one RAM stick and see if it runs okay, then swap it over continuously until I find the culprit RAM? (i.e leaving 3 sticks of RAM inside)

I will give it a shot on the weekend and will let you know how its progressed, many thanks for the advice!

Have a great day!
Click to expand...
Hi Zakeriah,
I guess it would work unless two sticks or more were bad that's the only pitfall I can see. See how you go on and you get any further dump files please post.
 
Upvote 0 Downvote
You must log in or register to reply here.