BSOD OS Ver 6.1.7601.2.1.0.768.3 Problem

[hsng]

Hi guys,

I've bought this laptop for 15 months now. All was well until a month plus ago when I started experiencing BSOD. This problem has persisted and even increased in frequency. Now it has become as frequent as occurring every two days. I have no idea what triggered this. Thanks so much for the help, really appreciate it!

OS: 32-bit Windows 7 Home Premium
OEM version
Age of system: 15 months
Graphics: ATI Mobility Radeon HD 5145

I am not sure what else do you all need. I'm new in this, so just tell me what else is required. Thanks

 

[zigzag3143]

Hi guys,

I've bought this laptop for 15 months now. All was well until a month plus ago when I started experiencing BSOD. This problem has persisted and even increased in frequency. Now it has become as frequent as occurring every two days. I have no idea what triggered this. Thanks so much for the help, really appreciate it!

OS: 32-bit Windows 7 Home Premium
OEM version
Age of system: 15 months
Graphics: ATI Mobility Radeon HD 5145

I am not sure what else do you all need. I'm new in this, so just tell me what else is required. Thanks

Memory corruption probably Related to SynTP.sys Synaptics Touchpad Driver..

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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



2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[hsng]

I have done the Memtest and got 15 passes or so. So, I figured that it should not be a RAM or motherboard slot problem.

However, problem arose when I tried to use the driver verifier. I followed the procedure but I couldn't start Windows when I rebooted the system. I had only two choices, either to launch Startup Repair (which was recommended), or to start Windows normally. I could not start Windows normally because it went blank when I selected the option. So I could only choose to restore the system. I wasn't given any choice to go into Safe Mode.

What should I do now? Thanks so much for the help.

 

[zigzag3143]

I have done the Memtest and got 15 passes or so. So, I figured that it should not be a RAM or motherboard slot problem.

However, problem arose when I tried to use the driver verifier. I followed the procedure but I couldn't start Windows when I rebooted the system. I had only two choices, either to launch Startup Repair (which was recommended), or to start Windows normally. I could not start Windows normally because it went blank when I selected the option. So I could only choose to restore the system. I wasn't given any choice to go into Safe Mode.

What should I do now? Thanks so much for the help.

Boot from the dvd and during the boot hit shift + F10. That will bring up a command prompt.

In that box type verifier /reset. That will turn off verifier.

Try rebooting. If you can reboot upload the dmp file from that crash.

 

[hsng]

Hi zigzag,

I'm currently in safe mode with networking, after activating the verifier. So should I continue using it till the com crash?

Thanks!

 

[zigzag3143]

Hi zigzag,

I'm currently in safe mode with networking, after activating the verifier. So should I continue using it till the com crash?

Thanks!

If it crashed in normal boot please find and upload the DMP's

 

[hsng]

Im sorry but where do I locate the dump file? There's only one dump file named 'MEMORY.dmp' at C:\Windows but the last modified date was 11th Dec 2011. It bluescreened right after the windows loading page (the page showing "starting windows...."). Thanks

 

[zigzag3143]

Im sorry but where do I locate the dump file? There's only one dump file named 'MEMORY.dmp' at C:\Windows but the last modified date was 11th Dec 2011. It bluescreened right after the windows loading page (the page showing "starting windows...."). Thanks

No problem



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[hsng]

Hi, sorry to bother you again.

I've done as you said and switched off auto restart option, as well as changing it to small memory dump in the dropdown box.

This time, after activating verifier and restarting again, I got back to the BSOD and it did not automatically restart like previous times. I've taken a picture and attached it here.

I then rebooted my laptop in safe mode with command prompt to disable verifier. After that, I restarted normally. However, back in my C:\Windows\Minidump folder, there was no new DMP file created and the newest files were dated 11th December 2011.

I'm really lost right now Really glad if you can help, thanks!!

 

[JMH]

Your snip indicates a Memory exception...

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

http://msdn.microsoft.com/en-us/library/ff559239%28v=VS.85%29.aspx

* Some basic troubleshooting techniques.

"Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server 2008 R2

http://www.sevenforums.com/tutorials/668-system-recovery-options.html

Advanced startup options (including safe mode)

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

 

[hsng]

Hi zigzag,

As I described earlier, there was no dmp file created when I turned on verifier, rebooted to find that com crashed before going into Windows, went into Safe Mode to turn off verifier then started Windows normally.

This time, as I was looking through the suggested links, my laptop crashed again. As usual, BSOD appeared and I restarted. Verifier was not on. But when I checked C:\Windows\Minidump, there was a new dmp file created (on the 17th Dec 2011). The zip file contains all content in the minidump file. I hope this is what needed to verify the problem.

Thanks so much.

 

[zigzag3143]

Hi zigzag,

As I described earlier, there was no dmp file created when I turned on verifier, rebooted to find that com crashed before going into Windows, went into Safe Mode to turn off verifier then started Windows normally.

This time, as I was looking through the suggested links, my laptop crashed again. As usual, BSOD appeared and I restarted. Verifier was not on. But when I checked C:\Windows\Minidump, there was a new dmp file created (on the 17th Dec 2011). The zip file contains all content in the minidump file. I hope this is what needed to verify the problem.

Thanks so much.

Still a memory exception, still 7E, still need a dmp with verifier enabled.

 

[JMH]

hsng,

Kaspersky is a frequent cause of BSOD's.

I suggest you remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows

 

[zigzag3143]

I have done the Memtest and got 15 passes or so. So, I figured that it should not be a RAM or motherboard slot problem.

However, problem arose when I tried to use the driver verifier. I followed the procedure but I couldn't start Windows when I rebooted the system. I had only two choices, either to launch Startup Repair (which was recommended), or to start Windows normally. I could not start Windows normally because it went blank when I selected the option. So I could only choose to restore the system. I wasn't given any choice to go into Safe Mode.

What should I do now? Thanks so much for the help.

Whats your current status?

 

[hsng]

I'm sorry for not responding for a day. I was out on a trip and merely had time to read up in order to understand what to do. Anyways, I am not sure if this is a useful information about kaspersky, I didn't check the drivers provided by Kaspersky (besides Microsoft Corporation as directed earlier), but the com still crashed before getting into Windows. There's no dmp file created, as usual. I am now on safe mode. Shall I continue in Safe Mode and wait for it to crash again? Thanks.

 

[zigzag3143]

I'm sorry for not responding for a day. I was out on a trip and merely had time to read up in order to understand what to do. Anyways, I am not sure if this is a useful information about kaspersky, I didn't check the drivers provided by Kaspersky (besides Microsoft Corporation as directed earlier), but the com still crashed before getting into Windows. There's no dmp file created, as usual. I am now on safe mode. Shall I continue in Safe Mode and wait for it to crash again? Thanks.

If you control panel is configured corrected to enable DMP's we just wait for the next one.

 

[hsng]

I am not sure if this would help, or is this a problem related to the BSOD, but the attached message has popped up twice today. Please verify. Thank you!

 

[zigzag3143]

I am not sure if this would help, or is this a problem related to the BSOD, but the attached message has popped up twice today. Please verify. Thank you!

That message is about your flash player. Read here gcswf32.dll - What is this?

 

[hsng]

Alright thanks. Will update you on the progress as soon.

 

[zigzag3143]

Alright thanks. Will update you on the progress as soon.

Good luck