Help with BSOD

Pastor098 · Nov 10, 2010

Hi all, I'm new to this site - so forgive me for posting in the wrong forum. Hopefully the mod's will move it for me! :wave

I work at a fairly large corporation, and have just implemented SAP into our environment. Since SAP has come along, there is a department that uses SAP very heavily, and their machines Blue Screen and reboot randomly throughout the day. I'm thinking this could be RAM related - and possibly 2GB just isn't enough to handle heavy SAP usage. It is only this department having this issue, and all of the team members are experiencing it.

Wondering if someone could take a look at the minidump attached, and let me know your thoughts. I have today installed an extra 2GB RAM in two of the machines - so will see over the coming days if this has helped or not.

Any more info you require, just let me know!

Thanks,
Cam

satrow · Nov 10, 2010

Welcome Cam
It looks like a kernel stack overflow http://www.carrona.org/bsodindx.html#0x0000007F

0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

* A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
* A hardware problem.
Click to expand...

Cause

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.
Resolving the Problem

Debugging: Always begin with the !analyze extension.

If this extension is not sufficient, use the kv (Display Stack Backtrace) debugger command.

* If kv shows a taskGate, use the .tss (Display Task State Segment) command on the part before the colon.
* If kv shows a trap frame, use the .trap (Display Trap Frame) command to format the frame.
* Otherwise, use the .trap (Display Trap Frame) command on the appropriate frame. (On x86-based platforms, this frame is associated with the procedure NT!KiTrap.)
Click to expand...

There's a lot more detail on that site that will help you figure this out, good luck and keep us informed on progress?

Pastor098 · Nov 17, 2010

Hey, thanks for the reply. Yeah I managed to google it, and found the page you are referring to. But still, I have no idea how to resolve a Kernel Stack Overflow problem!! haha - hence posting the problem on this site. I am trying my best to work out this debugging tool...but it seems to be beyond me at the moment.

We are trying a few things:

* Upgrading RAM (problem hasn't occurred since)
* Upgrading to XP SP3 (Just did this last night - testing now)
* Install a BIOS update (haven't done this one yet!)

Anyone know how to resolve a Kernel Stack Overflow problem!?

Cheers,
Cam

satrow · Nov 17, 2010

Resolving it depends on the cause. Try checking these out (from the same carronna.org link):

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem.

If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack.
Click to expand...

Keep testing until you have more info to work from.

Log in or Sign up

Help with BSOD

Pastor098 Private E-2

Attached Files:

BSOD.txt

satrow Major Geek Extraordinaire

Pastor098 Private E-2

satrow Major Geek Extraordinaire