BSOD windows 7 error 0x50

That's only my problem ? Or there is anything else except windows updating ?

Golden said:

I don't know because your BSOD'S don't produce .dmp files.

No .dmp files = no BSOD analysis possible.

ok what will i use for settings ? Small/Kernel/Complete Memory dump ? thanks

Golden said:

I don't know because your BSOD'S don't produce .dmp files.

No .dmp files = no BSOD analysis possible.

here we go the .dmp files !

sarmientojohn1 said:

Golden said:

I don't know because your BSOD'S don't produce .dmp files.

No .dmp files = no BSOD analysis possible.

here we go the .dmp files !

Don't start another new thread again, I've already merged these two and removed the one you just started.

You just need to be patient. Starting multiple threads for the same issue is against the rules as well as causing confusion.

derekimo said:

sarmientojohn1 said:

Golden said:

I don't know because your BSOD'S don't produce .dmp files.

No .dmp files = no BSOD analysis possible.

here we go the .dmp files !

Don't start another new thread again, I've already merged these two and removed the one you just started.

You just need to be patient. Starting multiple threads for the same issue is against the rules as well as causing confusion.

Ohhh ok sorry !

Golden said:

Code:

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*E:\Symbols*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 Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`04a04000 PsLoadedModuleList = 0xfffff800`04c40e70
Debug session time: Wed Nov 12 01:41:32.599 2014 (UTC + 10:30)
System Uptime: 0 days 0:03:04.067
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {224, fffff880022ed818, fffff98017d449d0, ffffffffc00000bb}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

You still haven't updated Windows as advised - this will likely solve your BSOD which appears to be USB-related.

Read it and follow the instructions:
Install Windows updates in Windows 7

ohhhh thanks :) i think my driver have problem already :) but thanks god its just windows updated needed thank you bro for helping me

Golden said:

You misread my reply. I said it will "likely" address what"appears" to be USB related....there may still be other issues, but it's not possible to tell until you have updated the installation.

ohhhhhh okay im installing windows update right now . i will observe bsod and i will post it here !