BSOD after installing Malware byte's anti malware software.


Joined
Nov 16, 2010
Messages
10
Reaction score
0
I downloaded the Malware byte's anti malware software, Ran sacn and while I was shutting down the system. I got BOSD with bccode 0*50

Here is the dump fie attached.

Plz help me.

Vijay.
 

Attachments

Ad

Advertisements

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Hi. It has nothing to do with MBAM. (And I'm telling you this before I even open the crash dump.)

Your NEC USB 3.0 driver caused the crash. Update it from the motherboard website:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI01.512\111610-25038-01 - Copy.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0364c000 PsLoadedModuleList = 0xfffff800`03889e50
Debug session time: Tue Nov 16 07:06:38.905 2010 (UTC - 5:00)
System Uptime: 0 days 8:21:50.623
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8019ed9dd8, 0, fffff880053cace0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nusb3hub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys

Could not read faulting driver name
Probably caused by : nusb3hub.sys ( nusb3hub+10ce0 )

Followup: MachineOwner
---------
Code:
2: kd> lmvm nusb3hub
start             end                 module name
fffff880`053ba000 fffff880`053d1000   nusb3hub T (no symbols)           
    Loaded symbol image file: nusb3hub.sys
    Image path: \SystemRoot\system32\DRIVERS\nusb3hub.sys
    Image name: nusb3hub.sys
    Timestamp:        Fri Nov 20 05:15:57 2009 (4B066C5D)
    CheckSum:         00016F6B
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
Joined
Nov 16, 2010
Messages
10
Reaction score
0
Thank u.

Hi Thanks for the info, Yes I remeber before shutdowining the pc, I disconnected the usb device without safe remove.

But earlier also i had faced crashes, that time USB port used to stop responding and when i shutdown it used to crash with errror code 0X9F... Is this is also because of same driver problem.

Is there any chance that there is a problem with my ram.
I bought this pc 5 months before , it is a lenevo w510

Regards,
Vijay
 
Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
You're welcome. (That driver from that date you have now is a known issue.)
 
Ad

Advertisements

Joined
Nov 16, 2010
Messages
10
Reaction score
0
Thanks a lot TorrentG

I need some more info from you, I have attached another dmp file with this post and this was generated few days before but with error code "0X9F" can you please check this and let me know is this because of the same usb driver problem.

I'm asking this because the error codes are different [ my earlier post it was 0X50 and now 0X9F ] .

Please post the dmp content if possible.

Thank you in advance.

Regards,
Vijay.
 

Attachments

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Admittedly, I never even analyzed your dumps before because this case is clear and simple. I will offer my advice here to fix your machine and it really should be followed perfectly for best results.

1) You have never updated the driver for the NEC USB 3.0 and it is still the issue you're having:

nusb3xhc nusb3xhc.sys Fri Nov 20 05:16:01 2009
nusb3hub nusb3hub.sys Fri Nov 20 05:15:57 2009

Yes, every crash you posted has been caused by this.

2) You have what I personally consider the worst software you could possibly have, based on my analysis of over 10,000 machines. It is Norton/Symantec.

Remove that in safe mode with this tool:

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN&ln=en_US

Reboot and install MSE and nothing but MSE to replace it.

3) Update your video card driver:

nvlddmkm nvlddmkm.sys Thu Dec 03 11:22:44 2009

NVIDIA

4) Uninstall whichever CheckPoint software you have to remove this old, problematic driver:

vnaap vnaap.sys Mon Dec 29 07:10:44 2008

5) Update or uninstall your Nokia phone software. This driver is too old for stability on Windows 7:

pccsmcfdx64 pccsmcfdx64.sys Thu Aug 28 05:44:41 2008

6) You have old Creative drivers which are known issues, Use Driver Sweeper in safe mode to remove all Creative software:

Phyxion.net | Driver Sweeper | Products | Products

CAX_DPV CAX_DPV.sys Tue Jun 30 16:05:11 2009
CAXHWAZL CAXHWAZL.sys Tue Jun 30 16:01:14 2009
CAX_CNXT CAX_CNXT.sys Tue Jun 30 15:59:52 2009

Then reboot and install the latest download for your card from their site:

http://support.creative.com/

7) Update your old Thinkpad Power Management driver:

Tppwr64v Tppwr64v.sys Wed Oct 18 04:40:21 2006

-------------

I really hope you follow all this as precisely as possible, or you will continue to or eventually have problems with this in the future.

Start with updating that USB 3.0 driver, of course. Enjoy and good luck.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI00.750\101910-40357-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03449000 PsLoadedModuleList = 0xfffff800`03686e50
Debug session time: Tue Oct 19 01:30:26.390 2010 (UTC - 5:00)
System Uptime: 0 days 3:21:00.276
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006c66680, fffff80000b9e510}

