Member Avatar for kenny1989

Win 7 64

Hi, this problem began when my computer/program crashed while running frets on fire.

After reboot I got a message that mscorwks.dll could not be laoded so I ran
sfc /scannow

but this did not fix it so I used takeown to take ownership of the entire folder and subfolders and deleted it and replace them with copies of the files from a fresh install (.net sp1 and sp2 files as well).

I then reinstalled frets on fire but the program is still running slow.

Anyone know what the problem is here and how to fix it?

  • 4 Contributors
  • 9 Replies
  • 267 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by kenny1989

Dani AI

Generated

Good outcome — the slowdown turned out to be a graphics‑driver issue rather than a broken .NET runtime. ‘s isolation test (clean Windows install, then adding the video driver) makes that clear and is a good troubleshooting pattern: restore the minimal environment, then add components one at a time to see which one reintroduces the problem.

Why this happens: games and other multimedia apps call native graphics APIs (Direct3D/OpenGL) or native libraries from managed code. When a video driver is corrupted or misbehaving the system can fall back to slow software rendering, hang during GPU calls, or surface errors inside the host process — which can look like a runtime problem even though the root cause is the display driver. ‘s suggestion to consider runtime cleanup is valid, but driver faults should be ruled out first.

Practical next steps for anyone hitting the same symptom:

  • Check Windows Logs (Application and System) for recent display/driver errors and for any application exceptions around the same time as the slowdown.
  • Verify Device Manager for driver warnings and note the driver version.
  • Do a clean driver reinstall from the GPU vendor (uninstall current driver, reboot, install the vendor package). If a normal uninstall leaves trouble, use a dedicated driver-clean tool before reinstalling.
  • If a new driver introduced the issue, roll back to a previously working version. Test other GPU‑heavy apps to confirm the problem is system‑wide. Only after drivers are eliminated as the cause should you run official .NET repair/cleanup tools or consider reinstalling system components.

Caution: avoid copying system DLLs or registry entries by hand — that can create signature/compatibility problems. This thread shows the faster path: check graphics drivers early when a game crashes or suddenly becomes slow.

Recommended Answers

All 9 Replies

Member Avatar for caperjack

Win 7 64

I then reinstalled frets on fire but the program is still running slow.
Anyone know what the problem is here and how to fix it?

hi,did it ever run fast

Member Avatar for Micelf

Win 7 64

Hi, this problem began when my computer/program crashed while running frets on fire.

After reboot I got a message that mscorwks.dll could not be laoded so I ran
sfc /scannow

but this did not fix it so I used takeown to take ownership of the entire folder and subfolders and deleted it and replace them with copies of the files from a fresh install (.net sp1 and sp2 files as well).

I then reinstalled frets on fire but the program is still running slow.

Anyone know what the problem is here and how to fix it?

If you're fearing that .NET is your culprit, might I suggest using the cleanup tool and re-installing it. :)


Member Avatar for kenny1989

Thing is because I use Win 7 64 it won't let me reinstall as such, hence why I installed .net 2.0 on a virtual machine and then moved the files over. Today I even copied the .NET registry files and imported them in.

If you're fearing that .NET is your culprit, might I suggest using the cleanup tool and re-installing it. :)


: I think its fairly obvious that the program in question did run faster before this incident.

Member Avatar for Bob_180_Bob

: "I think its fairly obvious that the program in question did run faster before this incident."
I didn't think it was or is obvious as you neglected to make any statement to indicate it either way.
"I then reinstalled frets on fire but the program is still running slow."
That sounds like it was always running slow!!
"this problem began when my computer/program crashed while running frets on fire." That sounded like it only just started after you installed Frets on fire!!
I think the only thing obvious is that it is not obvious what you are saying.

Edited by Bob_180_Bob because: n/a
Member Avatar for caperjack

its all obvious ,bye bye

Member Avatar for kenny1989

OK apologies if that seemed rude, it wasn't meant to be.
BUT, the title of this thread is:
.net framework program is now running slow

: "I think its fairly obvious that the program in question did run faster before this incident."
I didn't think it was or is obvious as you neglected to make any statement to indicate it either way.

As I said, thread title.

"I then reinstalled frets on fire but the program is still running slow."

I then after 'reinstalling' .net framework 2.0 reinstalled frets on fire. I think that implies I ran this program between my 'reinstall' of .net framework 2.0 and reinstall of frets on fire.

"this problem began when my computer/program crashed while running frets on fire." That sounded like it only just started after you installed Frets on fire!!
I think the only thing obvious is that it is not obvious what you are saying.

This problem (program now running slow) began when my computer/program crashed whilst running frets on fire. How does that imply that I only just installed it?

Even if you think my points are invalid I think the thread title makes it obvious.

Edited by kenny1989 because: n/a
Member Avatar for kenny1989

The problem seems fixed now, seems the graphics card driver got messed up.

Member Avatar for Micelf

Kenny,

Glad your problem was fixed, would you mind posting the video card details & what you did to correct this issue? Thanks in advance. :)

The problem seems fixed now, seems the graphics card driver got messed up.

Member Avatar for kenny1989

Kenny,

Glad your problem was fixed, would you mind posting the video card details & what you did to correct this issue? Thanks in advance. :)

My graphics card is a 9600M GT, OS as stated above is Win 7 64.

I did all the steps I desccribed in the previous posts and then decided that maybe I should try running the program on a clean install of win 7. I didn't want to lost any data so what I did was:

Shrink my drive
Install win 7 on the new partition
Try running game on that install of Win 7

It still didnt work (as in having exact same problem), but I realised that a new install would not have the gfx drivers, so I downloaded and installed them and then my game ran as before.

In short, I think just installing the gfx drivers will fix the problem.

So my problem with the game seems to have nothing to do with .net.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.