Windows 7 x64 - Application not responding when closing some applications

L

leelo

Well-Known Member
Joined
Aug 17, 2005
Messages
246
Reaction score
0
Location
Durban
I'm been scouring the InterGoogle for an answer on this.
Fresh install on my new i7-2600K system, fully updated proper licensed Win7 x64 HomePrem.

I saw this many moons ago during MSDN Win7 pre-release (Release Candidate).

when closing some applications, the application closes too quickly and Windows 7 thinks the application is no longer responding.
It's quite annoying, but a liveable problem. Just that I'd prefer to actually get rid of it than live with it.

Has anyone else found this and more importantly found a solution? like a close-delay registry setting or something?

Many thanks
 
Soz, I put it here (hardware), since It was only since I upgrade from Q9450 setup to the i7-2600K setup, I don't mind if it's moved to software....
 
Interesting.

Which apps are giving trouble. The only one I have issues with is iTunes.
 
LOTRO, Bad Company 2 and Word 2007 (only, not excel or outlook) weird huh? iTunes seems to close fine on mine.
 
leelo said:
LOTRO, Bad Company 2 and Word 2007 (only, not excel or outlook) weird huh? iTunes seems to close fine on mine.
Click to expand...
Well I have Home Premium, BC2 and Word2007 and never had an issue with them. Mmmmmm ...
 
Yeah, I suipport I could do that - reinstall takes less than 30min or so.... *sigh, setting up other software takes a long time though....I'd prefer to understand the root cause
 
leelo said:
Yeah, I suipport I could do that - reinstall takes less than 30min or so.... *sigh, setting up other software takes a long time though....I'd prefer to understand the root cause
Click to expand...

Sometimes the root cause is a bad install, nothing worse than spending hours wondering what the cause is only to reload. Rather get rid of a bad install upfront and if that does not work then you start looking for the issue. You know then windows is not the problem :D
 
No content with the strange behaviour, I continued the PLUG-AWAY at it until I find the cause.
It's true, I'm like a dog with a bone with these kind of things, I don't give up until I figure it all out.

SO, guess what - I've fixed the problem - not with a reload, but with something strange that I thought I should share.

It turns out that the Manual for the Sabertooth P67 motherboard lists the RAM slots incorrectly and that Placement of your RAM on a p67 is actually quite important.
See, I've got two sticks of 1.5v Vengence memory an 8Gb kit. The manual says you MUST slot them in Slot 1 and 3.
So I did that on install and everything seemed fine - until I had these "closing too quickly" problems that I mentioned above.

I later noticed that in a few monitor programs that it listed my RAM as slot 2 and 4 - and it clicked, so I moved them and VOILA! problem solved.

The reason behind the correct placement is quite a strange one on the P67 board, the initialization of the PCI/USB etc etc no longer has a direct path to the RAM during POST when the memory is not initialized from SLOT1 - when in the wrong slot, RAM access is then channelled back to the Northbridge and controlled by the CPU and then sent to the South Bridge. The knock on effect is that you actually don't initialize South Bridge hardware until after OS has loaded.

Anyway - thats my basic explaination for the day - I can now dig a hole and put the bone back.... :p
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X