Call Search
     

New to Ham Radio?
My Profile

Community
Articles
Forums
News
Reviews
Friends Remembered
Strays
Survey Question

Operating
Contesting
DX Cluster Spots
Propagation

Resources
Calendar
Classifieds
Ham Exams
Ham Links
List Archives
News Articles
Product Reviews
QSL Managers

Site Info
eHam Help (FAQ)
Support the site
The eHam Team
Advertising Info
Vision Statement
About eHam.net

   Home   Help Search  
Pages: [1]   Go Down
  Print  
Author Topic: Help, Ham Radio Deluxe causing computer crash  (Read 2675 times)
NZ5N
Member

Posts: 774


WWW

Ignore
« on: April 09, 2009, 08:32:32 AM »

I have been using HRD successfully for over a year with my IC-756 Pro II. Recently I bought a new USB CAT cable to control my IC-7000. The computer is a Lenovo desktop running Windows Vista. I was able to connect to the 7000 and control the rig with HRD for about 30 seconds. Then, my computer gave me a blue screen error message and crashed. Here is the message:
***********************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 00000004, A NULL parameter was passed to a function that required a non-
NULL value. Use the "ln" debugger command with the value of
Parameter 3 as its argument to determine the function which
requires a non-NULL parameter.
Arg2: 8076c3d2, Reserved.
Arg3: 00000000, The caller's address.
Arg4: 86077630, Reserved.

Debugging Details:
------------------


BUGCHECK_STR: 0x10D_4

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: HamRadioDeluxe.

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8077570c to 81b1f0e3
***********************

I then moved the new cable over to the 756. Same result, a computer crash after about 30 seconds, although with a different error message:

************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000004c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80778fc1, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81b3e868
Unable to read MiSystemVaType memory at 81b1e420
0000004c

CURRENT_IRQL: 2

FAULTING_IP:
Wdf01000!FxIrpQueue::InsertIrpInQueue+12
80778fc1 897a4c mov dword ptr [edx+4Ch],edi

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: HamRadioDeluxe.

TRAP_FRAME: aea36950 -- (.trap 0xffffffffaea36950)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=8629e704 edx=00000000 esi=861cb6f8 edi=861cb72c
eip=80778fc1 esp=aea369c4 ebp=aea369d0 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
Wdf01000!FxIrpQueue::InsertIrpInQueue+0x12:
80778fc1 897a4c mov dword ptr [edx+4Ch],edi ds:0023:0000004c=?HuhHuh?
Resetting default scope

LAST_CONTROL_TRANSFER: from 80778fc1 to 81a61d24
****************************

Anyone run into this type of problem? Any fix? I assume it has some connection with the new USB cable, as I never had this problem with the old cable.

73, Bill NZ5N
Logged
KB9PZA
Member

Posts: 5




Ignore
« Reply #1 on: April 09, 2009, 09:02:34 AM »

go and update the driver for the usb cable this is the #1 thing that make it stop working
Logged
Guest

« Reply #2 on: April 09, 2009, 09:13:29 AM »

Hi Bill, check to see if your program is recognizing the USB connection in your audio settings. I had this problem using Vista also until I got it to see the USB cable.   Bill
Logged
NZ5N
Member

Posts: 774


WWW

Ignore
« Reply #3 on: April 09, 2009, 09:19:46 AM »

Thanks for the replies.  Yes, the connection is being recognized in Device Manager.  How to ensure that I have the latest drivers?  When I first attached the USB, it would not recognize the device, but it did after I installed the Windows Vista driver for prolific chip USB Serial Adapters from
http://www.cooldrives.com/wividrforprc.html.

73, Bill
Logged
GW0DIV
Member

Posts: 122




Ignore
« Reply #4 on: April 09, 2009, 09:56:49 AM »

Some of the Prolific USB to serial chipsets do funny things to Vista, especialy 64 bit versions. I got a USB cat lead for the '706 that crashed the PC instantly. So I replaced it with a serial lead and USB to serial lead, which turned out to have the exact same Prolific chip set but worked perfectly!?! Now to confuse the issue more I tried the USB/serial/cat combo on the '706 and the USB/cat lead on the 7400 and it all ran for 2 or more hours before the return of the blue screen of death! Think I'll try a quality USB to 2 or 4 way serial adapter with serial cat leads, or an internal serial card on the PC. The Prolific chips seem a little hit and miss to me.

Rhys
GW0DIV
Logged
N6AJR
Member

Posts: 9906




Ignore
« Reply #5 on: April 10, 2009, 11:37:04 AM »

I have had good luck with the Keyspan HS19 device, any other serial to usb converter may or may not work for ham radio, but he keyspan 19 HS always works.  something about the way it is wired or such, they run about 30 bucks each.
Logged
K3AN
Member

Posts: 787




Ignore
« Reply #6 on: April 11, 2009, 06:29:26 AM »

I went to the Keyspan web page for the HS-19 and found this in the System Requirements section.

Windows 98/Me/2000/XP/Vista (32bit)

It looks like the HS-19 works with 32-bit Vista only. I wonder if that's true with most or all USB to Serial converters.

Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!