Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Go Back   OSR Online Lists > windbg
Welcome, Guest
You must login to post to this list
  Message 1 of 4  
11 Mar 18 10:22
Mark Roddy
xxxxxx@gmail.com
Join Date: 06 Jul 2011
Posts To This List: 21
Re: WER/CrashAPI 2655: ERROR Invalid args, too big block.

some app is having a bad time. Mark Roddy On Sat, Mar 10, 2018 at 8:34 PM, xxxxx@rolle.name <xxxxx@lists.osr.com> wrote: > What does this mean. I see about 30 of these lines in the debugger when I > load my driver on the target. > > > --- > WINDBG is sponsored by OSR > > OSR is hiring!! Info at http://www.osr.com/careers > > <...excess quoted lines suppressed...> --
  Message 2 of 4  
11 Mar 18 19:51
Michael Rolle
xxxxxx@rolle.name
Join Date: 07 Mar 2018
Posts To This List: 5
Re: WER/CrashAPI 2655: ERROR Invalid args, too big block.

Could you please elaborate? Is the error happening on the host or the target? And what is WER and CrashAPI? BTW, your reply to my original post somehow wound up in a new thread, instead of being added to the original thread.
  Message 3 of 4  
11 Mar 18 20:28
Michael Rolle
xxxxxx@rolle.name
Join Date: 07 Mar 2018
Posts To This List: 5
Re: WER/CrashAPI 2655: ERROR Invalid args, too big block.

It seems to be related to Visual Studio on the target. When I launch it and open a Solution, then about 15 of these messages appear in the host debugger. If I close and reopen the Solution, then another 15. Perhaps VS has a driver that is using DbgPrint with the VDRIVER device?
  Message 4 of 4  
12 Mar 18 18:09
Mark Roddy
xxxxxx@gmail.com
Join Date: 06 Jul 2011
Posts To This List: 21
Re: WER/CrashAPI 2655: ERROR Invalid args, too big block.

WER is windows error reporting. This is just user mode noise getting output on the kernel debug console. Generally you can ignore it unless you are like a registry or file system filter driver and you are *causing* the apps to crash. This is all happening on the target system. Mark Roddy On Sun, Mar 11, 2018 at 8:27 PM, xxxxx@rolle.name <xxxxx@lists.osr.com> wrote: > It seems to be related to Visual Studio on the target. When I launch it > and open a Solution, then about 15 of these messages appear in the host > debugger. If I close and reopen the Solution, then another 15. > Perhaps VS has a driver that is using DbgPrint with the VDRIVER device? > > > --- > WINDBG is sponsored by OSR > > OSR is hiring!! Info at http://www.osr.com/careers <...excess quoted lines suppressed...> --
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the windbg list to be able to post.

All times are GMT -5. The time now is 17:50.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license