Kernel Data in Page error

itsupport · #1 (**permalink**) 16-06-2005, 11:23 AM

One of our users keeps getting this error on his dell laptop, i have got him to disconnect it from the docking station ensuring the only connection is for the network i have run boot sector virus scan adware and spybot (for good measure) and scan disk and it is still happening

the message is:

KERNEL DATA IN PAGE ERROR
windows has shutdown to prevent damage to computer (yada yada)
the tech details are: STOP 0X0000007A (0XE186A514)

jephree · #2 (**permalink**) 16-06-2005, 08:56 PM

Here is the standard 0X7A page:

http://www.microsoft.com/resources/d...d_stp_fvlq.asp

Also: look in your Event viewer: rt. click My Computer then click Manage then Event Viewer.
Or: Administrative Tools/Event Viewer or Start/Run/ eventvwr
Open the system as well as the application tabs & look for X errors. Click error line for details.
Post back the source & event id especially of errors that seem to coincide with a crash.

Also:

Go to start | search (type in) .dmp
Note the location of your latest .dmp file.

Then:

1) Download and install the
Debugging Tools from Microsoft
2) Download and install this
debugwiz
3) Open the Wiz & Browse to, or paste in the path to, your latest .dmp file.
4) After the Wiz creates a Text document attach it back to this thread.

itsupport · #3 (**permalink**) 17-06-2005, 12:52 PM

Right used the cool diagnostic tool supplied by Dell and surprise surprise no errors (this was running EXTENDED scan option so I/O, hard drive memory fan, etc)

also had a look at the event viewer and heres what i found:

From System log:
(Time) (Category) (Event)
11:49 system error 1003
Error details:
0000007A. Parameter 1 E186A514 Parameter 2. C0000009A Parameter 3. BF857C47 Parameter 4. 071A7860.

(Time) (Category) (Event)
12:09 NONE 2019
The server was unable to allocate from the system nonpaged pool because the pool was empty.

Application Log:

(Time) (Category) (Event)
12:12 EventSystem 4609

The COM+ event system detected a bad return code during its internal processing HRESULT was 800706BB from Line 44 of D:\nt_qxp\com\com1x\src\events\teir1\eventsystemob j.cpp

Hope these help

jephree · #4 (**permalink**) 18-06-2005, 03:09 AM

So are things running OK now?

As to the 4609 error I found this indirect fix:

Quote:

1) Go to Start -> Settings -> Control Panel -> Administrative Tools.
2) Run “Local Security Policy”.
3) Go to Security Settings -> Local Policies -> User Rights Assignments.
4) Double click on “Create global objects”. The correct default settings are “Administrators”, “INTERACTIVE”, and “SERVICE”.
5) Double click on ''Impersonate a client after authentication''. The correct default settings are “Administrators”, “ASPNET” (if you have the .NET Framework installed) and “SERVICE”.
Even if the settings are set correctly, you may need to “refresh” them to fix the problem. To do this, on each policy, remove one of the entries (“SERVICE” is probably the best to remove), then press OK to save the changes, and then go back in and add it back in again (click “Add User or Group...”, type “SERVICE” into the white box, and press OK). Then close the Local Security Settings box and reboot. If you are running in a domain with Group Policy, you might want to force a group policy refresh before you reboot by running “gpupdate /force”.

Also found this direct match RE: MicrosoftMoney:

The COM+ event system detected a bad return code during its internal processing HRESULT was 800706BB from Line 44 of D:\nt_qxp\com\com1x\src\events\teir1\eventsystemob j.cpp

http://groups-beta.google.com/group/...eb2b8f5d04231e

itsupport · #5 (**permalink**) 21-06-2005, 03:30 PM

Everything seems to be running ok now, i have checked and modified the settings for imporsonate and user is happy its not crashing anymore

jephree · #6 (**permalink**) 22-06-2005, 01:47 AM

Glad to hear it

Let us know if we can help further in the future!

This thread has been Resolved and Locked to prevent other users hijacking the thread and to help others know which threads have been Resolved and which are still being worked on.

If you started this thread and the problem returns or the case has not been properly Resolved, please send a Private Message to a Moderator of this forum to have the thread opened again. If you have a different problem, please start a new thread.