BSOD several times a day...

[derk]

Microsoft wireless multimedia keyboard microsoft wireless optical mouse

 

[CarlTR6]

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.

 

[derk]

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.

 

[CarlTR6]

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.

 

[derk]

Well it happen again this morning.. Here is the memory duno

 

[techyguy]

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:http://www.sevenforums.com/crashes-debugging/87631-windows-7-unstable-2.html#post759751.Firstly,check for malware and then go to the step with the memtest86+ (plus read further down).

 

[CarlTR6]

Derk, I hoped we had solved it. I'm sorry we didn't; but we will.

Here is the Bugcheck. It blames lserial.sys

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82c8a5e5, c7713acc, 0}

Probably caused by : [COLOR=DarkRed][B]lserial.sys[/B][/COLOR] ( 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 [COLOR=DarkRed][B]lserial[/B][/COLOR]+0x1d65
c7713bb4 9a74335e 8658e1d4 82c9a610 872b30e8 [COLOR=DarkRed][B]lserial[/B][/COLOR]+0x1df9
c7713bcc 9a742abf 8658e008 876fb008 872b30e8 [B][COLOR=DarkRed]lserial[/COLOR][/B]+0x235e
c7713be4 9a74ca9b 872b3030 876fb008 872b30e8 [COLOR=DarkRed][B]lserial[/B][/COLOR]+0x1abf
c7713c08 82c4c4bc 872b3030 00000000 00000800 [COLOR=DarkRed][B]lserial[/B][/COLOR]+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: 
[B][COLOR=DarkRed]lserial[/COLOR][/B]+1d65
9a742d65 ??

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.

Let's try this -

1. Create a restore point. Make sure restore points are turned on. http://www.sevenforums.com/tutorials/81500-system-restore-enable-disable.html

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. http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html

4. Reboot

Post back your results. We have, at least, eliminated one more driver problem.

 

[derk]

Hello Carl,

I search my HD and was unable to find that file.

 

[derk]

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..

 

[CarlTR6]

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.

 

[derk]

Thanks for everything. I hope this it.. Have a great weekend!

 

[derk]

wow.. I just had 5 within 15 minutes.. it is still kicking out the 1serial.sys and i have search my HD and can't find it.

 

[CarlTR6]

Did you reboot after you uninstalled the software associated with 1serial.sys?

Let's try this -

follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
Please follow these instructions in order to run it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[derk]

Yes i did.. You know i think it has to do with MMC.. I have noticed it more and more when i launch it to connect to my remote desktops i have listed in there it seems to crash.

 

[derk]

I actually ran sfc and it found corrupt files and repaired them

 

[CarlTR6]

Very good. Are you still getting BSOD's?

 

[derk]

It is definitely Microsoft Management Console that is causing the crashes. Within seconds after load MMC, it Blue screens.

 

[Jonathan_King]

Time for a repair install: http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[zigzag3143]

It is definitely Microsoft Management Console that is causing the crashes. Within seconds after load MMC, it Blue screens.

If it is MMC there will be an error message in event viewer (type eventvwr in search) go to the windows log>application tab.

Look for critical errors (they have red in the left hand column) that say app hang, app crash, or mention MMC.

When you find them please note the event ID and source codes and let us know what they are.



Let us know if you need help with that

Ken