Windows error 0x00000098, 152

Detailed Error Information

TOO_MANY_MUXWAITERS[1]

MessageDosMuxSemWait did not execute; too many semaphores are already set.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070098.

END_OF_NT_EVALUATION_PERIOD[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x98: END_OF_NT_EVALUATION_PERIOD.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code152 (0x0098)

Possible solutions

5

unknown arm linux kernel image format

linux
kernel
arm

ARM Linux kernels are usually self-loading plain binaries, generated from the original ELF by extracting the code+rdata sections from it and appending the "piggy" loader. They're loaded by the bootloader at some place in the memory and just run from there. The piggy loader unpacks/copies the main payload to the final address and jumps to it.

Restoring ELF from the binary might be possible (the final runtime address is usually fixed to 0xC0008000, and you can find out .data/.bss ranges by analyzing boot code), but the symbol table is trickier. Recent kernels don't use ELF symbol table as-is but employ compression to save space. If you can boot the kernel, the easiest way is to read /proc/ksyms or /proc/kallsyms as it will have the symbols in uncompressed format. Otherwise you'd have to find the compressed table in the binary and decompress it manually.

answered on Stack Overflow Feb 11, 2013 by Igor Skochinsky
2

UIWebView loading html5-Video EXC_BAD_ACCESS crash

iphone
objective-c
uiwebview
exc-bad-access
html5-video

There is a little trick to override this crash. If you slightly scroll the webview just before the video content is loaded, the crash can be avoided. Before trying it out from code, try scrolling the webView a bit on device with your finger. It won't crash now.

In code, do something like this:

- (void)webViewDidFinishLoad:(UIWebView *)webView
{
  [webView stringByEvaluatingJavaScriptFromString:@"window.scrollTo(0, 10);"];
}

to simulate a scroll on the webview through javascript. The scroll value can be as low as 1, so the user won't notice the scroll at all.

answered on Stack Overflow Feb 24, 2011 by Srijith Vijayamohan • edited Feb 24, 2011 by Srijith Vijayamohan
2

Analyzing crash dump file from Windows 2003 R2 SP2

windows-server-2003
server-crashes
bsod

I'm not the best OS debugger, but here's what I see:

PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced.

What often causes this is a "use after free" condition where memory is freed, and then a thread references it as if it were still allocated. When a user-mode program does this, it usually just ends up crashing that program. But when a kernel-mode component, such as a driver, does this, it causes a bug check. It can also be caused when a thread attempts to write to an address that is marked as read-only. But because argument two of the error code specified that the fault occured during a read operation, we can eliminate that possibility.

Other things can cause this bug check as well, such as faulty hardware, and cosmic rays flipping bits in your RAM. But for the sake of discussion we'll disregard those possibilities as well.

If you look at the stack text - this stands out to me:

ExFreePoolWithTag+0x67b fffffadf1fb33360

That function freed pool memory, which is in kernel space. I'm not positive that it freed the memory that was later referenced that caused the machine to crash, but I'm highly suspicious of it. It is typically drivers that allocate and deallocate pool memory. The people who write drivers have to be extremely careful about allocating and deallocating memory, because if you don't do it perfectly, you either cause a memory leak or you crash the machine.

If you look here, you'll see the parameters of your bug check code:

Parameter       Description
---------------------------    
1   Memory address referenced    
2   0: Read operation   1: Write operation    
3   Address that referenced memory (if known)    
4   Reserved

Windbg identified sptd.sys as a probable cause of the crash. I'm guessing Windbg figured that sptd.sys is the culprit because it happened to be loaded in the address that was found in argument 3 of the bug chuck code. (But I could be wrong about that. I'm not sure how Windbg derives that information.) The information is not guaranteed to be accurate in any case, but stpd.sys appears to be a non-Microsoft driver related to CD/DVD burning software like Daemon Tools and Alcohol 120%.

I would definitely start by either upgrading or uninstalling that software.

Edit: Looks like you can find updated versions of sptd.sys here: http://www.disc-tools.com/download/sptd

answered on Server Fault Mar 24, 2013 by Ryan Ries • edited Mar 24, 2013 by Ryan Ries
1

