New
#31
I was just wondering about those, since there seems to be a connection even if it's not the main cause something is going on.
I was just wondering about those, since there seems to be a connection even if it's not the main cause something is going on.
I can take the computer to the local repair shop and have the sound card removed just to be on the safe side, but I probably won't get a chance to do that until Wednesday.
I don't know what to do about the USB3 though, both the default and updated drivers crashed and I don't even use it. If disabling it doesn't work then I don't know what will.
Edit: I also have an empty folder (with apparently 1,025 sub-folders [when I hover the mouse over the folder that's what it says], but I can't check because the system won't let me open the sub-folders) that I can't delete called "16d6d53b60d75b756362b2138233b3" on my D: drive that I think I got when I replaced the default Via USB3 driver with the updated one.
I don't know about that folder honestly.
Have you tried the uninstall option instead of disable?
I'm guessing you are doing this in device manager?
I did disable first but afterwards I uninstalled from the Control Panel.
Sorry I was away for a few days again, I had the sound card removed and USB3 disabled in the BIOS so there should be no more problems in the Device Manager. I haven't had any youtube videos give me a BSOD for a bit over a week now but at least one of my games are still giving me BSODs (didn't get a chance to check the others). I'll attach the dump file, if it's the display driver then I'll try some other drivers ASAP.
Also, I forgot to mention before but the latch at the end of the PCI-Express lane for my video card snapped off awhile ago...is that something that could cause a problem?
Yeah, it's the display driver again,
Code:BugCheck D1, {0, 2, 8, 0} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+cf1a5 ) Followup: MachineOwnerSo you may want to try an earlier one. As long as your card isn't bouncing around I don't think that latch is a big deal at the moment.Code:Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Thu Feb 05 10:01:37 2015 (54D3B001) CheckSum: 009D4DDE ImageSize: 00A12000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I don't seem to have anymore problems with youtube videos but my game always eventually crash when under load...the heavier the load the sooner it'll crash on average. Today I had 1 BSOD and 2 freezes, here's the file.
If the problem is still the Display Driver then so far I've been firstly uninstalling the drivers in the Control Panel and then using Display Driver Uninstaller in Safe Mode...maybe I could try skipping dealing with Control Panel and delete the entire driver using Display Driver Uninstaller in Safe Mode directly? I don't know if it's a good idea or would help which is why I'm asking, but so far I've been doing the same thing repeatedly and while things are getting better I'm still having BSODs.
Well, thank you for your help so far and please let me know if there's anything else I can try doing while trying different drivers.
You're welcome,
You can try using different methods, at this point I don't see anything wrong with how you have been but it might be worth a try,
It is in fact your display driver again,
Code:Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0xd0001You can try a different driver again, I'm going to ask for some other eyes to look at this to see if we are missing something obvious.Code:Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Dec 12 22:53:17 2014 (548BE25D) CheckSum: 009E7B4F ImageSize: 00A20000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Hi, Phoenix VII. I would like to ask some questions and make a couple of observations, if I may. First, am I correct that you had these problems before and replaced the Motherboard, CPU and GPU and are still having the same problems? If I am correct, I would start looking at the components that were moved over from the old rig that was having the same problems.
Second, did you do a clean install when you put the new Motherboard in? I suspect not as I believe you said 6 months ago and you have error reports dating back to 7.2013. Unless you do a clean install, you will never get it running right. Also, did you install the drivers for the new motherboard? If so, did you download them from the Motherboard's web site. If you installed from the DVD, all of the drivers will be pretty old. Also, mentioning the error reporting, I find the last error report is from 11/2014, which is quite unusual. As of that time you were getting numerous errors from MB_Warband.exe.
Also, on that Graphics Driver install, did you change Windows Update to Download but let me decide? If you did not, Windows Update will automatically install a driver for you. Then when you install the driver you downloaded, you will have 2 which is what the tutorial is attempting to avoid. Windows will install a graphics adapter, which is OK. If you have ever had an AMD card in that rig, I would run DDU and select AMD Display drivers (or ATI, whichever one it has). If you go strictly by the tutorial, running DDU is not necessary. Just be sure to install only the graphics driver and the PhysX driver and make certain the 'clean install' box is checked.
Also, if you cannot find current drivers for your sound card, I would uninstall whatever drivers you do have from Device Manager and remove the card from the machine. If you have positive air flow, the missing pcie slot cover won't make a difference, plus they are not that hard to find.
Yes, the RAM, hard drives, and power supply are the only parts of this system that are more than half a year old.A clean re-install of Windows? I didn't, I had the motherboard upgraded a bit over half a year ago at a local repair shop after my old CPU and motherboard died.Second, did you do a clean install when you put the new Motherboard in? I suspect not as I believe you said 6 months ago and you have error reports dating back to 7.2013. Unless you do a clean install, you will never get it running right.Yes, and I installed from the motherboard's web site.Also, did you install the drivers for the new motherboard? If so, did you download them from the Motherboard's web site.Yes, it still installs a graphics adapter though.Also, on that Graphics Driver install, did you change Windows Update to Download but let me decide?Yes, that's what I've been doing.If you have ever had an AMD card in that rig, I would run DDU and select AMD Display drivers (or ATI, whichever one it has). If you go strictly by the tutorial, running DDU is not necessary. Just be sure to install only the graphics driver and the PhysX driver and make certain the 'clean install' box is checked.I had the sound card removed a couple days ago.Also, if you cannot find current drivers for your sound card, I would uninstall whatever drivers you do have from Device Manager and remove the card from the machine. If you have positive air flow, the missing pcie slot cover won't make a difference, plus they are not that hard to find.
If I really need to re-install Windows to fix these BSODs then it'll probably be awhile before I'm able to do so since I can't find the Windows 7 DVD that I used before so in order to re-install Windows I'd need to buy a new copy of Windows 7 and I'll also need to backup my data. I'll re-install Windows if I have to of course, but I probably won't be able to for a couple months since I'm dealing with some other matters right now as well. I was just hoping that since the Internet is no longer BSODing that maybe I could get my games working without BSODs as well.