These recurrently BSOD are getting me crazy. Help Please

[leonardogw]

Hi people.

I could tell you a huge and boring history about me and my "all-kind-of" BSOD problem (it's been trhough 2 months now), but i think it's unnecessary.

I've already enabled the driver verifier and my windows began having problems even on startup. That's why i think that i have a faulty driver.

Could you help me find, for god's sake, what driver is not working correctly?

Thank you.


System spec:

- Proc: Phenom x4 955
- Mb : asus m4a785td-v evo
- 2x 2Gb Gskill 1666 mhz
- Radeon 5870
- hd 500 gb samsung
- mouse a4tech x-750f
- windows 7 professional 64 bit

 

[ttran]

Hi people.

I could tell you a huge and boring history about me and my "all-kind-of" BSOD problem (it's been trhough 2 months now), but i think it's unnecessary.

I've already enabled the driver verifier and my windows began having problems even on startup. That's why i think that i have a faulty driver.

Could you help me find, for god's sake, what driver is not working correctly?

Thank you.


System spec:

- Proc: Phenom x4 955
- Mb : asus m4a785td-v evo
- 2x 2Gb Gskill 1666 mhz
- Radeon 5870
- hd 500 gb samsung
- mouse a4tech x-750f
- windows 7 professional 64 bit

Hey yo,

That's so straight forward, Amfltx64.sys, your A4Tech X-705FS Mouse Driver, is causing your BSODs. In looking through your driver, I can see that you are so out of date:

Amfltx64 Amfltx64.sys Mon Oct 15 10:37:21 2007 (4712E071)
Amusbx64 Amusbx64.sys Wed Feb 13 15:20:14 2008 (47B2A83E)

Please update them right now, if there aren't any updates for them, then they are not compatible with window 7.

If you have time, please 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. Exception code ffffc0000005 and stop code 50 make me think about that.

BUGCHECK SUMMARY:

BugCheck 1000007E, {ffffffffc0000005, fffff800029bc0f3, fffff88002fa88b8, fffff88002fa8110}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )

Followup: MachineOwner
---------
BugCheck C4, {f6, 178, fffffa8006b5bb30, fffff88001984634}

Unable to load image \SystemRoot\system32\DRIVERS\Amfltx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Amfltx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Amfltx64.sys
Probably caused by : Amfltx64.sys ( Amfltx64+1634 )

Followup: MachineOwner
---------
BugCheck 50, {ffffd900c1c0493f, 0, fffff80002899e8c, 7}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!DestroyClass+18c )

Followup: MachineOwner
---------

Regard,

Tuan

 

[leonardogw]

Ttran,


First of all, thank you for posting.

I'll try to find a newer driver. After that, i'm gonna make some tests and i'll come here to tell you the results.

Talking about memory, i've already ran the memtest86 for 4 hours without any error. =)

 

[ttran]

Talking about memory, i've already ran the memtest86 for 4 hours without any error. =)

Yeah, memtest is optional, forget about it unless you want to check your hardware. 4 hours? How many passes had it done?

Let us know how things go in the future

Tuan

 

[leonardogw]

Talking about memory, i've already ran the memtest86 for 4 hours without any error. =)

Yeah, memtest is optional, forget about it unless you want to check your hardware. 4 hours? How many passes had it done?

Let us know how things go in the future

Tuan

Honestly, i don't know how many passes it did. I started the program and went to the gym. lol



Now, talking about the old driver... It is ok if i simply delete the Amfltx64.sys from the system32/driver folder? Or there's a better way to uninstall this thing?

 

[ttran]

Are you trying to re-install them? If you are trying to re-install them, then you can go to device manager, and uninstall it under mouse device, then install the newly install one.
If you think about using different mouse and want to get rid of those file, you can go to system32/driver as you said, change the name of those files from .sys to .BAK. That's the safe way to remove unused drivers.

 

[leonardogw]

Hi people!!


I thougth my BSOD problems were solved but today they started to appear again (and 4 times in a row)


I have uninstalled the old drivers that TTRAN (thank you dude ) told me and i don't have a clue about what's going on by now...

Please, could someone analyse these minidumps????



Thanks

 

[ttran]

Hi,

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

A4Tech X-705FS Mouse Driver, again it is still causing the issue. It's date from 2008 and probably not compatible with window 7. The driver need to be at least from 2009 until now.

Amusbx64 Amusbx64.sys Wed Feb 13 15:20:14 2008 (47B2A83E)

You can download and install fresh copy of it.

Run system file check please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BugCheck 1A, {5003, fffff70001080000, 194b, 175400003696}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+297b1 )

Followup: MachineOwner
---------
BugCheck D1, {ffffda80047945a8, 2, 0, fffff88001563ef7}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : volsnap.sys ( volsnap!VspReadCompletionRoutine+17 )

Followup: MachineOwner
---------
BugCheck 50, {ffffd8a00012d9c8, 1, fffff80002d90154, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+184 )

Followup: MachineOwner
---------
BugCheck C4, {105, fffff980048c8ca0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\Amusbx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Amusbx64.sys
*** ERROR: Module load completed but symbols could not be loaded for Amusbx64.sys
Probably caused by : Amusbx64.sys ( Amusbx64+1a11 )

Followup: MachineOwner
---------

Stop code 50 is usually hardware come into play so I really suspect the mouse itself instead of drivers.

Regard,

Tuan

 

[leonardogw]

Ttran, thank ou again.

I"ll follow the steps.

Also, l'll try to test other mouse and see what happens.

Tomorrow i post the results