Blue Screen error Needs Solution
August 7th, 2016
I don’t know Why this is happening,I changed the power and data cables also but the problem repeats I have dump files of my System.Can anyone please tell me the problem of my computer by examining the dump files.
Please find the solution. System Dump files:
http://~ Dead File Host ~/rch9e1qtp3dl
Are those the only minidump’s you have? They’re dated from the 15th of December!
Is your system date set correctly?
What do you usually do before this occurs?
Also, What are your PC specs?
The minidump file showed a WDF_VIOLATION (10d) stop error that was caused by the libusb0.sys.
http://msdn.microsoft.com/en-us/library/ff557235%28VS.85%29.aspx
The libusb0.sys appears to be a driver for the following software:
http://sourceforge.net/projects/libusb-win32/files/
Update or, if necessary, uninstall the libusb software.
You clearly haven’t noticed the date on those minidumps (Or read my reply) before posting.
Unless his system date is set wrong, Those minidumps are completely irrelevant!
Yes those dumps are dated on 15th December, I didn’t have recent dump files so I uploaded those which I had kept a copy.
My Pc specifications
Hdd:seagate 160gb
1 gb ram
Intel core2duo 2.20GHz
Asus p5gc mx motherboard
OS:win 7
Download and run this software to get an idea about what’s causing the crashes:
http://www.resplendence.com/whocrashed
By default settings, Windows will restart your computer when a BSOD occurs, However, You could turn this
settings off (So you’ll actually be able to see the bluescreen and make some sense of it!)
Just follow this guide:
http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm
Next time it happens, Just take a picture of the BSOD with your phone or digital camera and post it here for a followup.
Are you doing anything particular when the BSODs occur?
You should check your HDD for errors, as your hard driver could be failing.
One thing I observed is that the system is not responding for 1 to 2mins and it repeats for 2 to 3 times and gets restarted.
New dump files dated on 5-1-2014 are posted,please let me know the problem
http://~ Dead File Host ~/x3mqvxwtk3sp
The latest ones indicate it’s caused by a faulty HDD or bad RAM!
Get your HDD checked with the following app (Get into the health tab):
http://2baksa.net/news/90194/
If it’s all good in that department, Get your RAM checked with memtest86+:
http://memtest.org/#downiso
It’s bootable, So after you burn it, Or put it on your flash drive, You’re gonna have to restart your computer, Adjust the boot order in BIOS accordingly, And boot from it. If you plan on using a disc, Make sure you burn it properly with imgburn (Use the “write image file to disc” option) memtest will run tests non-stop after booting, So you’re gonna have to restart your computer whenever you’d wanna stop it. Let it do at least 1 pass tho. If you see anything highlighted in red during the process, This would indicate your RAM has truly gone bad!
Do keep in mind however that it’s very rare for multiple RAM sticks to go bad at once, So if memtest does find errors (And you have 2 or more RAM sticks), The next step would be testing each of em individually, In order to find the bad one (This can only be done physically, By leaving only 1 stick connected to the motherboard at a time and then running memtest!) Anyways, Good luck.
Thank you.I wanna test and see what happens
Thanks to all for giving your suggestions. I changed my SMPS and my system is working fine
Ah yes, we were just gunna mention that…
Taking multimeter from back pocket..
Ah yes, we were just gunna mention that...
I’ve had no reason to mention it at the time to be honest (As nothing indicated the PSU was at fault)
But I’m sure I would’ve gotten to it eventually (If the OP would’ve mentioned that both the RAM/HDD checked out okay at least)
Yep, that’s it.
Fault finding is usually just a process of logical elimination,
with hopefully not too much collateral damage.
Yep, that’s it.
Fault finding is usually just a process of logical elimination,
with hopefully not too much collateral damage.