UIWebView loading html5-Video EXC_BAD_ACCESS crash

iphone
objective-c
uiwebview
exc-bad-access
html5-video

Telling the webview to evaluate any JavaScript (or none at all) on webViewDidFinishLoad: seems work (albeit hacky).

- (void)webViewDidFinishLoad:(UIWebView *)webView
{
  [webView stringByEvaluatingJavaScriptFromString:@""];
}
answered on Stack Overflow Feb 28, 2011 by sbelous
1

UIWebView loading html5-Video EXC_BAD_ACCESS crash

iphone
objective-c
uiwebview
exc-bad-access
html5-video

Seems I've solved this issue... i've moved all HTML-5 video tags insertion in Javascript

function placeVideoTag() {
   var val = '<video />';
   var el = document.getElementById('video-id');
   el.innerHTML = val;
}

And i'm calling JS in [UIWebView didFinishLoad]

- (void)webViewDidFinishLoad:(UIWebView *)aWebView {
   [aWebView stringByEvaluatingJavaScriptFromString:@"placeVideoTag()"];
}

Works perfectly in my case. Other suggestions didn't work for me.

answered on Stack Overflow May 11, 2011 by tt.Kilew
0

UIWebView loading html5-Video EXC_BAD_ACCESS crash

iphone
objective-c
uiwebview
exc-bad-access
html5-video

I have exactly the same problem. no answer yet. Saw many others reports similar problems - iOS 4.2.1 only.

Basically, I have a UIView Controller with a webview as its subview, and load a URLRequest to a youtube link.

The first time I load the viewController, the console logs error "Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Internet Plug-Ins/QuickTime Plugin.webplugin/QuickTime Plugin (file not found).". I stop loading and release the viewController. The second time I re-load new viewController with the same request to that youtube link, now the app crashed with EXC_BAD_ACCESS

answered on Stack Overflow Feb 18, 2011 by xingzhi.sg
0

UIWebView loading html5-Video EXC_BAD_ACCESS crash

iphone
objective-c
uiwebview
exc-bad-access
html5-video

Thanks, for your posts!!! In my case it only works with different quite high offset-values for Portrait- and Landscape-Mode on iPad

(Portrait-Mode: greater than 60; Landscape-Mode: greater than 780):

- (void)webViewDidFinishLoad:(UIWebView *)webView
{
    if (self.interfaceOrientation == UIInterfaceOrientationPortrait ||
    self.interfaceOrientation == UIInterfaceOrientationPortraitUpsideDown) {

        [webView stringByEvaluatingJavaScriptFromString:@"window.scrollTo(0, 60);"];
    } else if (self.interfaceOrientation == UIInterfaceOrientationLandscapeLeft ||
           self.interfaceOrientation == UIInterfaceOrientationLandscapeRight) {

        [webView stringByEvaluatingJavaScriptFromString:@"window.scrollTo(0, 780);"];
    }
    webView.loadCounter--;
}

But with this solution my app crashes by double-tapping to zoom during the loading-process of a site.

I did subclass UIWebView to solve this problem (to prevent webView from zooming while loading):

.m:

@synthesize loadCounter;

- (UIView *)hitTest:(CGPoint)point withEvent:(UIEvent *)event
{
    CGPoint p = currentPoint;
    NSTimeInterval t = currentTimestamp;
    currentPoint = point;
    currentTimestamp = [event timestamp];

    if (CGPointEqualToPoint(p, point) &&
        [event timestamp] - t < 0.2 && loadCounter > 0){
        return self.superview;
    }

    return [super hitTest:point withEvent:event];
}

.h:

@interface NonDoubleTapableWhileLoadingWebView : UIWebView {
    CGPoint currentPoint;
    NSTimeInterval currentTimestamp;

    NSInteger loadCounter;
}

@property (assign) NSInteger loadCounter;

And added a counter to determine the last "didFinish"-call and to reactivate the double-tapping possibility (init loadCounter with 0)

- (void)webViewDidStartLoad:(UIWebView *)webView {
    linkWebView.loadCounter++;
}
answered on Stack Overflow Mar 2, 2011 by Florian

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0