Multiple BSODS

[Jayrikh]

Hello dear forum users,

Lately I've facing a lot of BSOD's, varying from BSOD 1e to 24 and 50.
I've used this and this program to collect some specs about those errors.
I hope you guys (and girls) can help me.
If you need some further information, please tell me and I'll try to collect it.
Please bear in mind that I'm just an average computer user.
Thank you in advance.

Sincerely,

Jay

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? someone installed it for me
- an OEM or full retail version? Full Retail
- What is the age of system (hardware)? About 2.5 years right now
- What is the age of OS installation? 2 months

Note: before I had vista installed on this PC, but I was facing several BSOD so a friend said that I should
install windows 7.

 

[Jonathan_King]

Hello Jay, welcome to SF!

I see two likely causes; perhaps they are both at fault.

The first of these is SPTD, which has a long history of causing BSODs in Windows. It is used by Daemon Tools and Alcohol 52/120%, neither of which I see installed on your system. First, remove any such programs you may be using, and then remove the actual driver. Use this tool to finish the job: http://www.duplexsecure.com/download/SPTDinst-v178-x64.exe

The other issue I see is network-related. AVG crashed twice, and Firefox once. It's possible AVG is the cause, but more likely, a network adapter driver is at fault.

e1e6032e.sys     Tue Mar 24 14:17:23 2009 (49C923B3) - Intel ethernet

Please install this updated driver: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18713&ProdId=998&lang=eng

You may also run a hard drive diagnostic; I recommend SeaTools.

