C# SerialPort KERNEL_SECURITY_CHECK_FAILURE

I'm using SerialPort class to read and write data from an USB device that use USB CDC class. My Program is called CameraControl.
Often I get blue screen with KERNEL_SECURITY_CHECK_FAILURE
Below WinDbg analysis
* Bugcheck Analysis *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd00020d51470, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd00020d513c8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
OVERLAPPED_MODULE: Address regions for 'niorbk' and 'IntcDAud.sys' overlap
TRAP_FRAME: ffffd00020d51470 -- (.trap 0xffffd00020d51470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe001e1d400b8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe001e5cf6c28 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800c73f0414 rsp=ffffd00020d51600 rbp=ffffe001e1a87080
r8=fffff800c73f03c0 r9=0000000000000012 r10=0000000000000000
r11=fffff80209967897 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
usbser+0xa414:
fffff800`c73f0414 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffffd00020d513c8 -- (.exr 0xffffd00020d513c8)
ExceptionAddress: fffff800c73f0414 (usbser+0x000000000000a414)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: CameraControl.
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - Il sistema ha rilevato un sovraccarico di un buffer basato su stack in questa applicazione. Il sovraccarico potrebbe consentire a un utente non autorizzato di assumere il controllo dell'applicazione.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Il sistema ha rilevato un sovraccarico di un buffer basato su stack in questa applicazione. Il sovraccarico potrebbe consentire a un utente non autorizzato di assumere il controllo dell'applicazione.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff802099667e9 to fffff8020995aca0
STACK_TEXT:
ffffd000`20d51148 fffff802`099667e9 : 00000000`00000139 00000000`00000003 ffffd000`20d51470 ffffd000`20d513c8 : nt!KeBugCheckEx
ffffd000`20d51150 fffff802`09966b10 : ffffe001`e7dc0440 00000000`00000000 ffffe001`00000001 ffffd000`20d514c0 : nt!KiBugCheckDispatch+0x69
ffffd000`20d51290 fffff802`09965d34 : 00000000`00000000 ffffe001`e7956de8 ffffc001`e05c6320 fffff800`c377ccb2 : nt!KiFastFailDispatch+0xd0
ffffd000`20d51470 fffff800`c73f0414 : 00000000`00000306 00000000`00000000 00000000`00000050 00000000`000007ff : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`20d51600 fffff800`c73f0470 : ffffe001`e5cf6c18 00000000`00000000 ffffe001`e1aa4400 00000000`00000000 : usbser+0xa414
ffffd000`20d51630 fffff800`c73ef9a1 : ffffe001`e53ffa00 ffffe001`e5cf69d0 ffffe001`e5cf6880 00000000`00000010 : usbser+0xa470
ffffd000`20d51660 fffff802`09bdcab2 : ffffe001`e17bf780 ffffe001`e17bf780 00000000`00000000 ffffe001`e7546680 : usbser+0x99a1
ffffd000`20d51690 fffff802`09bed5fa : ffffe001`e1aa43d0 ffffe001`e0d88dc0 ffffe001`e1aa43e0 ffffe001`e1aa4300 : nt!IopCloseFile+0x152
ffffd000`20d51720 fffff802`09bed3f3 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`00000001 : nt!ObpDecrementHandleCount+0x1b6
ffffd000`20d517c0 fffff802`09bed02e : ffffe001`e1a8c080 fffff802`09855114 00000000`00000000 00000000`00000002 : nt!ObCloseHandleTableEntry+0x313
ffffd000`20d51890 fffff802`09d641f6 : ffffe001`e1a87080 ffffe001`e1a7e400 ffffc001`ed9e17c0 00000000`00000001 : nt!ExSweepHandleTable+0xba
ffffd000`20d518f0 fffff802`09b9506a : ffffd000`245d7713 ffffd000`245d7713 ffffe001`e1a87348 ffffffff`00000040 : nt! ?? ::NNGAKEGL::`string'+0x32c16
ffffd000`20d51960 fffff802`09c2f6cb : 00000000`e1a87088 00000000`e1a87088 00000000`c000010a 00000000`00000000 : nt!PspRundownSingleProcess+0x286
ffffd000`20d519f0 fffff802`09c2f3d1 : ffffe001`e1def880 ffffe001`e1a7e400 ffffe001`e1a87080 ffffe001`e1a87080 : nt!PspTerminateAllThreads+0x27f
ffffd000`20d51a50 fffff802`09c2f15e : ffffffff`ffffffff ffffe001`e10c0080 ffffe001`e1a87080 ffffe001`e1a7e080 : nt!PspTerminateProcess+0xe5
ffffd000`20d51a90 fffff802`099664b3 : ffffe001`e1a87080 ffffe001`e1a7e080 ffffd000`20d51b80 00000000`0000159c : nt!NtTerminateProcess+0x9e
ffffd000`20d51b00 00000000`77022772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0ff6eac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77022772
STACK_COMMAND: kb
FOLLOWUP_IP:
usbser+a414
fffff800`c73f0414 cd29 int 29h
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: usbser+a414
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbser
IMAGE_NAME: usbser.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f890
IMAGE_VERSION: 6.3.9600.16384
FAILURE_BUCKET_ID: 0x139_3_usbser+a414
BUCKET_ID: 0x139_3_usbser+a414
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_usbser+a414
FAILURE_ID_HASH: {f38f031c-a840-6c18-f377-c47aa3e1dec1}
Followup: MachineOwner
I'm using Windows 8.1 PRO and this problem is very embarrassing for my clients.
Thank you

Hello tazzo,
According to this
article, the issue seems to be related with the system as it describes that “This bug check indicates that the kernel has detected the corruption of a critical data structure”.
I would suggest that you could post this issue to:
http://answers.microsoft.com/en-us
Best Regards,
Fred.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Windows 8 crashes and with the error "kernel_security_check_failure" after installing Boot Camp drivers.

Hi!
I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
All help is greatly appreciated!

I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise. After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD. This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON!
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Am conrtacting them, but, here's the Debugger output:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
*                        Bugcheck Analysis                                    *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29            int     29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2            xor     edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner

Problem with characters from SerialPort

Hii!! My problem is: How to convert the characters of SerialPort ??
For example, I receive from SerialPort:
sESB="U��U��U��+��"DDDDDDDDDDDDDDDDDDZ#�fffffffffffffffffffffffffffffffffff�"
my programa for convert is:
public String getASC(String sESB)
     String sASC = "";
     CharToByteConverter cb = CharToByteConverter.getConverter("CP500");
     sEBC = new String(cb.convertAll(sESB.toCharArray()));
     return sASC;
but I obtain :
��{��"��]��W
I want to obtain normal characters, for example 'hello' .
Thanksss

Hi!! My way for convert the bytes is :
private String readData()
byte[] buffer = new byte[32];
try
while( IS.available() > 0 ){ int numBytes = IS.read(buffer); }
catch (IOException e)
return( new String(buffer) );
First, for example I obtain 'OK', 'CARRIER DETECT'... this works fine, but then the data I need are:
UUU+??\"DDDDDDDDDDDDDDDDDDZ#?ffffffffffffffffffffffffffffffffff
I don't know .... help!! Thanksssssssssssss

Endless SerialPort Reading

Hello there!
I have implemented the code Kevin Le made and it works perfectly.
It is a windows form that allows you to configure, open, read, write and close a COM Port in a wonderful and straightforward way. All of that using the serialPort class.
Due to the nature of my project, I need not only to read it once (through the 'read' button) but to read it as long as I want continously. Basically, I'm receiving data in any moment and I need to be able to capture it and save it into a SQL database (Haven't
figure that yet). Right now, I'm able to capture the buffer by clicking the button and save the data to a .txt file. I just want to make the program an automatically reader.
Any idea?

You are looking for the
DataReceived event on the SerialPort class. Attach a delegate to that event and it will be called anytime there is data to read. When your delegate is called, then call the Read method

In serialport- write() i have a error

in serialport->write(System::string) getting error.but we include serialport->write(std::string) means it get executed.How we include System:: string in serialport->write.

If it is a native class, then use the managed SerialPort class or try this:
#include <msclr/marshal.h>
msclr::interop::marshal_context mc;
serialport->write( mc.marshal_as<string>( some_String ));
Then show the error details.

My application hangs after 10 hours in the serialport read sub-vi. Why?

My application is programmed under LabView 5.1.1 on a windows 2000 platform.
I use a MOXA RS232 extending module with a B&B RS485- converter.
After 10 hours trouble-free working, the application, using semaphores, hangs in the serialport read sub-vi.
In the same constelation without RS485-converter, once the application hanged up in the serialport write sub-vi. After Restarting LabView I was still not able to access the serial port. So I had to restart the PC.

I am not sure, but it looks for me as some buffer overflow error.
Like you read or write something before it is ready.
Try to play with the lines like DTR and so on.
regards
PP
Isildur wrote:
>
> My application is programmed under LabView 5.1.1 on a windows 2000
> platform.
> I use a MOXA RS232 extending module with a B&B RS485- converter.
> After 10 hours trouble-free working, the application, using
> semaphores, hangs in the serialport read sub-vi.
> In the same constelation without RS485-converter, once the application
> hanged up in the serialport write sub-vi. After Restarting LabView I
> was still not able to access the serial port. So I had to restart the
> PC.

Data from SerialPort

Does anyone know how to read data from voltage probes connected to a serialport? I got javax.comm to compile and the port (COM1) is being recognized, but I am having trouble actually reading the data. I am confused on how to use inputstream or if it will even work for what I want to do...any thoughts?
Thanks
...the probes are actually connected to an analog which is connected to a serialport--does that make a huge difference?...is it still possible to read the volts?

You need to look into the javax.comm API.
Read this, and you shall see the light:
http://www.javaworld.com/javaworld/jw-05-1998/jw-05-javadev.html

SerialPort Read Timeout

Anyone knows how to achieve SerialPort Read Timeout? Or in another way to say it, stop reading from the SerialPort.

Remove the Serialport listener Maybe !

Please help: kernel_security_check_failure

Hello,
today i have got after month of running without problems a kernel_security_check_failure.
Here are the links for dump an msinfo:
https://onedrive.live.com/redir?resid=6EBE47BA73D67E80%21108
https://onedrive.live.com/redir?resid=6EBE47BA73D67E80%21109
Thank you

Hi,
According to the dump file, it looks like network device caused this problem, please try to reinstall your NIC driver for test. In addition, do you install any security software in your system?
Roger Lu
TechNet Community Support

SerialPort: inputStream.read blocks, never return -1

I use javax.comm package to transfer files between two virtual com ports (looped)
Send a file from com3, and receive file from com4, but at reciever side, inputStream.read(buffer) never return eveb though I close the outputstream at the sender.
Here is code:
is: serialPort.getInputStream();
os: serialPort.getOutputStream();
//sender:
//fis: FileInputStream
try {
     int i =0;
     while ((counter=fis.read(buffer)) > 0 ){
          fileSize += counter;
          debugInfo(i + ": "+counter + "bytes read");
          os.write(buffer,0,counter);
          i++;
     debugInfo(fileSize + " bytes read totally");
     os.flush();
     fis.close();
     //close os when no file need transfering
     os.close();
} catch(IOException e) {
     e.printStackTrace();
}file receiver
fos: FileOutStream
try {
     int i =0;
     while ((counter=is.read(buffer)) >0){ //blocks and never return
          counter=is.read(buffer);
           fileSize += counter;
           debugInfo(i + ": "+ counter + " bytes read");
           fos.write(buffer,0, counter);
           i++;
debugInfo(fileSize + " bytes write totally");
fos.flush();
fos.close();
debugInfo("fos closed");
is.close();
} catch(IOException error) {
     error.printStackTrace();
}Anything I have done wrong? or anything better solution? Thanks

oops, sorry for copied wrong codes. Thanks for your remind. The second read was used with while (is.availble()), when I post, I forgot to remove it. You are right, if I have read twice, I will not even get the right file, since I only write every second buffer in.
Here I update the receiver, I can get the whole file correctly, but can't get EOF.
//file receiver
//fos: FileOutStream
try {
     while ((counter=is.read(buffer)) >0){ //blocks and never return
          fileSize += counter;
           fos.write(buffer,0, counter);
fos.flush();
fos.close();
is.close();
} catch(IOException error) {
     error.printStackTrace();
}

Window 8.1 Kernel_Security_Check_Failure

My PC ran into problem , The window is 8.1 ,this is not before window 8.1 ,This error started after i have installed the window 8.1
Plz tell me what will be the process to resolve this problem.
The error is
KERNEL_SECURIT_FAILURE_CHECK
Plese suggest me something to resolve out this problem
Crazy learner

Hello,
I'd ask in the
Windows 8.1 IT Pro forums if this is a machine in a corporate environment, or in the
Windows 8.1 forum on Microsoft Community if this is your personal PC.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Getting KERNEL_SECURITY_CHECK_FAILURE (bugcheck: 0x00000139) crash every day

Sometimes it's twice a day. Every time I come back to my computer and find that it's on the login screen, I know that it crashed and rebooted. I think there could be some connection to the USB subsystem. Often times, my keyboard won't work after a crash,
and I'll have to plug it into different USB port to get it to work.
Below are links to the most recent minidump files. While the parameters may differ each time, it's always the same driver (ntoskrnl.exe) and the same crash address (ntoskrnl.exe+150ca0).
http://1drv.ms/1OhFvdG
http://1drv.ms/1Dn4dio
http://1drv.ms/1DEyyZ2

CB
Before anything else you need to update drivers from as far back as 2004 Including
Related to SIWinAcc.sys Windows Accelerator Driver from Silicon Image, Inc.
Related to SiRemFil.sys Filter driver for Silicon Image SATALink controllers. from Silicon Image, Inc.
THEN, you need to run driver verifier to find the under lying issue
These crashes were related to memory corruption (probably caused by a driver).
Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first. You do not need to run memtest yet unless you want to.
If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! If you do not know what this means you probably are not
1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)
Wanikiya and Dyami--Team Zigzag

Java SerialPort using COMM API

Hi All,
I am trying to develop a java program that will dial a GSM modem and send some data over it.For developing this i am using java rxtxcomm API with jdk 1.6_38 on windows 7 OS.I am using notifyOnDataAvailable method in order to listen to any incomming data.
The following is the set of steps i need to perform
1) I am first executing AT command to check if the modem is connected or not
outpursteam.write("AR\r");
the above statement should return OK if the modem is connected.
2) then i will try to dial the number using DTD<modileNo> which should return CONNECT 9600.
if the remote party is nor responding or some problem in dialing the above command will returrn ERROR
3) Once the connection is open and no operation is performed for 1 Minute the connection will be closed by the destination which will be indicated By NO CARIER message.
when i run my program the first statement will return OK so now i am dialing the specified destination number (Step 2) it should return CONNECT 9600 but i did not get any message.After 1 minute i am getting both CONNECT 9600 and NO CARIEIER message together.
Can some one help me in resolving this problem
Thanks&Regards
kishore.m