Probably caused by : usbser.sys ( usbser!CallUSBD+e8 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006c66680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9e510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006c66680

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff800036bd400 -- (!locks fffff800036bd400)

Resource @ nt!PiEngineLock (0xfffff800036bd400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff800036bd400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800034c0992 to fffff800034bf5da

STACK_TEXT:  
fffff880`031bd3c0 fffff800`034c0992 : fffffa80`06c66680 fffffa80`06c66680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`031bd500 fffff800`034c2cff : 00000000`00000000 00000000`00000000 fffffa80`00000000 00000000`00000088 : nt!KiCommitThreadWait+0x1d2
fffff880`031bd590 fffff880`09042b48 : 00000000`00000000 fffffa80`00000000 fffffa80`0965b100 fffff800`03633e00 : nt!KeWaitForSingleObject+0x19f
fffff880`031bd630 fffff880`0903d27e : ffffffff`ee1e5d00 fffffa80`0cda58f0 fffffa80`0965b150 00000000`000007ff : usbser!CallUSBD+0xe8
fffff880`031bd690 fffff880`09042678 : fffffa80`06f6af70 fffffa80`06f6acf0 00000000`00000000 fffffa80`0cda5a40 : usbser!GetDeviceDescriptor+0xa2
fffff880`031bd6d0 fffff880`0904541a : fffffa80`0cda58f0 fffffa80`0783a640 fffffa80`0cda5a40 fffffa80`06f6acf0 : usbser!StartDevice+0x150
fffff880`031bd740 fffff800`0387806e : 00000000`00000000 fffffa80`06f6acf0 fffffa80`0783a640 fffff880`02f64180 : usbser!UsbSer_PnP+0x25e
fffff880`031bd790 fffff800`035b314d : fffffa80`0c7e1d50 fffffa80`0783a640 fffff800`035b8d30 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031bd7d0 fffff800`03882db6 : fffff800`036bd1c0 fffffa80`0c766620 fffffa80`0783a640 fffffa80`0c7667c8 : nt!PnpStartDevice+0x11d
fffff880`031bd890 fffff800`03883054 : fffffa80`0c766620 fffffa80`09410033 fffffa80`0941b060 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`031bd920 fffff800`038a6346 : fffffa80`0c766620 fffffa80`0941b060 00000000`00000001 00000000`00000103 : nt!PipProcessStartPhase1+0x74
fffff880`031bd950 fffff800`038a68d8 : fffff800`036bad80 00000000`00000000 00000000`00000001 fffff800`03726840 : nt!PipProcessDevNodeTree+0x296
fffff880`031bdbc0 fffff800`035bb3a7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031bdc10 fffff800`034c6961 : fffff800`035bb080 fffff800`037b5c01 fffffa80`06c66600 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031bdcb0 fffff800`0375dc06 : ae74fdff`dbef4876 fffffa80`06c66680 00000000`00000080 fffffa80`06c53040 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`03497c26 : fffff880`02fd5180 fffffa80`06c66680 fffff880`02fdffc0 fffeffff`faefffff : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bbb60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8006c66680 ; kb

FOLLOWUP_IP: 
usbser!CallUSBD+e8
fffff880`09042b48 eb03            jmp     usbser!CallUSBD+0xed (fffff880`09042b4d)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbser!CallUSBD+e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbser

IMAGE_NAME:  usbser.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc08

FAILURE_BUCKET_ID:  X64_0x9F_4_usbser!CallUSBD+e8

BUCKET_ID:  X64_0x9F_4_usbser!CallUSBD+e8

Followup: MachineOwner
 
Joined
Nov 16, 2010
Messages
10
Reaction score
0
Another error ->Hard drive error 2100: HDDO initilization error (1)

Hi Torrent G,
I followed all the instruction as you have mentioned in your previous mail and BSOD is not seen. Thanks a lot.

But just today when i was browsing on my W510, all of a suddent the pc got hanged and restarted.
and showed a messge : Hard drive error 2100: HDDO initilization error (1)
I hard restarted the pc and ran hard disk drive diagnostics program. and results were pass for both "controller diag" and "read verification and speed test "

After restarting the windows normally, the pc is working fine, May I know why this error is caused.
Are there any problems with my hard drive. please help.
I have attached the system information .


Also please tell why do we get these errors, is it always because of problem with hardware or due to some software issues.


Regards,
Vijay.
 

Attachments

TrainableMan

^ The World's First ^
Moderator
Joined
May 10, 2010
Messages
9,354
Reaction score
1,587
Do you own a thinkpad? A search seems to indicate it to be a common issue with them.

Did you do as TEWS suggested and try reseating your hardware? It's also possible your hardware could be going bad as indicated in his source link. If your computer is under warranty I would contact them immediately.
 
Joined
Nov 16, 2010
Messages
10
Reaction score
0
Feedback required.

Hi,
Thanks for your suggestions, I still need to carry out all the test as suggested by TESW.

What I would like to know is "Is this kind of error is caused all the time due to problem with hard drive or does it happen due to software issues also "

The reason why I'm asking this is
1) As my friends told whenever they had received this error, their hard disk stopped working and they had to replace.
2) In my case I found this problem only once. and after restarting the drive is working fine.

Could you please provide your feedback on this.

Regards,
Vijay.
 
Ad

Advertisements

TrainableMan

^ The World's First ^
Moderator
Joined
May 10, 2010
Messages
9,354
Reaction score
1,587
I can't answer that with any certainty but it seems logical that if reseating the hardware could fix the problem then it can be caused by loose connections. I would definitely contact the manufacturer either way because parts that come loose are not much better than broken parts and I would want it fixed if it's under warranty.
 
Ad

Advertisements

Joined
Sep 22, 2010
Messages
613
Reaction score
102
@vijay

From what I see in your crash dumps, your machine was crashing because of outdated drivers. NEC USB 3.0 was the precise culprit. If you have updated it then no need to worry, you'll be fine, use the machine as normal. Should you get new crashes, please attach them so we can take a look. So no, luckilly not hardware, it all looks software related.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top