• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hottroc

Profile Information

  • OS
    Windows 7 x64
  1. I think I remember something in the BIOS about that. I'll check it out.
  2. Afraid so, yes, it does still occur. I try uninstalling different USB devices including hubs and controllers in Device Manager but so far I still cannot solve it. Oddly the time taken for the problem to recur following a reboot does not appear to be constant. Sometimes it can be 2-3 hours, sometimes (usually) longer up to a few days. I wonder if there is a loose solder joint on my motherboard or something, but I just can't tell. I did think the internal card reader was the main suspect but still not sure. I have now changed it for a spare one I had laying around (same model) but the problem has still reappeared since so... I've sort of given up a bit, it was driving me nuts and taking up lots of time so I have just let it go and decided to just put up with the occasional reboot (on average a couple of days I suppose).
  3. Me again. My problem is still not resolved although it took a long time to reappear. The variation you mentioned in post #467 did not seem to give any more information than the normal method. I cannot run a cleanboot for reasons given earlier ie the problem sometimes takes days to appear and a reboot cures it till the next time. Never mind. hottroc.
  4. OK, will do. It is a great shame that xperf and LatencyMon cannot be improved to show exactly which device was causing the problem. That would be much more useful. As it stands there is little benefit to using them (for me anyway) over the normal trial and error of removing one device at a time, which was eventually what I had to do anyway more or less. Still your help has been very welcome and I really appreciate it. Thanks.
  5. Since my last post my interrupts problem hasn't occurred, been a few days now. I am hoping my issue may have been fixed. Not really sure how though. I think it may have something to do with my internal card reader (which I think is connected to an internal USB port?) as one of my troubleshooting steps included uninstalling that (then Windows redetected it), but I also changed the drivers on my internal modem. Anyway we'll see, thanks for your help thus far.
  6. Hi, thanks for your response.... yes it seems to. What do you mean "without stack traces"? How do I get these? Or do you mean the Memory dump? You will see in an earlier post I offered to upload the memory dump for inspection. Would this help? MagicAndre1981 - was your post #467 aimed at me?
  7. I didn't get much response from cluberti I'm afraid. He did reply to my PM, by PM, saying that he would look at my trace in a few days time, but that was ages ago well before you asked him in this topic. I've since sent a reminder PM but got no reply from that, so maybe he's too busy to help. Maybe when he has some free time he will respond. In the meantime, recently it has seemed a little better, going somewhat longer between occurrences of the interrupt problem. I have no idea why or even if it's just my imagination but I'll keep observing and let you know if I find anything else out.
  8. OK, great, I'll do that, thanks. Ask cluberti, that is. I wouldn't hold out much hope of MS helping.
  9. I think I answered that in post #390. It sounds like this topic isn't the answer I hoped it would be. Basically I cannot understand why there is no tool available that can show what device is using the interrupts. Surely Microsoft should have invented this by now. I would have thought it was an essential part of any OS to know when and what devices are calling for action, but xperf isn't really helping here. Is there another tool that can do what I need? Having said that I do want to thank you for your help and effort. I really appreciate it even if in this instance the answer wasn't found.
  10. Another new trace when the problem re-occurred:!162 This was with all the USB things disabled that I mentioned.
  11. The problem occurred yesterday again, I tried to disable AVG but there doesn't appear to be any way to do so without completely uninstalling. I can disable individual elements, so I just disabled the Identity Protection feature but it didn't seem to make any difference. I have disabled all my USB devices (I think) in Device Manager now so will see if that has an effect. I'll post a new trace if/when the problem occurs next time.
  12. Sorry our posts crossed, see my EDIT2.
  13. Hi, thanks again for your efforts. As far as I can find out I already updated my HD audio and display drivers from the Asrock web site months ago and nothing is found if I search for updated drivers from Device Manager. Yes I have one of those (card reader - connected via internal USB) along with a webcam, printer, erm...oh, a wireless joystick, erm...that's it I think. Other things are plugged in as and when needed like my phone, camera etc but not while I've been doing the traces here. Haven't tried but I'll try disabling it next time the problem occurs. I wouldn't want to leave it disabled for long. Is the IDSFilter.sys just related to the Identity Protection feature? If so could I just disable that particular part? As discussed above the display is integrated on the MB so I've always just used the drivers from Asrock. To my knowledge I am using the latest ones from them. EDIT - Actually I may be wrong, I have a vague memory that maybe I did use a driver directly from Intel some time ago. Dev Mgr shows it as v. dated 23/09/2009 from Intel so that sounds like what I did. I'll have another look there at Intel website now. EDIT2 - Yep that looks like the latest driver, (strangely also numbered as Intel now describes it as discontinued so I don't know if they're updating it anymore?
  14. Hi, me again, I have uploaded a new trace as requested. Here is the link:!162 Please note that I had to compress it twice so you will need to uncompress it twice. This now is without the USB HDD caddy or the sptd driver. Thanks, hottroc.
  15. Hi, now we know, the problem re-occurs even with the external HDD caddy completely disconnected. So it's not that. Tbh, I was hoping there was a way to find out the cause of the interrupt problem without going through a process of elimination of every hardware and software driver possible. I was hoping that was what this topic would give me.