Presumably step 2 has a \r on it.

Binary Output On Serialport

Hi,
I am trying to send numbers from 0 to 255 over the serial port. Locally I can convert an integer to a byte by a cast. However, if I write this byte in the Outputstream with the OutputstreamWriter, all values from 128 to 160 get lost. Instead I recive the value 63.
Using a workaround with ISO-8859-1 makes it possible to send all values except 129,141,143,144,157. Again, these are replaced by the value 63.
OutputStreamWriter aus = new OutputStreamWriter(main.out);
int value;
String s;
s = new Character((char) i).toString();
s = new String(s.getBytes("ISO-8859-1"));
aus.write(s);For the communication I am using the RxTx library under Windows XP pro.
How can I write binary code to the serial port?

If you want write byte per byte (not very effective) :
DataOutputStream aus = new DataOutputStream(main.out);
int value;
aus.writeByte(value);If you want write more efficiently, gather data into byte arrays, and write into a buffered output.
DataOutputStream aus = new DataOutputStream( new BufferedOutputStream(main.out) );
byte [] values;
//fill values, assuming numberOfValuesInArray is the number of bytes
// in values that must be written, with numberOfValuesInArray<=values.length
aus.write(value, 0, numberOfValuesInArray);
//Don't forget to flush after writing the last array of values, or at any time you want to force data output on underlaying stream.
aus.flush()

