i allways have stop bluescreens like page_fault_in_nonpaged_Area or i_ivqa or something like that and win32k.sys in the techinikal information...what can it be?(its happen all the time no mather what i do on the computer...i have xp sp2..
thanks

welcome to dal the online computer help forum

i have done a bit of research on the net and this is what i have come uop with

Firstly did you update any Drivers or Direct X prior to this problem happening? If you did see if you can revert to the previous drivers and see if it still happens.

Try reinstalling DirectX and then reinstall your graphic card and soundcard drivers.

Do a complete file check within the EQ patcher to ensure that you have all the latest files.

I did a search on the stop error - Stop: 0x0000008E and win32.sys on the Microsoft website. This is one Knowledge Base article that may assist you.

http://support.microsoft.com/default...b;en-us;834450

One other possibility is that your machine is infected with the HaxDoor Virus - since another Knowledge base article mentions this as a possibility. This article can be found here:-

http://support.microsoft.com/default...b;en-us;903251


Another possible cause of a Stop: 0x0000008E error is faulty Ram. It may have become faulty or my not be seated properly in their sockets. If you can and do know what you are doing remove them and reinsert them to ensure they havent worked loose.

After having read through the Microsoft website it would seem that the general consensus of opinion is that the latest service packs do sort out many of the issues that cause this problem. Do you regularly keep your Windows installation up to date with the Windows Update? Its worth doing if you don't.

are you getting any stop error messages like the one i have listed if so could you please let me know which one t is so that i can look at it further


hoipe this helps

i allready tried what you said and the first guide but about the second...
i think its going to work i just need to find my xp instalation disk..thank you i hope i will not back unless its to say thanks...

please let me know if it works and if it doesnt please come back to me so that i can help you more

ok what you sent isnt working and my computer now compleatly got crazy and he allso allways freezing and show me another screen:
IRQL_NOT_LESS_OR_EQAL
what the hell can it be?

Please post the exact error message. I know it is a full page but we need to see it.

Otherwise try this:

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.

the log:
Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers



and listen:
the blue screen is really normal the only thing write there is to check bios and delete drivers(at least thats what i understood)

the techinikal information of IRQL blue screen is: STOP:000000000A...
and...those screens work together one time this one and 1 time the other and one time frezeing the percent is 33% lol

That is just the start of a log. Either you didn't let the WIZ run all the way or you just copied the first part. These logs are very long. Scroll the whole window when copying please.

As to IRQL 0XA they are so common and varied we need to know what triggered them.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
“Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
“Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)
How to Use Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003

http://aumha.org/win5/kbestop.htm

log:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Aug 17 10:05:48.962 2005 (GMT+2)
System Uptime: 0 days 0:53:20.532
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
.................................................. .................................................. ...........
Loading unloaded module list
.............
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {7d7e000d, ff, 0, 804db65c}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for nv4_disp.dll -

We are still not getting a full log. You are still just getting the start of it.

Such a log would look like this:

http://www.d-a-l.com/help/attachment...tachmentid=635