adrian5683 adrian5683

WindowFX 5 crashes explorer

WindowFX 5 crashes explorer

Seems this is an age old problem... I already have an elevated support ticket with SD. I'm using Windows 7 64-bit and running WindowFX 5 which I just installed about an hour ago. Every time I have to reboot/shut down my pc explorer crashes with this error:

"The instruction at 0x69016fd0 referenced memory at 0x69016fd0. The memory could not be written."

Is anybody else experiencing anything like that?

 

Edit: My apologies, I'll post this in the feedback thread. Could a moderator please delete this thread? Thank you.

157,419 views 72 replies
Reply #26 Top

Quoting ebeneezergeezer, reply 25
Uninstalled WindowFX and withdrew my support ticket. I feel tricked into beta testing software.

"Have you contacted support" is the automated answer to every post here, it seems. But this is not a petition, which a certain amount of people has to subscribe to.

I recommend not looking into people's systems, but into the code of the software.

Tons of people on Win 7 x64 have the issue.

Only the software developers cannot reproduce it. Go figure.

 
End of ebeneezergeezer's quote
The information we've gleaned from user reports have allowed us to modify the code to address (and resolve) a number of issues.

Reply #27 Top

Quoting ebeneezergeezer, reply 26
"Have you contacted support" is the automated answer to every post here, it seems
End of ebeneezergeezer's quote

This is because support has something to give you that should fix the issue.  I'm not sure why you're responding in this way when we are literally doing nothing except trying to help you.

Reply #28 Top

Quoting Rosco_P, reply 24
Quoting nbarn, reply 24I have the same problem, runnning windows 7x64.

It's so annoying that i have stopped using FX 5

Have you contacted support@stardock.com yet?
End of Rosco_P's quote

Hi, No i haven't contacted support as yet, and it seems i don't have to now since they are going to release an updated version.

I wrote that i was having the same memory address problem to show that it isn't just a minor isolated problem.

Reply #29 Top

Just in praise of rplies #11 and #15.

The Support people are fully willing and able to put things together [devs and knowledge] to help people with problems with any of SD's apps. 

 

That said, there's no rule against helping them with as much info as possible... after all, the end user is interested in making it work as designed.

The more they know and can tie together, the better and more quickly one is helped.

Just a thought.

Reply #30 Top

All is well here, due to our support team!   5* 5* 5* 5* 5*

Reply #31 Top

Well. excuse old grumpy boots here.

Quoting Rosco_P, reply 27
This is because support has something to give you that should fix the issue
End of Rosco_P's quote

Are you saying that there is a fix? I can't find an update in my downloads...

Reply #32 Top

I too have the exact same error, I've contacted the support and hope they have a fix for it soon otherwise I have to uninstall the application

Reply #33 Top

Testing with the people who have contacted support shows that the issue seems to have been resolved in the updated build, so I would expect the build to be released to everyone else at some point this week.

Reply #34 Top

Quoting Neil, reply 33
I would expect the build to be released to everyone else at some point this week.
End of Neil's quote

:thumbsup:

I too have the W7 64 shutdown error, I just can't be bothered to moan about it ;)

Reply #35 Top

i don t have contact the support team  atm because the problem is mostly recent in my case. Can we hope the release of the update this week or not finally?

Reply #37 Top

If anyone is having this issue, you can either wait until we roll it into an official update, which should be soon, or you can contact support@stardock.com and we can send you the fix.

Reply #38 Top

Quoting Rosco_P, reply 38
If anyone is having this issue, you can either wait until we roll it into an official update, which should be soon, or you can contact support@stardock.com and we can send you the fix.
End of Rosco_P's quote

Hello, I have the same problem, I have installed windows 7 64 bit, I hope that it will be resolved soon.
It would be possible to windowFX 5 in Spanish?, we would be many grateful customers.
Sorry for my English.
Best regards.
Reply #39 Top

Quoting ganymedes2, reply 38

Quoting Rosco_P, reply 38If anyone is having this issue, you can either wait until we roll it into an official update, which should be soon, or you can contact support@stardock.com and we can send you the fix.


Hello, I have the same problem, I have installed windows 7 64 bit, I hope that it will be resolved soon.
It would be possible to windowFX 5 in Spanish?, we would be many grateful customers.
Sorry for my English.
Best regards.
End of ganymedes2's quote
Try uninstalling and re-installing.  the installer has been uptaded with the latest fix.

Reply #40 Top

Quoting Zubaz, reply 39
Try uninstalling and re-installing. the installer has been uptaded with the latest fix.
End of Zubaz's quote

I just reinstalled WFX5 and have a question.

After install, it prompts for a serial number. Only trouble is, while the Registration window is open, waiting for a number, SDC can't be accessed to get the number.  Q: How is that supposed to work?o_O

You have to use the link in the Registration box and/or go to the store and login to get the number. SDC or the store is fine, but I shouldn't need both to install and register software.

Reply #41 Top

Quoting Wizard1956, reply 40
Only trouble is, while the Registration window is open, waiting for a number, SDC can't be accessed to get the number. Q: How is that supposed to work?
End of Wizard1956's quote
Good point.  I'll talk to the SDC dev.

Reply #43 Top

Quoting ganymedes2, reply 42
WindowFX in Spanish?
End of ganymedes2's quote
Not likely.  :(

Reply #44 Top

version 5.1.0.0??

my download section indicates that windowfx is in build 5.00.001. :rolleyes:

Reply #45 Top

Update on the registration number  issue on SDC:

 If I click on View Serial  before installing WFX5, it tells me no number is needed. After install, it then asks for a Registration number which SDC can't give. ;P

Reply #46 Top

Bonjour

Avez vous trouvé une solution au problème :

"L'instruction à 0x00000000 référencé la mémoire à 0x00000000. La mémoire ne peut pas être écrite."

Merci

___

Hello

Have you found a solution to the problem:

"The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written."

thank you


Reply #47 Top

Quoting lecajef, reply 46
Bonjour

Avez vous trouvé une solution au problème :

"L'instruction à 0x00000000 référencé la mémoire à 0x00000000. La mémoire ne peut pas être écrite."

Merci

___

Hello

Have you found a solution to the problem:

"The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written."

thank you


End of lecajef's quote
Uninstall the version you have and reinstall the version available through Stardock Central.

Reply #48 Top

Quoting <span><span>Zubaz</span></span>, reply 48
Désinstallez la version dont vous disposez et réinstaller la version disponible par le biais Stardock Central.
End of <span><span>Zubaz</span></span>'s quote

Bonjour Zubaz,

Je vous remercie.

C'est avec plaisir que j'ai pu constater que le problème à été résolu.

Je vous souhaite une bonne journée

Jef

___

Hello Zubaz,

Thank you very much.

It is with pleasure that I could see that the problem has been solved.

Have a good day

Jef

Reply #49 Top

Vous êtes les bienvenus. Je suis désolé je n'ai pas pu répondre hier française mais je suis heureux que vous avez pu comprendre.

You are very welcome.  I'm sorry I was unable to respond in French yesterday but I am glad you were able to understand.

Reply #50 Top

Quoting Wizard1956, reply 45
Update on the registration number  issue on SDC:

 If I click on View Serial  before installing WFX5, it tells me no number is needed. After install, it then asks for a Registration number which SDC can't give.

End of Wizard1956's quote
Should be fixed.  Let me know if it's not.