New
#21
Microsoft wireless multimedia keyboard microsoft wireless optical mouse
Microsoft wireless multimedia keyboard microsoft wireless optical mouse
The MS keyboard is consistent with nskbfltr.sys. It is an MS keyboard driver though a little old.
Here are some links for you:
Microsoft Hardware Mouse and Keyboard – Home Page
Download Software
You might be able to update your driver through these links.
All updated.. everything seems to be running, so i hope this has resolved the issue. Thanks so much for everyones help. I greatly appreciate it. I will keep you posted.
One more thing, Derk, regarding that mysterious driver, lserial.sys. if you have any more problems, search for this driver on your system and delete it. But first create a system restore point. Don't delete it without a system restore point - just in case.
Congratulations on getting your drivers updated and your system running smoothly (we hope). You did a good job. And thanks for reporting back to us.
I will let the thread ride a couple of days before we mark it as solved.
Happy computing. :)
Well it happen again this morning.. Here is the memory duno
Do you have random crashes too?I mean,do different programs crash at different times?Do the BSODs happen when you do something particular,or are they totally random?
If all crashes are random and BSODs are random,then you should check your ram,because that was my problem.Do check on my post here:https://www.sevenforums.com/crashes-d...tml#post759751.Firstly,check for malware and then go to the step with the memtest86+ (plus read further down).
Derk, I hoped we had solved it. I'm sorry we didn't; but we will.
Here is the Bugcheck. It blames lserial.sys
This analysis also mentions mmc.exe which is most probably NOT the cause. mmc.exe is the Microsoft Management Console application and is used to display various management plug-ins accessed from the Control Panel, such as the Device Manager.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 82c8a5e5, c7713acc, 0} Probably caused by : lserial.sys ( lserial+1d65 ) Followup: MachineOwner ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 82c8a5e5, The address that the exception occurred at Arg3: c7713acc, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!MmUnlockPages+4e1 82c8a5e5 66214306 and word ptr [ebx+6],ax TRAP_FRAME: c7713acc -- (.trap 0xffffffffc7713acc) ErrCode = 00000002 eax=fffff7fd ebx=00000001 ecx=00000000 edx=00000000 esi=85800748 edi=00000000 eip=82c8a5e5 esp=c7713b40 ebp=c7713b88 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MmUnlockPages+0x4e1: 82c8a5e5 66214306 and word ptr [ebx+6],ax ds:0023:00000007=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: mmc.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 9a742d65 to 82c8a5e5 STACK_TEXT: c7713b88 9a742d65 00000001 8658e814 8658e816 nt!MmUnlockPages+0x4e1 WARNING: Stack unwind information not available. Following frames may be wrong. c7713b9c 9a742df9 8658e1d4 8658e03c 8658e008 lserial+0x1d65 c7713bb4 9a74335e 8658e1d4 82c9a610 872b30e8 lserial+0x1df9 c7713bcc 9a742abf 8658e008 876fb008 872b30e8 lserial+0x235e c7713be4 9a74ca9b 872b3030 876fb008 872b30e8 lserial+0x1abf c7713c08 82c4c4bc 872b3030 00000000 00000800 lserial+0xba9b c7713c20 82e51e07 8591b780 85df3088 00000000 nt!IofCallDriver+0x63 c7713c64 82e3173c 85df30a0 85df30a0 85df3088 nt!IopDeleteFile+0x10c c7713c7c 82c78f60 00000000 85ca1d48 85df3088 nt!ObpRemoveObjectRoutine+0x59 c7713c90 82c78ed0 85df30a0 82e557cc b8447838 nt!ObfDereferenceObjectWithTag+0x88 c7713c98 82e557cc b8447838 85ca1d48 00000188 nt!ObfDereferenceObject+0xd c7713cdc 82e56fb2 b8447838 af4ab310 87251a28 nt!ObpCloseHandleTableEntry+0x21d c7713d0c 82e5712a 87251a28 85ca1d01 049ff5c4 nt!ObpCloseHandle+0x7f c7713d28 82c5344a 00000188 049ff5c8 774f64f4 nt!NtClose+0x4e c7713d28 774f64f4 00000188 049ff5c8 774f64f4 nt!KiFastCallEntry+0x12a 049ff5c8 00000000 00000000 00000000 00000000 0x774f64f4 STACK_COMMAND: kb FOLLOWUP_IP: lserial+1d65 9a742d65 ??
Let's try this -
1. Create a restore point. Make sure restore points are turned on. System Restore - Enable or Disable
2. Do a search for lserial.sys on your C: drive (or whichever drive your OS is loaded on).
3. Delete this file. You may have to take ownership to do this. Take Ownership Shortcut
4. Reboot
Post back your results. We have, at least, eliminated one more driver problem.
Last edited by CarlTR6; 29 May 2010 at 19:09.
Hello Carl,
I search my HD and was unable to find that file.
Wait i found it.. the iserial.sys is asscoaited with StarTech IP-Extender. I used to to connect to a serial-ip device for my phone system..
Uninstall that program. I recommend that you use Revo uninstaller. After you uninstall program, make sure iserial.sys was removed also. If not, delete it. It is not a bad idea to periodically uninstall any programs that you no longer use.