Various BSOD's (PAGE_FAULT_IN_NONPAGED_AREA, DRIVER_IRQL_LESS_OR_NOT_EQUAL)

Status
Not open for further replies.

SuperKoopa

Posts: 10   +0
Hi, I'm hoping you can help me. I'm getting various BSOD's at random times, all the time. They include 0x0000008e (which happens the most), STOP 0x00000050, and STOP 0x0000000A. 0x0000008e and 0x00000050 give me PAGE_FAULT_IN_NONPAGED_AREA and 0x0000000A gives me DRIVER_IRQL_LESS_OR_NOT_EQUAL. I have researched these all until my fingers are bloody and I can't find any cause. I have everything possible set right (ACPI settings correct, etc.) and I've ran RAM tests more than once and they've all passed. The BSOD's happen when I'm doing a few things at once, usually. I'm getting very frustrated and can't read the minidumps myself. Could any of you analyze them, please? Most of my symptoms are relative to the Backdoor.Haxdoor trojan but I've looked in the driver folders and such, and found nothing, as well as ran many virus and spyware tests. So can someone please help. I will post minidumps if anyone can read them. Thanks for reading my post.

-SuperKoopa

P.S. My system is an AMD Athlon 1600+ with an nvidia GeForce 5200FX, 512 MB RAM, Creative Sound Blaster card, and a Gigabyte motherboard, VIA chipset.
 
Well, I ran memtest86 and everything passed. I've also ran Windows Memory Diagnostic, and that passed as well. My BIOS settings are good. All my crashes happen because of win32k.sys-- What could this mean? What is win32k.sys? :(
 
From your description, sounds like a driver issue. I can't get more specific than that though.

But driver issues are (more often than not) a result of chipset or graphics drivers. Try installing the latest versions. If you have the latest versions, install older versions.
 
Zip 5 or 6 minidumps together, and attach them here.

You can find your minidumps in c:/windows/minidumps

Please note. techspot has a limit of 100kB per attachment, so you may need to attach several zip files.

Regards Howard :)
 
As you know your minidump crashes at win32k.sys. This is the Windows Multi-User Win32 Driver. Your minidumps also references Firefox when the crash happened. Make sure you are using the latest version of Firefox.

The bugcheck was 8E.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

It would be better if you could post some more minidumps, as I can`t really tell what the problem might be from just one. That`s why I suggested you post 5 or 6 minidumps.

Look HERE for help in understanding Windows stop messages.

Regards Howard :)
 
Hmm.. firefox? Weird. I updated my chipset drivers and things are seeming pretty ok for now. Here's some more minidumps (from today).
Edit: Sigh, got 0x0000008e again.. :mad:
 
3 of your minidumps crash with memory corruption, and a bugcheck of 50.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

One minidump cashes at win32k.sys, with a bugcheck of 7F.

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

The rest crash at win32k.sys, and a bug check of 8E.

It looks to me like you have a ram problem. Did you run the Memtest86+ programme for at least seven passes? Did you also try cleaning the contacts of your ram?

Please note. Some faulty ram can pass memtest.

Did you try a different dimm slot?

Is your ram compatible with your mobo?

Bad ram can be your physical ram/video ram/L2 cache ram of your cpu/or maybe a corrupt page file.

Make sure your system is not overclocked in any way.

Did you run a check disk from the command prompt?



Regards Howard :)
 
Hmm. Alright. Is there any way possible to combat this problem without physically testing and taking out ram? Thanks
 
Alright, well I tested each 256MB I had separately, and they passed- twice. Right now I'm experimenting with just this crucial 256MB DDR in here to see if it crashes anytime. I've moved them to different slots and blown dust from the slot and the RAM itself. Everything else in there was nice an clean. Also, why do you think firefox would cause the crash, howard? Why was I getting IRQL BSOD's pointing to device drivers? Thanks.

-SuperKoopa
 
Hi,

I agree Howard's finding and the culprit is faulty memory. Three of minidumps are crashed due to one bit memory corruption. Maybe the one bit corruption is caused by overheat. The running processes of two minidumps are firefox.exe. If I were Howard, I would make the suggestion. From the stack trace of Mini120105-08.dmp, probably it is faulty video ram. Run 3D Mark to stress test your VID.

158924e1 00000000 00000000 00000000 00000000 win32k!hbmSelectBitmap+0x28f (FPO: [Non-Fpo])
f6158bec 80565cec f6158ca8 f6158cac f6158c7c nt!KiCallUserMode+0x4 (FPO: [2,3,4])
f6158c48 bf813e47 00000002 f6158c8c 00000018 nt!KeUserModeCallback+0x87 (FPO: [Non-Fpo])
f6158ccc bf8035fe bbead530 0000000f 00000000 win32k!SfnDWORD+0xa8 (FPO: [Non-Fpo])
f6158d0c bf80f552 0050c903 f6158d64 0012fd70 win32k!xxxDispatchMessage+0x1dc (FPO: [Non-Fpo])
f6158d58 804de7ec 0012fdd0 0012fda8 7c90eb94 win32k!NtUserDispatchMessage+0x39 (FPO: [Non-Fpo])
f6158d58 7c90eb94 0012fdd0 0012fda8 7c90eb94 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f6158d64)


Mini120105-05.dmp BugCheck 10000050, {f8672000, 1, 804d8f45, 0}
DEFAULT_BUCKET_ID: CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Probably caused by : memory_corruption

Mini120105-06.dmp BugCheck 10000050, {ffffffe9, 1, bf80621c, 0}
DEFAULT_BUCKET_ID: CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Owning Process 82dbe650 Image: firefox.exe
Probably caused by : memory_corruption

Mini120105-07.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Owning Process 83049458 Image: csrss.exe
Probably caused by : win32k.sys ( win32k!InputApc+60 )

Mini120105-08.dmp BugCheck 1000008E, {c0000005, bf80a933, f615889f, 0}
Owning Process 82d73850 Image: firefox.exe
Probably caused by : win32k.sys ( win32k!hbmSelectBitmap+28f )

Mini120105-09.dmp BugCheck 1000000A, {a1552c0c, 1, 1, 804e9421}
DEFAULT_BUCKET_ID: CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Owning Process 8323e020 Image: explorer.exe
Probably caused by : memory_corruption
 
Interesting, because since I've removed my crucial RAM, I've had no problems. No BSOD's or anything yet. Which is great considering I'm using Azureus (Bittorrent client), mIRC, listening to music/videos, and using firefox. My comp crashed when I did lots of things at once. Maybe not anymore? :D
 
Status
Not open for further replies.
Back