Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on wiped and reinstalled Win 7 x64 Home Edition


  • Please log in to reply
6 replies to this topic

#1 trulyblue

trulyblue

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Phoenix, AZ
  • Local time:09:44 AM

Posted 06 February 2014 - 04:47 PM

Please help! I'm at the end of my knowledge and it's still not fixed!

Basically my mother got another virus, ugly one too. Can't remember the name of it out of the frustration from this episode. Anyway, I saved her stuff and did a clean re-install. Got all the drivers downloaded and all that from Toshiba, all Windows updates done and only put Chrome, Spybot, AVG, Yahoo Messenger and LogMeIn (that has saved me so many headaches). I haven't even resaved her stuff onto here. I did all the stuff and did a restart and boom, BSOD on me just have the second tone when Windows starts *buh duh buh duh*. It automatically restarted and was fine. But why is it doing that? I tried looking at the Windows solutions and ran the memory and hard disk scans but they came back clean. I don't know what else to do besides give it back to her and tell her to ignore it and select 'Start Windows Normally'. Oh, here's some info that I saw on another question that might help?

 

 ==================================================

Dump File         : 020614-45973-01.dmp
Crash Time        : 2/6/2014 2:01:42 PM
Bug Check String  : INVALID_PROCESS_ATTACH_ATTEMPT
Bug Check Code    : 0x00000005
Parameter 1       : fffffa80`01722840
Parameter 2       : fffffa80`040ceb30
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000001
Caused By Driver  : SynTP.sys
Caused By Address : SynTP.sys+6be20
File Description  : Synaptics Touchpad 64-bit Driver
Product Name      : Synaptics Pointing Device Driver
Company           : Synaptics Incorporated
File Version      : 17.0.8.21 23Aug13
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\020614-45973-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,160
Dump File Time    : 2/6/2014 2:03:13 PM
==================================================
 
==================================================
Dump File         : 020614-23992-01.dmp
Crash Time        : 2/6/2014 1:55:37 PM
Bug Check String  : INVALID_PROCESS_ATTACH_ATTEMPT
Bug Check Code    : 0x00000005
Parameter 1       : fffffa80`01722840
Parameter 2       : fffffa80`041dfb30
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000001
Caused By Driver  : SynTP.sys
Caused By Address : SynTP.sys+6be20
File Description  : Synaptics Touchpad 64-bit Driver
Product Name      : Synaptics Pointing Device Driver
Company           : Synaptics Incorporated
File Version      : 17.0.8.21 23Aug13
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\020614-23992-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,160
Dump File Time    : 2/6/2014 1:56:34 PM
==================================================
 
==================================================
Dump File         : 020414-51355-01.dmp
Crash Time        : 2/4/2014 4:38:53 PM
Bug Check String  : INVALID_PROCESS_ATTACH_ATTEMPT
Bug Check Code    : 0x00000005
Parameter 1       : fffffa80`01722840
Parameter 2       : fffffa80`040b1b30
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000001
Caused By Driver  : SynTP.sys
Caused By Address : SynTP.sys+6be20
File Description  : Synaptics Touchpad 64-bit Driver
Product Name      : Synaptics Pointing Device Driver
Company           : Synaptics Incorporated
File Version      : 17.0.8.21 23Aug13
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\020414-51355-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,104
Dump File Time    : 2/4/2014 4:40:45 PM
==================================================
 
==================================================
Dump File         : 020414-56425-01.dmp
Crash Time        : 2/4/2014 1:30:57 PM
Bug Check String  : INVALID_PROCESS_ATTACH_ATTEMPT
Bug Check Code    : 0x00000005
Parameter 1       : fffffa80`017225f0
Parameter 2       : fffffa80`03f39b30
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000001
Caused By Driver  : SynTP.sys
Caused By Address : SynTP.sys+6be20
File Description  : Synaptics Touchpad 64-bit Driver
Product Name      : Synaptics Pointing Device Driver
Company           : Synaptics Incorporated
File Version      : 17.0.8.21 23Aug13
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\020414-56425-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,104
Dump File Time    : 2/4/2014 1:32:27 PM
==================================================
 


BC AdBot (Login to Remove)

 


#2 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:44 AM

Posted 06 February 2014 - 04:55 PM

