BSOD Every Time I Plug Something In With USB Port

[☠bones☠]

Every time I plug something in a usb port, I get a BSOD. It's really starting to make me mad and I can't figure out the cause. I've included a minidump to be looked at. I would love it if someone could help.

[Shintaro]

This is interestng:

Quote:CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Skype.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002aa2490

I would suggest that you look at shutting down the skype process to test if it is indeed skype.
The try plugging in te USB device.
But also look at any usb / chipset driver that may have been updated for your motherboard.

---

Also a short list of old drivers:

Quote:secdrv secdrv.SYS Wed Sep 13 23:18:38 2006 (4508052E)
hamachi hamachi.sys Thu Feb 19 21:36:41 2009 (499D3639)
spldr spldr.sys Tue May 12 02:56:27 2009 (4A0858BB)
spsys spsys.sys Tue May 12 03:20:58 2009 (4A085E7A)

http://www.neuber.com/taskmanager/proces...v.sys.html

[☠bones☠]

It isn't skype, I know that. I only had skype open during one of the times it happened.

[Shintaro]

So what were you doing the other times it crahsed?
Do you have those mini dumps?

---

I suppose you could also look for a BIOS update on your Lenovo desk top.

http://support.lenovo.com/en_GB/research...D=HT050904

Quote:BiosVersion = DZKT26AUS
BiosReleaseDate = 10/26/2011
SystemManufacturer = LENOVO
SystemProductName = Lenovo H415

[☠bones☠]

Every other time the only things I had running were MSN and Nightly. It always happened when I tried to plug in my headset. I thought it was just the headset at first, but then I tried unplugging and plugging in my keyboard, and that caused the bsod, too. So, I came to the conclusion that it was every time I plug some in using a USB port.

Edit: Here's a minidump from just now when I tried to shut off my computer. As soon as I press shut down, it bsod'd. Mayeb it isn't to do with the USB ports then?

[Shintaro]

This is what was what Windows thought crashed your PC last.

Quote:CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: KeyScrambler.e

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002a96490

[☠bones☠]

What? Keyscrambler? That's odd, I've been using keyscrambler for over a year now and I've never had an issue with it. I guess I could uninstall it and use my computer for a while, see if anything happens. I'll post back here explaining what happened. I appreciate all of your help.

[Shintaro]

Mate,
That is what I would be doing. Do you have the latest version?
Also have you updated your drivers and maybe the BIOS for you computer?

Personally, I would update everything first, because the crash dumps are pointing to something different every time. I would also do an offline scan of my PC, just because I am paranoid.

[AceInfinity]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c52670
Debug session time: Mon Jun 11 06:24:44.618 2012 (GMT-6)
System Uptime: 0 days 0:15:15.054

SYSTEM_SERVICE_EXCEPTION (0x3B) - (NTSTATUS) 0xC0000005

I'm seeing some strange things here:

Code: (SELECT ALL CODE)

2: kd> .cxr 0xfffff8800c039c40
rax=0000000000000012 rbx=fffffa8004335b30 rcx=fffffa80076d4e00
rdx=fffffa8004335b30 rsi=fffffa8004335c00 rdi=fffffa8004335b30
rip=fffff80002a96490 rsp=fffff8800c03a628 rbp=fffffa8003f24600
r8=0000000000000000  r9=0000000000000012 r10=fffffa80036fec70
r11=fffffa8003f1eb50 r12=0000000000000000 r13=fffffa80076ece20
r14=0000000000000000 r15=fffff8a004381780
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!IofCallDriver+0x50:
fffff800`02a96490 49ff64c070      jmp     qword ptr [r8+rax*8+70h] ds:002b:00000000`00000100=????????????????

Code: (SELECT ALL CODE)

GetPointerFromAddress: unable to read from fffff80002cbc100
Pool page fffff80002a96490 region is Unknown

Validating Pool headers for pool page: fffff80002a96490

Pool page [ fffff80002a96000 ] is __inVALID.

Analyzing linked list...
[ fffff80002a96000 ]: invalid previous size [ 0x6 ] should be [ 0x0 ]
[ fffff80002a96000 --> fffff80002a960a0 (size = 0xa0 bytes)]: Corrupt region
[ fffff80002a960b0 --> fffff80002a960e0 (size = 0x30 bytes)]: Corrupt region


Scanning for single bit errors...

None found

Code: (SELECT ALL CODE)

nt!IofCallDriver+0x50:
fffff800`02a96490 49ff64c070      jmp     qword ptr [r8+rax*8+70h]
fffff800`02a96495 90              nop
fffff800`02a96496 90              nop
fffff800`02a96497 90              nop
fffff800`02a96498 90              nop
fffff800`02a96499 90              nop
fffff800`02a9649a 90              nop
fffff800`02a9649b 90              nop

So lets get you to run Driver Verifier:

Driver Verifier: Note make sure you backup your data first

Quote:If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.

A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start - All Programs - Maintenance - "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu

Follow these steps:
- Go to Start and type in "verifier.exe" 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.

Note: If Norton Antivirus is installed, do not enable Driver Verifier's Deadlock Detection

Reboot the system and wait for it to crash to the BSOD. 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 make sure to let it run for at least 48 hours.

Reboot into Windows after the crash once again and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, or by opening a command prompt and typing in: "verifier /reset" without the quotes. If for some reason you can't get into Windows after the crash and reboot, try booting up in Safe Mode, then try these options to disable Driver Verifier from there.

If you can't get into Windows because it crashes too soon, it is recommended to try it in Safe Mode or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.

Make sure your minidumps are enabled so Driver Verifier can output one to the location for you, and post it so I can review it.

[Shintaro]

I have a feeling that those strange thing are from the Keylogger protector or malware.