oh, sure. Then i will break it, since it is only a few steps.
By the way, after i change the mouse, the bsod have less occur. Does this mean that my Razer mouse is the culprit for my previous bsod? If so, what should i do to fix it? This is the window problem, laptop problem or mouse problem? I feel like a bit sad that i cant use my expensive mouse on my laptop.
It does indicate that your mouse was at least part of the problem. After you get your system stable, you can try it again. If the problem returns, you know your mouse is not going to work with your system. I have seen a number of problems with Razer mice on Win 7. The key to fixing it is a driver made for Win 7. The driver should be dated July 13, 2009 or later. Razer seems to have chosen not to update their hardware for Win 7.
I see. I will try it. Anywhere, really thanks a lot to you(CarlTR6) and also yowanvista. Thanks for helping me alone the way.
You are very welcome. Perhaps you can go to the Razer site and ask their support folks if there is a Win 7 driver available for your mouse.
hmmm, the thing is the driver given by the Razer site state that it is supported win7 64bit as well. The link is here: Razer Support
And before i get my this new laptop, i am fine using the Razer mouse with my previous laptop, which is win7 32bit. Why?
Did you up date the mouse firmware updater or do you have the updater installed? Razer Imperator Windows Firmware Updater v1.15
Did you install this driver? Razer Imperator Driver v1.02
ya, of cause. I try to use the newest firmware and driver for my mouse already ><. And, sadly that even i change the mouse, i got another crash which is cause by usbport.sys again.... needed your help again. The dump file is uploaded. The crash happen before i change the asdf.sys to asdf.old. After this crash, i just change it. I am no sure that this crash related to asdf.sys or not.
Attachment 117689
Whocrashed result:
This was likely caused by the following module: usbport.sys
Bugcheck code: 0xFE (0x5, 0xFFFFFA80089D81A0, 0x80863B34, 0xFFFFFA8008F976A0)
Error: BUGCODE_USB_DRIVER
Dump file: C:\Windows\Minidump\112510-18813-01.dmp
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
This dump is a USB error dump. The dump blames usbehci.sys which is a Microsoft USB driver and very unlikely to be the real cause. Something else messed up the USB. It could be another driver or a program. The dumps shows mfeavfk01.sy, which is a McAfee Firewall Total Protection 2010 driver, as an unloaded module. This means that McAfee was involved in the crash though not necessarily the cause of the crash. However, McAfee is a well known and documented cause of crashes on some Win 7 systems, especially the McAfee firewall. I suggest that you uninstall McAfee using this removal tool: Tool. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on. I do not recommend reinstalling McAfee.
You still have these outdated drivers loading on your system.
The following drivers are Ricoh drivers for your card reader and can affect USB. They are also Vista Drivers and may work with Win 7.adfs.SYS Thu Jun 26 16:52:37 2008 - Adobe File System Driver, Adobe. I believe you have renamed this driver since this dump occurred.
CtClsFlt.sys Mon Jun 15 01:06:41 2009 - Creative Camera Class Upper Filter Driver, Creative Worldwide Support. This driver can be affecting USB. See if there is an update for it. It is a Vista driver and it may work with Win 7.
itecir.sys Mon Mar 09 04:58:47 2009 - itecir.sys Mon Mar 09 04:58:47 2009 - ITE Consumer IR Driver is a driver file from ITE Tech. Inc. belonging to EC CIR (PMC).ITE Tech. Inc. This driver can be affecting USB. See if there is an update for it. It is a Vista driver and it may work with Win 7.
PxHlpa64.sys Tue Jun 23 19:16:35 2009 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished. This driver is a Vista driver and it may work with Win 7.
Uninstalling McAfee may solve this problem. If it does not, there are two approaches you can take to troubleshoot this USB error. (1) you can can rename each of these drivers for which there is no update; (2) you can rename them one at a time, reboot and run your system. If you get another USB error, rename the next one, reboot, etc. The Ricoh drivers will need to be renamed all at one time. If you elect the second approach, rename them in this order: itecir.sys - Ricoh drivers - and lastly, PxHlpa64.sys.rimspe64.sys Wed Jul 01 19:54:49 2009 - RICOH Memory Stick driver, RICOH Company Ltd. OEM - none at Home | Ricoh Global. Try to update these Ricoh drivers from your computer manufacturer's website.
risdpe64.sys Wed Jul 01 05:31:57 2009 - Ricoh PCIe Memory Stick Host Controller Driver, OEM - none at Home | Ricoh Global.
rixdpe64.sys Sat Jul 04 06:27:00 2009 - Ricoh-Multi-Card-Reader-Driver, OEM - none at Home | Ricoh Global.
Please keep us updated on how your system is doing.
McAfee also involved? >< My McAfee is given by Dell which subscribe for 15 month, now still is the first month... uninstall it feel like pain for me. Now, i will use for a period to check that is asdf.sys is the cause or not. If crash happen again, i will uninstall McAfee. And do the thing by your instruction.
Remember, the dump indicted McAfee was involved in the crash and it is a known, documented cause of crashes. It is not a good program. The first thing I would do if it were my computer is get rid of it.
Quote