[SOLVED] Various BSODs

The services relating to the particular svchost processes are to do with networking such as UPnP - This could explain the problem, as recently I just made my computer DMZ, and the UPnP could have issues trying to port forward something that already is open. I'm also pretty sure it has something to do with MsMpEng.exe (Microsoft Security Essentials)

I will try disabling the UPnP service and see if that makes any difference
 
My router is terrible and port forwarding is buggy due to dodgy design. Port forwarding doesn't work, and I will at some point replace it with a working one. Stay away from Thomson TG585v7 routers!
 
All I want is a decent router that supports DD-WRT firmware, then port forwarding should work easily or should be easy to fix
 
Yeah I know about the compatible list, I was just making a statement :) that linksys one that supports everything is tempting
 
I agree with Wrench in that router/modem combos are pretty miserable in quality and should be avoided by all means. Just look for reviews on routers that are effective at handling high traffic like streaming and then slap DD-WRT, Tomato or whatever on it.
 
One quick question - If you need to use a virtual CD device (for mounting ISO files, ect) are there any that are well coded (Unlike Daemon which causes BSODs for example) ?
 
Did you get the RAM stable?

What is the RAM frequency?
AMD CPUs have issues with RAM frequencies above 1333MHz, you need to increase the NB frequency to 2000-2400MHz to get it above 1333MHZ.
What is the DRAM voltage?

With more than 4GB RAM you will need to bump the CPU NB (IMC) voltage, bump it to 1.250v and test with memtest86+, this is a common issue with AMD systems.
If still not stable bump again by 0.02v until stable, if you get to 1.35 to 1.40v then you will need to look at DRAM voltage or other causes..
If stable then lower it by0.02v until unstable and bump it back up 0.02v, should be good.
Just like when you OC RAM, adjust and test.

This is the abbreviated version, let us know if you have any questions.
 
Note that Daemon Tools contrary to popular belief is not responsible for all the BSODs often caused. Rather it is the SPTD driver that is optionally installed. This driver is responsible for advanced media security emulation like SecuROM and whatnot and is not necessary to typical virtual drive usage unless you are attempting to use media that uses such security measures. Plus, from what I've found, almost all the SPTD driver crashes were caused by people using an outdated version of the SPTD driver that ended up making Daemon Tools notorious for crashing because it did not support Windows 7. I've found very few problems caused by the updated version of the driver.
 
Just a bit of discussion here.

Not all instances of Daemon Tools are causing systems to crash. It's just that the sptd.sys driver has a much higher incidence of caused crashes than other programs. But I've seen that dtsoftbus01.sys driver (primarily from the newer versions of Daemon Tools)can also cause BSOD's

We discovered this long ago with the Asus ATK0110 ACPI utility driver. The 2004/2005 versions were causing many, many BSOD's on Win7 systems. I then started checking at work and found that many of the systems there had the older version and weren't getting BSOD's. Then I went home and checked my personal system and found that I had the old version - and I wasn't experiencing BSOD's!

So, in short, we're playing the odds here. If you really want to try it again, feel free to do it. Should the system start BSOD'ing on you again - the primary suspect will be Daemon Tools (so remove it and the sptd.sys driver before trying anything else!).
 
UPDATE -
Sorry I haven't been replying in ages!

BSODs have completely stopped - I didn't change timings of RAM or voltages - they just seemed to stop one day. Haven't had one in at least 2 weeks.

Wierdly another problem has occured
Dllhost.exe is spiking and utilising about 31~2% of my CPU. After a bit of searching I found that it could be dodgy codecs, so I re-downloaded K-Lite Codec pack and installed it. Gave me a LOT of corrupted Codec warnings, removed them all, and installed fine. Next reboot same thing happens - So I have tracked its I/O with procmon and it seems to be accessing quite a few files (but I'm guessing since its a DllHost that it should do that anyway) - Log (filtered) has been attached to this post

thanks

View attachment 376
 
Last edited by a moderator:
Start with QuickTime Lite. Remove it and see if that helps (there's a 5 second delay right after the last QuickTime access).

Unfamiliar modules associated with that entry (I'm just too tired to look them up - sorry!):
xfire_toucan_45320.dll
actxprxy.dll
EvoGameTracker_32.dll
 
Dllhost.exe is a host process used when a DLL file wishes to run itself as its own personal executable. I've seen it used for certain extensions for programs like cheat-detection stuff for games.

Typically you can easily find the hosted DLL by checking the Dllhost.exe process using Process Explorer. If I recall, the dll should be a child process listed under DLLhost, but it can also appear in the DLLhost's Handle list (visible in Process Explorer) and any running threads under the process.

Update: oops, I got DLLHost.exe mixed up with something similar. Anyways, DLLHost.exe is to host COM+ applications. Again, your best option to look at this is with Process Explorer. Use the Handle list for it, as well as running threads and whatnot. Note that .NET managed applications use this so if that's the case things can get complicated.
 
Last edited:
I also had an issue where all of the control panel items disappeared, but sfc /scannow sorted that out :)

And yes I had originally thought it was Quicktime Lite - it started appearing shortly (or maybe reboot after) I installed it
 
Removing Quicktime Lite changed nothing - dllhost is still holding 32% of my CPU hostage - but I just suspend it and it fixes the problem (until next boot)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top