Jump to content

kodel

Member
 View Profile  See their activity

  • Posts

    1

  • Joined

  • Last visited

Reputation Activity

  1. Like
    JGTC.co.jp
    kodel got a reaction from JGTC.co.jp in [GUIDE] LGA 771 Mod for Dell Vostro 220(s)   
    You fixed it!
    I modded my Vostro 220 a few years ago and had the same problem: very laggy windows 10 system due to high DPC and ISR CPU usage. Flashing your modded bios based on 1.2.0 immediately solved the problem.
    I didn't need to disable Speedstep or C1E support. I only disabled C-STATE.
     
    Thank you for sharing!
     
    Additional info:
    For the last 2 years I had Apple OS X installed on my Vostro. Strangely enough, the C-STATE incompatibility didn't effect OS X. It only caused a problem for Windows 10.
  2. Like
    Nobody.jp
    kodel got a reaction from Nobody.jp in [GUIDE] LGA 771 Mod for Dell Vostro 220(s)   
    You fixed it!
    I modded my Vostro 220 a few years ago and had the same problem: very laggy windows 10 system due to high DPC and ISR CPU usage. Flashing your modded bios based on 1.2.0 immediately solved the problem.
    I didn't need to disable Speedstep or C1E support. I only disabled C-STATE.
     
    Thank you for sharing!
     
    Additional info:
    For the last 2 years I had Apple OS X installed on my Vostro. Strangely enough, the C-STATE incompatibility didn't effect OS X. It only caused a problem for Windows 10.
  3. Like
    oskarha
    kodel got a reaction from oskarha in [GUIDE] LGA 771 Mod for Dell Vostro 220(s)   
    You fixed it!
    I modded my Vostro 220 a few years ago and had the same problem: very laggy windows 10 system due to high DPC and ISR CPU usage. Flashing your modded bios based on 1.2.0 immediately solved the problem.
    I didn't need to disable Speedstep or C1E support. I only disabled C-STATE.
     
    Thank you for sharing!
     
    Additional info:
    For the last 2 years I had Apple OS X installed on my Vostro. Strangely enough, the C-STATE incompatibility didn't effect OS X. It only caused a problem for Windows 10.
×