There are several types of freezing problems. Generally you will get a bugcheck Except if the problem is in a secondary processor like a GPU or some more advanced Network controllers (most likely you don't have one)
So if the machine locks up and just does not respond at all it is going to be your graphics hardware.
That being said, there are various caused depending on the GPU you are using.
For example, newer Nvidia GPU tend to lock up because of old network drivers because they install shadowplay streaming. The streaming uses the network driver even if you are not using it, drivers before 2013 all seem to cause problems for virus scanners and the NVIDIA GPUs. Windows does not update most network drivers and you have to go to the motherboard vendor or the chipset vendor to get a current working driver.
There are other issues that also cause the GPU to lock up. Audio driver conflicts, sound devices on a PC don't know if they have a speaker connected to them. If you have different sound sources, like a sound card on your motherboard, it can conflict with the sound source provided by your GPU. The GPU has to support sound if you use a HDMI or displayport cable if you have speakers in your monitor that are feed by the video cable. Problem is they can use the same Direct memory Access channel and interfere with each other. The BIOS sets the interrupts and DMA channels and creates a database that it sends to windows and windows uses these setting and then makes changes. Biggest problem is people add or change hardware and don't go into BIOS and reset it to defaults or update it to get it to rescan and recreate the database. The effect is the BIOS may provide a database to windows that says that you have certain hardware that you have removed, windows can not use those resource settings but then detects your new hardware and tries to configure it but can not use the proper hardware settings so has to configure it strangely. For example, I have seen graphics configured to be chained be to work behind a slow device like a USB drive.
problem is the graphics only gets a max of 2 seconds to respond or it bugchecks. Generally, it would work but bugs in the USB BIOS support and drivers can make the port take too long to respond.
So, consider, reset your BIOS after making a hardware change, turn off any sound sources that you don't have a speaker connected to. You can disable the GPU high definition sound support in control panel device manager.
you might also want to make sure you are not running overclocking software, and disable any BIOS overclock.
Some versions of motherboards automatically overclock the PCI/E bus to 103Mhz (should be 100Mhz) this would work, but then people get factory overclocked graphics cards and they just fail.
(I have seen systems with 20% overclocked graphics cards that did not work until you overclocked the PCI/E bus to get the hardware timing signals to on the BUS to match the speed of the card)
Generally it is easier to tell people how to underclock the GPU than trying to figure out the various overclocking problem.
- overclocked cards also, pull more power and generate more heat and cause more memory errors in the GPU. This can hang the GPU that windows may not detect. Windows has made changes to try and detect a non response and will try to reset the GPU. This only helps if the GPU stops talking to windows, but not in the case where it just stops updating its graphics buffers. (same image on the screen)
some times in this case you can use the keyboard and force a memory dump and have it looked at to see what the problem is. Google "how to force a memory dump using a keyboard" It is a registry setting, when the system locks up you hit a keyboard key sequence and it does a bugcheck.
overclocked GPU can overheat, generate memory errors in the GPU and crash the GPU drivers.
sometimes all you have to do is blow out the dust and turn the fan on high.
anyway, that is what I can think of off the top of my head.
update BIOS, reset to defaults, update USB drivers, update ethernet drivers, update CPU chipset drivers, update audio drivers are some of the stranger fixes for hung graphics devices. Guess I should mention you should update your graphics driver including the graphic drivers sound driver (you don't want to have mixed build dates for your graphics drivers)
Silverfall :
Hi!
So I have managed to contain the problem at least for now by simply doing like you did. I did disable the usb3 from BIOS and now BSOD since. Though could you give me some tips with some other problem which has annoyed me for much longer time. So this computer of mine is build by me. This computer has had the "freezing" problem from the start. First I thought it was about my faulty craphics card but I have changed it since. Also I did send my computer back to the place where I bought all the components and they managed to find out that it had faulty processor and memory sticks. So they changed them. Now after that my computer still freezes but it doesnt freeze as often as it did before. Sometimes it freezes when I play some games and sometimes when im simply watching stream or something with my computer. Im really curious what can cause this? Could it be my motherboard? I have only 2 ogirinal components left from the set which i build myself. Motherboard and power supply. Thanks alot!
johnbl :
the file name is contains the date and some numbers to prevent duplicate file names.
the file itself will contain the debug info used by the live kernel debugger.
it means windows was trying to figure out a problem on your machine. Most likely it could not fix it for some reason.
put the live kernel dumps on a server and post a link.
I have found, at least on my wife's machine the, the machines were rebooted after they did the live kernel dump.
(She asked me to find out why her machine was sometimes rebooted)
Silverfall :
johnbl :
for usb problems, you will want to update the BIOS, the BIOS sets up the electronics for the USB subsystems.
then you need to update the CPU chipset to get updates for usb 2.x drivers, then update the motherboard chipset drivers to get USB 3.0 driver updates. with older machines generally usb 3.0 does not work correctly until you get a BIOS and drivers built in 2013 and newer. There were many version of USB 3.0 chipset that were shipped. Microsoft put generic drivers that install but do not account for broken logic in the BIOS or in the actual chip that may be on your motherboard.
This can result in bugchecks and what looks like random reboots of your system in windows 10. (kind of rude)
start cmd.exe as an admin then run
cd c:\
dir /s *.dmp
look at the names of the .dmp files that are found. there may be some that indicate USB extensions in the file name.
looking at this with a debugger can help figure out the problem.
normally you need a kernel memory dump to figure out USB problems.
With my wifes system, I found that windows 10 driver did not account for a bug in the asmedia usb 3.0 chipset and her machine would crash. I could not get a BIOS update so I disabled the USB 3.0 hardware using the BIOS and here machine stopped rebooting. Looked like microsoft was collecting live kernel dumps on the system and rebooted it without making a log or providing a indication of why it was being rebooted.
Silverfall :
I was wondering how should I proceed with my usb.sys BSOD problem? So i have windows 10 now and suddenly today I got BSOD while watching live stream and being in a skype call. I have had problems with usb.sys earlier but that was sometime ago and I had win 8.1 back then. I managed to fix the problem my own at that time but im just tired of this happening now again with new Windows and I would like to maximize my chances to success completely this time. So I analyzed already dmp. file and Im not sure how i should not proceed with the information that I have. Should I remove usb drivers and install them again or what? One thing I noticed from analyze section that it stated that faulty usb.sys was in Windows 8 drivers sections but I have win 10. So is this something weird or am I just wrong about that one. Thanks alot in advance!
Hi!
Thanks for the answer! SO i have newest BIOS already which i am able to get from manufacturer's site. Also checked yesterday if there is something else "new" I could download from driver's and tool's section in the same site but there isn't anything I havent got already. My machine is pretty new. Not even a year old. Im not sure though how updated is my CPU chipset but both my BIOS is newest possible and also motherboard drivers should be aswell. I also did the CMD prompt command like you suggested and there was some old dmp. stuff aswell from the win 8.1 days back there but this is what it said in the kernel part:
Directory of c:\Windows\LiveKernelReports\WATCHDOG
10.04.2015 01:22 598 203 WD-20150410-0122-01.dmp
10.04.2015 01:22 598 205 WD-20150410-0122-02.dmp
10.04.2015 01:22 598 947 WD-20150410-0122-03.dmp
10.04.2015 01:22 614 574 WD-20150410-0122-04.dmp
10.04.2015 01:22 605 193 WD-20150410-0122.dmp
10.04.2015 02:54 572 610 WD-20150410-0254-01.dmp
10.04.2015 02:54 573 241 WD-20150410-0254-02.dmp
10.04.2015 02:54 570 542 WD-20150410-0254-03.dmp
10.04.2015 02:54 586 236 WD-20150410-0254-04.dmp
10.04.2015 02:54 577 013 WD-20150410-0254.dmp
10 File(s) 5 894 764 bytes
As you can see they are dated abit back in time back to the days I had win 8.1. This is what the new win 10 .dmp looks like:
Directory of c:\Windows\Minidump
16.08.2015 22:13 331 352 081615-19312-01.dmp
1 File(s) 331 352 bytes
Im not sure if those numbers should mean something to me but they do not. Do they tell something to you? Thanks alot again!
Facebook
Twitter
Instagram