Those dump files point at your synaptics touchpad driver. From control panel find programs and features, find synaptics from the list and uninstall, see if this solves the issue. There may be a newer or older driver that will not cause the crash. The generic windows mouse drivers will work but certain features such as the touchpad scroll options may not work.


Edited by zingo156, 06 February 2014 - 04:56 PM.

If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#3 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:44 AM

Posted 06 February 2014 - 05:00 PM

Wait... Were those dump files yours or someone elses?

 

Could you please run who crashed:

 

Please download Who Crashed? and save it to your desktop.

Double click whocrashedSetup.exe and choose Run

On Windows Vista, 7, 8 and 8.1 machines, when User Account Control asks if you wish to install this program, say YES to install the program on your computer.

Program can also be installed by right click and choosing Run As An Administrator.

On the next screen choose Next and accept the agreement.

Install the program in it's default location C:\Program Files\WhoCrashed (If your primary drive is different from C:, choose your primary drive.)

Choose Next and allow program to create a Start Menu Folder called WhoCrashed and click Next.

Allow program to create desktop icon and click Next.

Now Click Install.

Once the program is installed on your computer system, look for the WhoCrashed icon.png desktop Icon and double click it.

Accept the User Account Control request and the program will open in your screen and should look something like this.

whocrashed.png

Next, Click the Analyze button. analyze.png

An Information Window should appear on your screen prompting you to scroll down your screen.

If a report was generated we would like to have a look at this report.

To do this, click File analyze.png and then choose Export.

Save as WhoCrashedOutput.htm to your desktop.

Open WhoCrashedOutput.htm and copy and paste all of the contents from System Information (local) and Crash Dump Analysis and the Conclusion into your next reply.


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#4 trulyblue

trulyblue
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Phoenix, AZ
  • Local time:09:44 AM

Posted 06 February 2014 - 05:11 PM

Those were mine and the touchpad drivers fixed the problem :) I uninstalled them, rebooted and Windows automatically updated the drivers so I didn't touch them. I've rebooted a couple of times and it looks like it's fixed, yay!



#5 trulyblue

trulyblue
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Phoenix, AZ
  • Local time:09:44 AM

Posted 06 February 2014 - 05:16 PM

Sorry, forgot to add this:

System Information (local)

computer name: SHELLY-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Satellite C655, TOSHIBA, Portable PC
CPU: GenuineIntel Intel® Celeron® CPU 900 @ 2.20GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 2009047040 total
VM: 2147352576, free: 1926569984


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 2/6/2014 9:01:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020614-45973-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x5 (0xFFFFFA8001722840, 0xFFFFFA80040CEB30, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 2/6/2014 9:01:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: syntp.sys (SynTP+0x3B9FB) 
Bugcheck code: 0x5 (0xFFFFFA8001722840, 0xFFFFFA80040CEB30, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\drivers\syntp.sys
product: Synaptics Pointing Device Driver
company: Synaptics Incorporated
description: Synaptics Touchpad 64-bit Driver
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated). 
Google query: Synaptics Incorporated INVALID_PROCESS_ATTACH_ATTEMPT



On Thu 2/6/2014 8:55:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020614-23992-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x5 (0xFFFFFA8001722840, 0xFFFFFA80041DFB30, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 2/4/2014 11:38:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020414-51355-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x5 (0xFFFFFA8001722840, 0xFFFFFA80040B1B30, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 2/4/2014 8:30:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020414-56425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x5 (0xFFFFFA80017225F0, 0xFFFFFA8003F39B30, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


 

Conclusion

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 



#6 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:44 AM

Posted 06 February 2014 - 05:56 PM

Ok, that shows the same crash dumps. Because of this: "Oh, here's some info that I saw on another question that might help?" I thought those may have been someone elses crash report.

 

I am glad to hear that uninstalling fixed the issue. Just note that with the windows generic driver certain touchpad features may not work. The best example would be in a web page you may not be able to scroll by sliding your fingers in the corners. If this becomes a problem you can try and download the latest driver from the manufacturers website.


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#7 trulyblue

trulyblue
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Phoenix, AZ
  • Local time:09:44 AM

Posted 06 February 2014 - 07:20 PM

Because of this: "Oh, here's some info that I saw on another question that might help?" I thought those may have been someone elses crash report.

 

Yeah, sorry about that. I meant that I had read about how to get the information on another thread. But thank you very much for helping me finally fix this issue :)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users