Windlg crash with BEX - I'm out of ideas

WD Internal Drives Desktop & Mobile Drives
1

Hi all,

Today I tried to run windlg to test an HDD. I’ve run it several times in the past with no problem. Suddenly, it fails: upon startup, after getting my approval to the License Agreement, it crashes with the BEX error code. Details pasted below.

Reboot, reinstall windlg 1.24 - nothing helps. Crashes. (Win7 64 Ultimate).

The weirdest datapoint is this. I started suspecting malware, so I booted the machine off a diagnostics CD (Hiren CD). It has windlg 1.24 included. I start it up. It silently dies. 

I’m lost. Other than that, the machine works perfectly. What can I do?

Thanks for any insight.

Error details: 

Problem signature:
  Problem Event Name:	BEX
  Application Name:	WinDlg.exe
  Application Version:	1.24.0.0
  Application Timestamp:	4d926f29
  Fault Module Name:	WinDlg.exe
  Fault Module Version:	1.24.0.0
  Fault Module Timestamp:	4d926f29
  Exception Offset:	00047072
  Exception Code:	c000000d
  Exception Data:	00000000
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	8dc0
  Additional Information 2:	8dc0b4a650a3028cd2ac94eaf46d0b44
  Additional Information 3:	5921
  Additional Information 4:	592190362695506a3fcfd8358a3356c9

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
2

Searching “Problem Event Name: BEX” turned up a number of instances, many game-related. Adding “windlg” to the search found one WD support reference for WINDLG error messages. There was a hint in the Google extract of the page that a cable MIGHT be at fault. At least, that is an easy thing to try.

Here is a link to a Microsoft response-

http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_programs/problem-event-name-bex-error-message/cf5baf73-0877-4070-abfb-a2c3a17a9e10

From that-

BEX refers to Buffer Overflow Exception. For more details on BEX, kindly visit http://technet.microsoft.com/en-us/library/cc738483(WS.10).aspx

Also, labeled Most Helpful Reply-

“right click on my computer
go to properties
click on advanced system settings
under performance, click settings
click the Data Execution Prevention tab, and then click Turn on DEP for all programs and services except those I select.
click Add, browse to the executable file for the program and add it.”

This is all a bit dated (2009) and in reference to other software. It might give you some leads, though

1 Like
3

Thanks for your response and taking the time to search!

I should have been more clear - I posted here only after exhausting Google etc., including the DEX solution etc.

None of those helped.

After endless trials and errors, I found the problem about half an hour ago. It has to do with a multi-port 5.25" bay adapter, one of those 99-in-one with front USB, FireWire, audio and multi flash card reader.  The card readers are connected via USB to the mobo; turns out the CF card reader developed some weird issue out of the blue that would cause windlg.exe to die with that error.

Once I disconnected that particular reader, windlg runs happily.

You can only imagine how long it took to isolate this problem.

Many thanks!

4

That is really strange. I’m sure it was a chore to sort out. I can only guess that WINDLG polls the USB ports for drives so that the card reader was able to crash it.

Congratulations on your success! (We really need a “Thumbs Up” smily around here!)

5

Wow, this thread saved me a lot of heartache.  Thanks so much OP.  I was getting application crash with BEX code also, and no info on web about that code.  Per your post I disconnected my multi-cardreader from mobo, and then app would launch again!  Weirdest part is that I then RE-connected the cardreader and rebooted, and the app would still launch ok.  I know the connection was ok before… maybe the unit is going bad and this will just happen randomly.  But at least I am aware of it now.  Don’t think I ever would have figured this one out on my own.  Thanks again!

6

The111 wrote:

Wow, this thread saved me a lot of heartache.  Thanks so much OP.  I was getting application crash with BEX code also, and no info on web about that code.  Per your post I disconnected my multi-cardreader from mobo, and then app would launch again!  Weirdest part is that I then RE-connected the cardreader and rebooted, and the app would still launch ok.  I know the connection was ok before… maybe the unit is going bad and this will just happen randomly.  But at least I am aware of it now.  Don’t think I ever would have figured this one out on my own.  Thanks again!

I’m really, really glad this helped you. It was so weird that I thought it was totally unlikely to happen anywhere else, but summarized anyway, and lo and behold - here you are…

It’s great that my efforts could help others as well. Thanks for reporting.