Solved random BSOD brand new g73jw win 7 ultimate 64bit fresh install

[CarlTR6]

Your latest dump blames memory corruption and does not give us anything specific. Keep in mind that outdated drivers can cause memory corruption. Right now you need to eliminate those drivers so we can see what your system does without them. If you get another BSOD with those drivers removed, we will look at the dump and move on to testing hardware. Troubleshooting is a process of elimination. The first hardware testing will be to test your RAM using Memtest and following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memtest for at least 7 passes. Errors, if any, will show on your screen in red. Post your results.


Did you do an upgrade install or a clean install? Upgrade installs create problems more often than not. Always do a clean install with a new OS. Add your programs back one at a time unless you know the program is compatible with the new OS; and run your computer for a day or two between each program install.

 

[homamkeh]

Hey,

thanks again for the reply.

I will uninstall eset and change the drivers to .bak.
I have already ran the memtest and passed. it does it automatically right?(after booting to memtest) all i did was wait until it said i was successful and no errors were found. it took 45 minutes. i do not remember how many passes i had. should i redo it?

I did a clean install the day i got the laptop.however, even before the clean install, (on the pre installed win 7 from Asus) for the brief time i have used it, i got a BSOD. which is leading me to believe that this is indeed a hardware issue. i have been using All the programs i am running on my system on my previous windows 7 for a while. I am fairly confident in their compatibility. However, i understand that we need to eliminate the possibility.

 

[CarlTR6]

You can certainly reinstall Eset and try it again after you know your system is running smoothly. Removing it is just part of the troubleshooting process. Regarding Memtest, it needs to run for at least 7 passes which will take 6 or more hours. If you get no errors, run it from a cold boot after your computer has been off for a while. We will run through the hardware tests after you take care of those drivers. Incompatible drivers are considered a hardware issue and are shown as such in the dump files. This is because they can cause memory corruption.

 

[homamkeh]

i have uninstalled eset (i installed ms security in the mean time), and renamed the drivers mentioned to .bak. i am now waiting for a BSOD.

when and if it happens, i will upload the dump file then proceed to run a memtest tonight. (i will probably run a memtest before i go to bed anyways)

thanks again

thanks again

 

[CarlTR6]

Very good and you are welcome. Let us know how your system is running as well as the results of Memtest. I'm hoping the BSOD's are gone.

 

[homamkeh]

I ran memtest all night (8 hours +) when i woke up i had 269 errors. I havnt shut it down yet. Is there a way to save the results?
Does this mean, whith a 100% certainty that it is a hardware issue?

Should i stop running memtest? I passed 7 tests already
What should i do now?

Thanks

 

[CarlTR6]

Yes, you can stop Memtest. All you can do is make notes of the results. This means you have a RAM problem. This can be bad RAM, incompatible RAM, a bad RAM slot or a bad memory controller. Your next step is to remove all of your RAM except the stick in the first slot. Run Memtest on that stick for at least seven passes. If no errors show, remove that stick and mark it as good. Test each remaining stick in the same way in the first slot. You can also try running your computer on just one stick and see if you get a BSOD.

If all of the sticks pass, take good stick and and test each RAM slot for at least seven passes. Post back with the results of your testing. I know this process is time consuming and aggravating; but there is no other way to do it.

I will also add that if your computer is under warranty, you should consider taking/sending it to the shop. Tell the techs what memtest found and let them sort it out.

 

[homamkeh]

hey thanks for the reply, attached is a pic of the memtest results if you need to see it.

my laptop is brand new, have had it for about a month now. I think it is a hardware issue cause like i said it was happening before and after a clean install. i have been having BSOD since day one. it would be a hassle to return it as I purchased it from the states and i am now in canada. i do not have the box and the return windows i had is long overdue. regardless, my warranty is still valid here. I already have my asus G1s at the service center here in canada. ironically, i bought this G73 laptop so i would have a computer while the g1s issue gets resolved. this will probably be my last asus purchase ever.

