Whenever I launch a 64bit program with a few minutes of it running I get a pop-up window with nothing in it. I'm guessing its some sort of windows warning/error message because it shows a yellow-bounded exclamaion mark in window header - but theres just no text anywhere to hint at what the problem might be...
The 64bit program just behaves like it does when it loses focus and continues to run fine after I close the mysterious warning window, but its a nuissance and I dont know what to do about it.
I've increased my ram from 8gb to 16gb in case its a RAM issue - but that didn't help.
None of my drives have less than 100gb free on them and I defrag regularly, and I have a
system managed page-file.
I thought it may be a windows aero problem, and tried to set the programs' compatibility property to disable visual themes and desktop composition - but these seem to be greyed out for 64bit apps...
Anybody any ideas?
Winows7 home - fully updated.
mobo: asus p8z77-v lx - latest bios
cpu: intel I5-3570k
gpu: nvidia 770 - driver updated jan 2016
ram: 16gb (4x4)
no problems as such, except now windows wont boot (BSOD after the initial windows logo appears). I've not done a fresh windows7 install after the update, but I was thinking a repair was all it would take. But the repair fails ("windows can not repair this installation") and I can only do a fresh intsall.
Should I go with the fresh-install or is there a workaround to repair it? (Is this UEFI thing the problem?). I already found a fix for the MBR vs GPT UEFI windows install problem, but wondering if its blocking the repair now somehow...?
when I power it on I get lots (>20) short beeps then it powers itself off.
the mobo has UEFI dual bios printed on it - the manual says its AMI EFI bios.
nowhere can I find an explanation of >20 short beeps except for AWARD bios which says its a power issue. BUT I DONT HAVE AWARD BIOS...???!?!?! (or do I?)
could anybody help?
They used to call it a page-fault, but now its hard-fault. Now I see in your quote the term 'hard-page-fault'. Are they the same things?
When I used to work on mainframes they used 'swap-files' as a cheap alternative to physical memory. When processor time is critical for clearing transaction queues then using slow-speed hard-drive swap-files is something you try and avoid where possible (using real-time priorities). If we could afford to have all physical memory then that's what we'd have done (though a finacially stupid idea for low-priority batch applications). In this day of cheap physical memory and relatively low usage I cant see a single reason for using page-files - unless modern OS' have some unaddressed legacy requirement for having one...
I ran quite a few memory hungry programs (I have 8gb RAM), and when COMMIT showed 6/8 I got the "windows is low on memory" warning.
I gave windows a 4GB pagefile and tried again. COMMIT is now showing 2/11 (GB) and I can easily load up a lot more memory hungry programs than last time before getting the "low on memory" warning..
so is HARD FAULT really meaning hits to the pagefile, or just hits to the hdd to get program data?
I believe it's just to the hdd.
I rarely use more than one menory hungry program at a time (eg: games, video editing etc) so I feel happy in ditching my pagefile for good, especially when I have an additional 8gb of physical RAM being delivered in a few days (unless somebody can give a good reason for keeping a pagefile?)
When I have a pagefile configured I can see it in windows explorer on the C: drive, I can no longer see or find any pagefile on any drive which would indicate there's no actual physical pagefile on the disk so where is windows 7 hard-faulting its pages from?
I just bought a MSI gtx 770 and now a little worried - the card has 2 x 8 pin power sockets but my PSU only has 2 x 6 pin power leads. The card comes with 2 x 6 pin to 8 pin converters so was wondering if anybody could advise if its ok to use them, or do I need to upgrade my PSU?
current psu GXS700
Now I think about it, I uninstalled Security Essentials last year because it would occassionally tell me that windows needed a genuine test, and that SE would refuse to run until I had. So I did, and it was happy. Then a few weekes later it would tell me again. I uninstalled it when I got fed up of seeing those messages.
Is this some ploy by MS to wear me down until I upgrade from XP? :)
anyway - re-installed SE and looks like I'm clean of viruses, so I dont know what the hell happened...