Serialport readbyte not reading the correct data

Hello everybody
I'm writing a software in VB.net to communicate with an external device with modbus I have a problem while reading data received from the device , to put it in example , using
sp1.ReadByte() the data sent from the device is this :
05-03-04-00-00-01-9F-FE-0B
but I receive this
05-03-04-01-9F-FE-0B
I use this to read Data
Dim reponse As Byte() = New Byte(5 + (2 * nombre_registrre - 1)) {}
For i As Integer = 0 To response.Length - 1
response(i) = CByte(sp1.ReadByte())
Next
It seems like 0x00 are ignored , I tried to send stream of hex manually and Ive got the same problem , always readbyte ignore 0x00 bytes
Why is that ?
thank you so much for your help
Hey :)

you are expecting 9 bytes ..
is (5 + (2 * nombre_registre - 1)) = 9 ... No that is impossible the answer of this equation will always be even
therefore
for i as integer = 0 to responce.length-1
dont read 9 bytes ... it will read an even number of bytes.
Something is wrong in your code
I don't think it's has someting to do with my buffer length , If so why do I receive the other bytes (Not 0x00 bytes)
as I said before , the only bytes I can not receive are 0x00 , I think its something with readbyte() function
Hey :)

C# SerialPort KERNEL_SECURITY_CHECK_FAILURE

Similar Messages

Maybe you are looking for