BSOD while plugging development kit in USB

#1
Hello friends,
I am using Texas Instruments C5515 USB Stick DSP Development Kit. Although the device does not give any error with other PC's( Win 7 -x64), when I plug it to my PC(Asus N53S Laptop-Win7-x64) crash dump occurs. The .dmp file is attached to this mail. Any help will be appreciated..

Regards.
yusufs
 


Attachments

Trouble

Noob Whisperer
#2
Hello and welcome to the forum.
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff80002ca1074, fffff8800357ddd8, fffff8800357d630}
[COLOR=#ff0000][U][B]Probably caused by : ftdibus.sys[/B][/U][/COLOR] ( ftdibus+91fa )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca1074, The address that the exception occurred at
Arg3: fffff8800357ddd8, Exception Record Address
Arg4: fffff8800357d630, Context Record Address
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!IofCallDriver+14
fffff800`02ca1074 fe4a43          dec     byte ptr [rdx+43h]
EXCEPTION_RECORD:  fffff8800357ddd8 -- (.exr 0xfffff8800357ddd8)
ExceptionAddress: fffff80002ca1074 (nt!IofCallDriver+0x0000000000000014)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000043
Attempt to write to address 0000000000000043
CONTEXT:  fffff8800357d630 -- (.cxr 0xfffff8800357d630)
rax=0000000000000000 rbx=fffffa80059bd1b0 rcx=fffffa8009517c70
rdx=0000000000000000 rsi=fffffa8010c00000 rdi=0000000000000001
rip=fffff80002ca1074 rsp=fffff8800357e010 rbp=00000000fffffa80
 r8=0000000000000000  r9=fffff88003317180 r10=fffffa8005816960
r11=fffffa80090c8e10 r12=fffffa80059a8c70 r13=0000000000000002
r14=fffffa8009517c70 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IofCallDriver+0x14:
fffff800`02ca1074 fe4a43          dec     byte ptr [rdx+43h] ds:002b:00000000`00000043=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000001
EXCEPTION_PARAMETER2:  0000000000000043
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec9100
 0000000000000043 
FOLLOWUP_IP: 
[COLOR=#ff0000][U][B]ftdibus[/B][/U][/COLOR]+91fa
fffff880`091a11fa ??              ???
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from fffff880091a11fa to fffff80002ca1074
STACK_TEXT:  
fffff880`0357e010 fffff880`091a11fa : fffffa80`059bd1b0 fffffa80`09517c70 fffffa80`10c00000 00000000`00000700 : nt!IofCallDriver+0x14
fffff880`0357e040 fffffa80`059bd1b0 : fffffa80`09517c70 fffffa80`10c00000 00000000`00000700 fffffa80`10c00000 : [COLOR=#ff0000][U][B]ftdibus[/B][/U][/COLOR]+0x91fa
fffff880`0357e048 fffffa80`09517c70 : fffffa80`10c00000 00000000`00000700 fffffa80`10c00000 fffff880`fffffa80 : 0xfffffa80`059bd1b0
fffff880`0357e050 fffffa80`10c00000 : 00000000`00000700 fffffa80`10c00000 fffff880`fffffa80 fffffa80`0af1fc00 : 0xfffffa80`09517c70
fffff880`0357e058 00000000`00000700 : fffffa80`10c00000 fffff880`fffffa80 fffffa80`0af1fc00 fffff880`0357e090 : 0xfffffa80`10c00000
fffff880`0357e060 fffffa80`10c00000 : fffff880`fffffa80 fffffa80`0af1fc00 fffff880`0357e090 fffff880`0357e0a8 : 0x700
fffff880`0357e068 fffff880`fffffa80 : fffffa80`0af1fc00 fffff880`0357e090 fffff880`0357e0a8 fffffa80`0a16a530 : 0xfffffa80`10c00000
fffff880`0357e070 fffffa80`0af1fc00 : fffff880`0357e090 fffff880`0357e0a8 fffffa80`0a16a530 00000000`00060000 : 0xfffff880`fffffa80
fffff880`0357e078 fffff880`0357e090 : fffff880`0357e0a8 fffffa80`0a16a530 00000000`00060000 fffff880`0357e098 : 0xfffffa80`0af1fc00
fffff880`0357e080 fffff880`0357e0a8 : fffffa80`0a16a530 00000000`00060000 fffff880`0357e098 fffff880`0357e098 : 0xfffff880`0357e090
fffff880`0357e088 fffffa80`0a16a530 : 00000000`00060000 fffff880`0357e098 fffff880`0357e098 fffff800`c000009d : 0xfffff880`0357e0a8
fffff880`0357e090 00000000`00060000 : fffff880`0357e098 fffff880`0357e098 fffff800`c000009d 00000000`00000000 : 0xfffffa80`0a16a530
fffff880`0357e098 fffff880`0357e098 : fffff880`0357e098 fffff800`c000009d 00000000`00000000 00000000`00000000 : 0x60000
fffff880`0357e0a0 fffff880`0357e098 : fffff800`c000009d 00000000`00000000 00000000`00000000 00000000`00000023 : 0xfffff880`0357e098
fffff880`0357e0a8 fffff800`c000009d : 00000000`00000000 00000000`00000000 00000000`00000023 00000001`09060000 : 0xfffff880`0357e098
fffff880`0357e0b0 00000000`00000000 : 00000000`00000000 00000000`00000023 00000001`09060000 fffff880`0357e0d0 : 0xfffff800`c000009d
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  [COLOR=#ff0000][U][B]ftdibus[/B][/U][/COLOR]+91fa
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: ftdibus
IMAGE_NAME:  [COLOR=#ff0000][U][B]ftdibus.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  499aab24
STACK_COMMAND:  .cxr 0xfffff8800357d630 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_[COLOR=#ff0000][U][B]ftdibus[/B][/U][/COLOR]+91fa
BUCKET_ID:  X64_0x7E_[COLOR=#ff0000][U][B]ftdibus[/B][/U][/COLOR]+91fa
Address this pre-Windows7 RTM release driver
ftdibus.sys 2/17/2009 Ftdi USB to Serial Adapter FTDI Drivers
Update, uninstall or rename, your options your choice.
A single dump file is not much information to go on so, if Blue Screens persist;
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7...you-filling-your-system-specs.html#post235529 .
Good luck
Randy
 


#3
Hello,
Firstly thanks for your quick reply. I tried updating FTDI drivers, it seems to be updated when I checked driver version from device manager. However blue screen problem still exists. Actually, I don't see blue screens when I plug the device to the other Win 7 / 64bit computers in our office. I attach the required data that you have said to this message. I hope it will work for you. Thanks for your interest in my problem. Best regards...
yusufs
 


Attachments

#4
Hello,
Would you please help me ?
yusuf
 


Trouble

Noob Whisperer
#5
Sorry for the delay, I've been away on vacation for the past week.
All of your dump files are still indicating an issue with the
ftdibus.sys 2/17/2009 FTDI Drivers
I have no idea which device you are using but you may very well need to download the appropriate file(s) and perform a manual update from within device manager.
Driver Install - Manual Method
  • Download the driver and extract it to a folder.
  • Open the Device Manager.
  • Right click the device you wish to change the drivers for. You can select Properties > Driver > Driver Details to check you have the right device.
  • Choose Update Driver Software.
  • Select Browse My Computer For Driver Software.
  • Select Let me pick from a list of device drivers on my computer.
  • Select Have disk...
  • Select Browse..
  • Navigate to the extracted folder and double click on the .inf file
  • Hit OK, then Next and the driver(s) will then begin to install.
  • After it has installed, GoTo C:\Windows\System32\Drivers. Locate the driver you've just updated, right click it and check the dates under its properties.
Additionally you have one additional old driver on your system
ASMMAP64.sys 7/2/2009 LENOVO ATK Hotkey ATK0101 ACPI UTILITY Lenovo Support - Home (US) you should probably address that as well by performing a driver update.
Regards
Randy
 


Last edited:
#6
You are welcome . Thank you very much for all your help. I think I solved the problem:)
I reinstalled the latest FTDI drivers and for now no BSOD's exist. I hope it will be stable.
Thanks for everything...
Sincerely...
Yusuf
 


Trouble

Noob Whisperer
#7
Go to hear.
Thanks for posting back and updating your thread with that information regarding the solution that worked for you.
Hope to continue to see you around the forum.
All the best
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.