i will deal with the daily BSOD for now. i will probably send it for repair after the fall semester.

note that i have not had a BSOD since i uninstalled eset and changed the drivers mentioned above to .bak. is there a chance that this might not be hardware related?

again, thanks for the quick and helpful response.

 

[CarlTR6]

You most definitely have a RAM problem. It may be that you can run fairly well with it. Uninstalling Eset and eliminating those two old drivers may take enough stress and conflict from your system that you can run with the RAM. Under heavy usage, it may bite you. I am not a hardware expert; so it is difficult for me to really say. Sometimes brand new RAM is defective. Asus does not make the RAM; it comes from another manufacturer. Asus is responsible since they built the computer; but the faulty RAM is not their fault.

Good job of following suggestions. I am delighted that you have not had another BSOD. I am glad we were able to solve at least part of your problem. Please keep us updated.

 

[homamkeh]

hello again,

I just had a BSOD again. as i stated earlier, i have already uninstalled ESET and renamed the drivers mentioned to .bak.
attached is the dump file.

should i keep posting them? is there any use?

can i rename the drivers to .sys and reinstall eset?

thanks

 

[zigzag3143]

hello again,

I just had a BSOD again. as i stated earlier, i have already uninstalled ESET and renamed the drivers mentioned to .bak.
attached is the dump file.

should i keep posting them? is there any use?

can i rename the drivers to .sys and reinstall eset?

thanks

It is still memory. Have you tested it? what are the results?

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

 

[homamkeh]

hey,

yeah I ran memtest all night (8 hours +) when i woke up i had 269 errors. had 8 passes.

the laptop is brand new and still under warranty (have had it for about a month now). i just need it for the fall semester, will probably send it in right after exams.

but if memtest says there are errors then that means it is a hardware issue for sure correct?

 

[usasma]

If MemTest says that there are errors, then it's most likely that you have a hardware problem. It's just a question of what hardware (the sticks or the slots).
The next step is to figure out which sticks and/or which slots are at fault.

Try following Steps 7 to 10 in this link: Memory Diagnostics

 

[homamkeh]

im definitely not dealing with this issue if it is a hardware problem. im just going to send it back under warranty and let asus deal with it.

thanks for all the help guys i will post back after sending it to get repaired.

rep to all who helped

regards

 

[CarlTR6]

You are very welcome for the help.

should i keep posting them? is there any use?

can i rename the drivers to .sys and reinstall eset?

At this point, I think you have made the decision to have your computer checked and repaired under warranty. I agree with that decision and think it is the wise choice.

I would not rename those 2007 and 2008 drivers back to .sys. if it were my machine. Most certainly you can try Eset again; but I suggest you wait until you get your machine repaired.

Please update us and let us know what the tech's find and what the do. I suggest that when you send it in for repair that you include a letter telling your Memtest results.

 

[homamkeh]

will do. thanks again for the help. Ill update after i send it in, probably sometime in January.

regards

 

[CarlTR6]

We will be here waiting and I wish you a joyful holiday season.

 

[homamkeh]

hey guys,

hope everyone is well and enjoying the holidays.

i sent in the g73 a few days ago to get repaired. it got shipped back yesterday. I wont get a chance to take a look at it till i go back home as i am away for the holidays.

i did call them up, they changed the memory and the keyboard (another issue) will updated when i check it out in person.

thanks again for the help !

happy holidays!

 

[CarlTR6]

You are welcome. Please let us know how it does when you get back home.

 

[homamkeh]

Hello again,

Hope all of you had a wonderful holiday!

I just got back yesterday and ran memtest on the laptop all night. got ten passes (it ran for 12 hours) no errors!! they said they changed all the ram sticks so i guess the problem is indeed solved.

sadly they scratched my baby (there are two scratches on the lid of the laptop screen, it was in mint condition before i sent it in. grrrr). overall this was a frustrating, time consuming ordeal. Thanks everybody for all the help and BSOD analyzing. your efforts are truly appreciated.

Best regards,
homamkeh