ntdll.dll failure after vba Int (random num)

[Wayne-I-M]

I am getting a system freeze on a specific terminal - the freeze is the
result of an ntdll.dll failure but I don't have a clue what's doing this and
why this dll would fail.

I have tried to come up with the simplest test I could so I have send key
Setocus to a button (with no OnClick event) then send key {ENTER} after a
random amount of time (well sort of random) between 25 min and (approx 41
mins.

I don't think the send keys will cause anything to fail - ??

Me.testbutton.SetFocus
Dim RandomNumber As Integer
'txtRandomNumber is an unbound box'
me.txtRandomNumber = Int((2488 - 1500 + 1) * Rnd + 1500)
PauseTime = txtLRandomNumber
Start = Timer
Do While Timer < Start + PauseTime
DoEvents
Loop
SendKeys "{ENTER}", True



Without the Int (it's a simple random number as you can see) it works fine.

Any ideas what may be causing this.

It only happens on one terminal - I have reinstalled access. Run updates.
etc.
Nothing changes. I still get the same result - the system freezes.

It I can't fix will probably just through this lap top away, but I do like
to try and fix things if possible


Does anyone have any ideas as to why a Int would cuase the freeze in the
ntdll.dll

 

[Stefan Hoffmann]

hi Wayne,

I am getting a system freeze on a specific terminal - the freeze is the
result of an ntdll.dll failure but I don't have a clue what's doing this and
why this dll would fail.

A problem may be memory corruption. What does freeze means? BSOD?



mfG
--> stefan <--

 

[Paul Shapiro]

hi Wayne,


A problem may be memory corruption. What does freeze means? BSOD?



mfG
--> stefan <--

Access has historically been sensitive to graphic drivers. Maybe check for
updates from the graphic card manufacturer? Seems unlikely that an Access'
computation is crashing the system all on its own. Too many users on too
many computers.

 

[Wayne-I-M]

A problem may be memory corruption. What does freeze means? BSOD?

Sorry for my English - I "think" freeze is used to say that access crashes
but with UI still useable. So you can use the mouse, keyboard but you are
not able to operate access. So you can select a string in a text box, but
you can not delete it. You can place the pointer over a button but left
click (or anyother UI) does not work.
If "freeze" is not correct I hope you understand.

:
Access has historically been sensitive to graphic drivers. Maybe check for
updates from the graphic card manufacturer? Seems unlikely that an Access'
computation is crashing the system all on its own. Too many users on too
many computers.

I have disabled the graphics card (and phisically taken out the video card)
from the terminal. It will freeze even when taken off the network.

The strange thing is that it "seems" to be only a call on the Int function
that cuases this problem.

I think I have a solution. I will replace this terminal with a new one and
store the damaged terminal in a box for a few months . If this sodes not
solve the problem it will be thrown out.

Thanks for trying to help. Sometimes it really is a case of TWAIN + TWASP
(solvable problem

 

[david]

I am getting a system freeze on a specific terminal - the freeze is the
result of an ntdll.dll failure but I don't have a clue what's doing this
and
why this dll would fail.

I have tried to come up with the simplest test I could so I have send key
Setocus to a button (with no OnClick event) then send key {ENTER} after a
random amount of time (well sort of random) between 25 min and (approx 41
mins.

I don't think the send keys will cause anything to fail - ??

Well, it will cause any error messages to disappear, which is probably not
what you would like in this situation.

(david)