BSOD new laptop

[Ryan90]

This is the second MSI laptop I have had, I have also posted on this forum once before about this issue. I had the issues with the first msi laptop I had, sent it back, got the replacement, now I am having similar BSOD issues right out of the box! Please help if you can.

Also, computer is brand new. OS is 84bit windows 7

MSI GT660R Review

url above is the laptop itself

 

[zigzag3143]

This is the second MSI laptop I have had, I have also posted on this forum once before about this issue. I had the issues with the first msi laptop I had, sent it back, got the replacement, now I am having similar BSOD issues right out of the box! Please help if you can.

Also, computer is brand new. OS is 84bit windows 7

MSI GT660R Review

url above is the laptop itself

Majority of these were caused by memory management (usually a driver)

Please run the following tests


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.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[Ryan90]

Majority of these were caused by memory management (usually a driver).

Are there any specific drivers for just memory modules? I wasn't aware that memory had its own drivers.. Or is it just drivers in general? (graphics card etc)

OR is there a way to pop up a list of all the components on the computer and tells or shows me which ones are out of date?

Any help would be great, thanks!

 

[Ryan90]

After running the driver verifier... the computer crashes, what do I do after it crashes? what is the point of the verifier, what does forcing the computer to crash do?

 

[zigzag3143]

After running the driver verifier... the computer crashes, what do I do after it crashes? what is the point of the verifier, what does forcing the computer to crash do?

After the verifier crash you need to upload the DMP file to us. The point of making it crash is to tell us what driver caused it. When done you can turn verifier off

 

[Ryan90]

Ok, I ran the jgriff program again since I can't move the .dmp files by themselves, the last 2 dmp files (from today, the 19th) should be the 2 from forcing the computer to crash.

Thanks again for all the help!

 

[zigzag3143]

Ok, I ran the jgriff program again since I can't move the .dmp files by themselves, the last 2 dmp files (from today, the 19th) should be the 2 from forcing the computer to crash.

Thanks again for all the help!

None of these were driver verified and the probable cause of the newest (from 6/12/2011) is memory corruption


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.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[Ryan90]

6/12/11 is the recent one? I would of thought the one I did today, 6/19/11, would of been the most recent.. ill try to run the memory test asap. I don't have any blank disk to run the test on. Does it have to be burnt to a disk or can it be done by other means

 

[zigzag3143]

6/12/11 is the recent one? I would of thought the one I did today, 6/19/11, would of been the most recent.. ill try to run the memory test asap. I don't have any blank disk to run the test on. Does it have to be burnt to a disk or can it be done by other means

My apologies there are more recent than the 12th. The newest is the 16th and is related to memory management. Again Memtest is called for.

I download your file again and there must have been a problem in the file extration so again my apologies.

 

[Ryan90]

Ok so here recently I've stopped getting the "memory management" errors and now I've been getting the "page_fault_in_nonpaged_area" blue screen. I have ran the jgriff again and complied the old and new blue screen errors. Please give this a look and let me know what you guys think.

I have not had a chance to get a blank disk to run the ISO yet. But I will asap.

Thanks for your help!