Random PC Crash during N2 Serial Tunnel
When connected to a site via serial tunnel, I am getting random PC crashes. The crash is the "Blue Screen of Death" and I must power off to restart the laptop. I have tried this on different laptops and different locations with the same results.
One day I worked on a site and commissioned three different systems all day long without a problem and other times I have tried to download a small program to an FX05 and as soon as I connect, the PC crashes.
Has anyone else had similar a similar experience? Johnson says they have no problem with it (imagine that!). I am using a Dell D830 laptop and a cable modem high speed internet connection. Any pointers would be GREATLY appreciated!
What OS do you have on the Laptop ? Hopefully not Vista.
If sense were so common everyone would have it !
All opinions expressed are my own. Any advice provided is based on personal experience, generally accepted fact or publicly available information. As such, it is worth exactly what you paid for it, not a penny more not a penny less !!
Windows XP Professional SP3
The problem is most likely caused when you click on the X at the top right to close out the fx comm pro.
If so, when done with the comm pro instead click file then either exit or close (i forget which) this has eliminated the problem for me.
let me know.
Since my original encounter with this problem, I have found that exiting CommPro seems to give me an IRQ error blue screen. Other times, as I said before, I get a different blue screen while discovering controllers, downloading/commissioning, or just doing nothing. The IRQ error only seems to occur on exit. I will try using the File/Exit instead of the red X and see if it helps the IRQ error. I have also talked to Milwaukee about this again and they have been in contact with Tridium. I questioned the serial tunnel.txt file that refers to version 1.2 and the installed version off of the Workbench CD is 1.1. The .txt file indicated a problem with 128 bit word errors. I have not been able to find this mythical version 1.2 and have had no reponse from Johnson as of yet.
Thanks for your reponse to this aggrivating problem!
If you post the core dumps (xp default will generate them) or post the "cryptic" error message shown on the BSD I can either tell you exactly why it crashed or at least point you in the right direction. The core dump file is more helpful and xp by default will generate them so unless you've changed the default settings they'll be there. The error message will only give you the reason it crashed with no information as to why that condition existed in the first place.
Guess that didn't work - I have screen shots of each error
Last edited by MrEddySpag; 11-07-2009 at 12:31 AM.
Reason: Added comment
Originally Posted by MrEddySpag
You'll probably have to put them up on an image hosting site and link to them.
edit: Is there no way to PM anyone on this site? I get "The administrator has restricted this function" when I try to view the member list.
Last edited by D1G; 11-07-2009 at 12:58 AM.
Reason: I'm probably missing something completely obvious.
Those indicate the device driver is "crashing" (parent directory is normally %WINDIR%\SYSTEM32\DRIVERS\) in both images but in different portions of allocated memory.
Originally Posted by MrEddySpag
There was at one point an issue where if you ran out of virtual memory you could get the same "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and simply increasing the size of your VM would work around it. If your box has been patched in the last couple years I'm almost positive this has been fixed.
Since your issue spans different hardware and your faults are occurring in different sections of allocated memory I would point the finger at your application passing bad code (argument, request, etc..) to the system.
The BSOD screens offer very little insight into the nature of the issue. If you're lucky the offending execution will have produced an event when it occurred before it snowballed into the system crashing. What does Event Viewer have logged?
I cleared the event log and started a serial tunnel connection. I downloded a controller, commissioned, and was just navigating between controllers and then crashed. This looked like an entry that looked like something related. What do you think?
Event Type: Error
Event Source: Serial
Event Category: None
Event ID: 36
Time: 9:32:52 PM
While validating that \Device\Serial1 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers. The device is assumed not to be a serial port and will be deleted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 24 00 06 c0 ....$..À
0010: 3e 00 00 00 00 00 00 00 >.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: e8 02 00 00 00 00 00 00 è.......
The link to Microsoft's knowledge base has no further information.