If the BSODs persist, run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 23 04:55:05.040 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:23.944
Probably caused by : ntkrnlmp.exe ( nt!AlpcpExposeAttributes+4a )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!AlpcpExposeAttributes+4a
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 23 04:52:28.939 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:11.453
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : avgtdia.sys ( avgtdia+75a4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID:  X64_0x50_avgtdia+75a4
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 22 17:26:14.040 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:15.554
*** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys
Probably caused by : rdyboost.sys ( rdyboost+1aebf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_rdyboost+1aebf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 22 13:17:58.240 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:42.144
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiCaptureProtectionFromProto+1c
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 22 04:07:25.689 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:20.593
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectSafe+c
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Mar 20 13:54:58.034 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:12.651
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2b49 )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2b49
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar 18 04:47:53.333 2011 (UTC - 4:00)
System Uptime: 0 days 0:26:04.847
Probably caused by : ntkrnlmp.exe ( nt!NtWaitForWorkViaWorkerFactory+d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!NtWaitForWorkViaWorkerFactory+d5
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar  2 07:08:28.029 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:41.543
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+460cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_sptd+460cc
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 22 05:27:31.320 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:11.006
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
Probably caused by : volsnap.sys ( volsnap+21618 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_volsnap+21618
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Jayrikh]

Hello Jonathan,

Thank you for your fast reply. I do have Daemon tools installed on my pc, i just removed it as you said.
I will perform the rest of your recommendation's this afternoon. I hope that it works.
Thanks again!

Jay

 

[Jayrikh]

Today I've had another BSOD, this time BSOD "a".

I attached the mini dump file and another file what should be helpful according windows.
Yesterday I did not have the time to run driver verifier, what does it actually do?
That seetools program did not find any errors..

Thanks again for your time and i hope you can help me.

Sincerely,

Jay

 

[Jonathan_King]

Please keep in mind the jcgriff2 report collects all dump files, so if you upload a full report, there is no need to upload the dumps separately. We often use the full jcgriff2 reports.

Driver Verifier runs in the background, testing each driver you select; a BSOD will result if it encounters a bad driver. These dump files can often lend clues to the cause.

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 24 05:08:31.695 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:34.599
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+1bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchiWaitForSchedulerEvents+1bc
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Jayrikh]

Hello,

Here I am once again. I still face multiple Bsod's. Sometimes none on a day, some more than one. Sometimes even before I log into windows.
Here are the reports, I hope you guys can help me.
If these reports arent enough, please tell me what to do.
Thnx in advance,

Sincerely

Jay

 

[Jonathan_King]

It now seems as if this program is being caused by hardware; which component is undetermined. One BSOD might be interpreted by some to indicate possible hard drive corruption, so let's not make that test last.

Open a command prompt, and enter chkdsk /r. Also, run SeaTools on the drive, for a more physical examination. Please let us know the results.

Prime95 is another good test to run; do all three tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Memtest86 can be run overnight: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 29 12:51:57.335 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:06.849
Probably caused by : ntkrnlmp.exe ( nt!NtWaitForWorkViaWorkerFactory+d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!NtWaitForWorkViaWorkerFactory+d5
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 29 03:02:50.921 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:23.435
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+205 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsFindPrefix+205
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Mar 28 03:44:10.908 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:32.812
Probably caused by : hardware ( nt!CmpKcbCacheLookup+a36 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  postgres.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Mar 26 07:51:01.849 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:00.753
Probably caused by : ntkrnlmp.exe ( nt!PfFileInfoNotify+612 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!PfFileInfoNotify+612
SystemProductName = MS-7502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Jayrikh]

Seatools didnt find any problems, at least the programm didnt gave me a notification that something was wrong..
Chkdsk /r did his work, no report or notification that something was wrong
With the stress test: do I have to look @ the tempratures by myself the whole 6 hours!?! Haha..

Thnx for your reply, still having BSOD's though.. This time "a". When I perform those programms which collect file data, do they collect also data from the old Bsod's? Is that a problem?

Thnx again!

 

[Jonathan_King]

Keep an eye on the temperatures while running Prime95 until they stop going up; that will probably take in the range of 10-15 minutes.

As for the new report, yes, it will collect the old logs as well as the new. That's not a problem for us, though, as we can tell by the dates what is new.

 

[Jayrikh]

Hello,

Here I am once again. Sorry for not posting sooner in this topic: I was not at home for a few days.
Anyway, last night I performed the Memtest: 8 passes and no errors.
Today I will do the stress test, I'll let you know later how it went.
Yesterday I faced another BSOD's and some start-up problems. I attached the files.
Thank you for all your help until now!

Jay

 

[yowanvista]

Your X10 USB wireless Transceiver seems to be the cause. Remove that device and uninstall the software associated to it

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff08008057bf0, 2, 0, fffff8800fd5ff6a}

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


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff08008057bf0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800fd5ff6a, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec90e8
 fffff08008057bf0 

CURRENT_IRQL:  2

FAULTING_IP: 
usbehci+4f6a
fffff880`0fd5ff6a 498b5b30        mov     rbx,qword ptr [r11+30h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff800040548f0 -- (.trap 0xfffff800040548f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005661800
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800fd5ff6a rsp=fffff80004054a80 rbp=fffffa80056546a0
 r8=000000004f444648  r9=0000000000000000 r10=0bad00000bad0000
r11=fffff08008057bc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
usbehci+0x4f6a:
fffff880`0fd5ff6a 498b5b30        mov     rbx,qword ptr [r11+30h] ds:2c20:fffff080`08057bf0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c97be9 to fffff80002c98640

STACK_TEXT:  
fffff800`040547a8 fffff800`02c97be9 : 00000000`0000000a fffff080`08057bf0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`040547b0 fffff800`02c96860 : fffffa80`05663d20 fffff880`03a585c2 fffffa80`06a4a860 fffffa80`071c7b88 : nt!KiBugCheckDispatch+0x69
fffff800`040548f0 fffff880`0fd5ff6a : fffffa80`071c7b88 fffff880`04003100 fffffa80`05d34d58 fffff880`0fd608da : nt!KiPageFault+0x260
fffff800`04054a80 fffffa80`071c7b88 : fffff880`04003100 fffffa80`05d34d58 fffff880`0fd608da 00000000`00000000 : usbehci+0x4f6a
fffff800`04054a88 fffff880`04003100 : fffffa80`05d34d58 fffff880`0fd608da 00000000`00000000 00000000`00000000 : 0xfffffa80`071c7b88
fffff800`04054a90 fffffa80`05d34d58 : fffff880`0fd608da 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`04003100
fffff800`04054a98 fffff880`0fd608da : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05d34c50 : 0xfffffa80`05d34d58
fffff800`04054aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`05d34c50 00000000`ffffffff : usbehci+0x58da


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci+4f6a
fffff880`0fd5ff6a 498b5b30        mov     rbx,qword ptr [r11+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbehci+4f6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ae28235

FAILURE_BUCKET_ID:  X64_0xD1_usbehci+4f6a

BUCKET_ID:  X64_0xD1_usbehci+4f6a

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

 

[SmurofNeves]

Try downloading Amigo if your done with the uninstalls...This program works excellent for a couple of reasons...Its worked for me now on a different number of PC's....you can download it from here...
360Amigo System Speedup Free - Free software downloads and software reviews - CNET Download.com

Hope this helps abit..

 

[Jayrikh]

@ yowanvista: To be honest: I have no clue what that is.. USB wireless receiver? If I have one, I did not know about it until now.

@ SmurofNeves: downloading.

Thanks!

EDIT: I think it is my keyboard/mouse receiver. I cant uninstall that, because I don't have another keyboard. Besides that, when I had vista installed I also faced BSOD's (never asked for help back then), and also used this device.

 

[SmurofNeves]

After downloading just check out the cleaner tab and run it...

 

[Jayrikh]

I really don't like cleaning the register, faced some problems with that in the past (used Advanced System Optimizer and CCleaner then). You think its safe to do that?

 

[SmurofNeves]

yowanvista is talking about a wireless mouse or keyboard or what ever it might be using those drivers and receiver.:huh:

 

[SmurofNeves]

This program is reliable...trust me

 

[yowanvista]

Try downloading Amigo if your done with the uninstalls...This program works excellent for a couple of reasons...Its worked for me now on a different number of PC's....you can download it from here...
360Amigo System Speedup Free - Free software downloads and software reviews - CNET Download.com

Hope this helps abit..

After downloading just check out the cleaner tab and run it...

This program is reliable...trust me

No, you are wrong, these programs are not recommended as they tend to cause problems at the system level. Windows 7 does not need whatsoever tuneup programs. They cause more issues

Windows is a closed source system. Developers of tuneup/speedup utilities do not have the core code of Win 7 and are not working on definitive information, but rather they are going on past knowledge and experience, most of which is not applicable to Win 7. Automatic cleaners will usually have to do some guesswork.

There is almost no tweaking that can be done to Win 7 to speed it up. The system is designed to diagnose itself and take care of itself which it does remarkably well. Win 7 maintains itself and that includes the registry.

Cleaners are pure snake oil. At best they do nothing except use resources. At worst, they can mess your system up, slowing it down, and even crash it. There is no utility out there anywhere that can speed Win 7 up and improve its performance, at least not at this time.

 

[Jayrikh]

@ yowanvista : lucky I did not used the program, only installed it and looked at it. I don't have good experience with those.

 

[yowanvista]

EDIT: I think it is my keyboard/mouse receiver. I cant uninstall that, because I don't have another keyboard. Besides that, when I had vista installed I also faced BSOD's (never asked for help back then), and also used this device.

Do you have a spare usb/ps2 keyboard/mouse to use. It could help us identify if that keyboard/mouse receiver is the cause