Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ChristSavesU2

Profile Information

  • OS
    Windows 7 x64
  1. The only way to disable the encryption password would be to decrypt the hard drive. What I did try was to not let the BIOS get completely through its process and turned off the computer before it got to the encryption password prompt. Then switched it back on and let it boot normally. That worked as well, no DPC latency issues all day.
  2. I have found out it is not a temperature issue. I tried letting the computer boot up to the hard drive encryption password, which should only have run the BIOS checks, and then hitting control, alt, delete, to reboot, and then letting it boot up normally from there. Doing this, there are no DPC latency issues all day and the computer works fine. I tried flashing the BIOS and booted normally the next day and the DPC issues are still there, but today I did the immediate reboot and it is working fine. I don't know what the change is when I do the immediate reboot, but it seems to work.
  3. I tried turning on the computer this morning and letting it sit for 30 minutes at the encrypted hard drive password prompt to make sure it was past the warm up time that causes the DPC spike and following degradation. Then when I let if finish booting I found that the DPC latencys were already bad as if I had let it boot in the first place. I downloaded the program you suggested and saved 2 reports. One before I rebooted and one after. And as always, once I rebooted the DPC latency issues are gone and it will run the rest of the day with no problems. 1temp.txt 2temp.txt
  4. After days of testing and narrowing things down, it does appear to be a temperature issue. After I had the initial problem, I shut down the computer and let it sit for about 3 hours. Started it and it was fine the rest of the day. One morning it was particularly cold and it took almost 25 minutes before I started seeing spikes in DPC times. This morning I turned the computer on and let it sir for 6 minutes before I let it start the boot process (I have an encrypted hard drive that requires a password, so I let it sit on the password prompt) and that was not long enough. It usually starts with a spike in the DPC times around 12 to 15 minutes from start-up. I have attached some informational screen shots at www.willowproperties.net/temp.html 1temp.jpg shows the list of drivers and their highest execution times right after the first spike. 1temp.txt shows the report at that same time. 2temp.jpg shows that the spike was generated from the kernel timer latency versus one of the drivers (not sure what the difference is). 2temp.txt is the report after it has run and the DPC times keep getting worse. 3temp.jpg is the screen shot of the drivers DPC times just before I reboot. You can see that there isn't one particular driver that has high DPC times, there are several. 4temp.jpg shows that both the kernel timer latency and driver DPC latency are both having issues. The end result is that it seems to be a hardware temperature issue and if I reboot after about 30 minutes of runtime the problem goes away until the machine cools off overnight. Not sure there is a fix. Your thoughts? Thanks, Ron
  5. I have found an interesting thing. The issue happens from a cold boot only and it doesn't matter what programs I run or don't run. It seems to be related to how long the computer is running. If instead I reboot the machine, even right after I first started it, it runs fine all day long. So there is something different between a cold boot and a restart that fixes things. Not sure what though. I will try the different USB configurations and see if that helps at all.
  6. Hi Andre, I could not find a setting in the BIOS for Hpet. I did find that there is a windows command to turn it on or off though here I used the command bcdedit /set useplatformclock true and verifiied it was on with WinTimerTester.exe, rebooted and it worked fine the rest of the day. The next day it had the same problem so I used the command bcdedit /set useplatformclock false, rebooted and it ran fine the rest of the day. The third day it had the same problem so I reset the command to true, rebooted and it ran fine the rest of the day. Today it had the same problem and I ran a new report which is here. I also included a Latency report because even though the issue appears to be the same the report was dramatically different than before. Thanks, Ron
  7. Unfortunately, the fix didn't last too long. Yesterday it ran all day no problems. Today within 2 hours the DPC latency starting climbing and got to high to use the computer after about 5 hours. I have attached the latest file here http://www.willowproperties.net/temp.html Thanks.
  8. In my previous post, I said I had a USB printer. I forgot that I replaced that with a WiFi printer. So the only two USB devices are the mouse and keyboard. I moved both of them to different USB ports and rebooted the computer. After running all day today the DPC latency is perfect. So far so good. Not sure why moving them to a different port helps but it has so far. I will let you know if it stays that way. Thanks for your help.
  9. So you have Audio and uSB issues. Which USB devices do you use? Does the USB controller share the IRQ with the soundchip? I have a mouse, keyboard, and a printer connected via USB. I have attached the IRQ list. It doesn't appear there are any commonalities between the two. Thanks. 1temp.txt
  10. Hi Andre. In reviewing this thread I see this problem has been going on for a long time. You would think there would be a permanent fix by now. I have been dealing with this issue on and off for almost 2 years. Lately, it is an everyday occurrence. The longer I run the computer the worse it gets. If I let it go on too long I get the BSOD. I have a Gateway SX2800-07 with a core2quad 8300 Intel processor. I have the latest drivers from Gateway, Intel, Realtek, etc... You can download the report.etl from here http://www.willowproperties.net/temp.html. I appreciate all the help you have provided to so many. Any insight you can give me would be great. Thanks, Ron
  11. Hi, I have a Gateway SX2800-07 desktop with Windows 7 64bit operating system. I have had the similar issue of occasional high system interrupts that slow my system down. I have updated all the drivers that I can find and still haven't solved the problem. You can view my traces at www.willowproperties.net/1temp.pdf and I have attached that file here as well. Any advice would be appreciated. 1temp.pdf