BSOD System Error - Event Category (102)

Status
Not open for further replies.
Hi Everyone

Im getting the BSOD with the error "DRIVER_IRQL_NOT_LESS_OR_EQUAL"
I tried running memtest and got 0 errors. I read in a previous post that i still might be the ram tho.
Can someone please take a look at my minidumps ???

http://www.members.shaw.ca/asusbsod/Minidump.rar

thanks

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/20/2006
Time: 10:26:42 AM
User: N/A
Computer
Description:
Error code 1000008e, parameter1 c0000005, parameter2 f6896dc6, parameter3 a9dd9acc, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 36 38 39 36 64 63 36 f6896dc6
0040: 2c 20 61 39 64 64 39 61 , a9dd9a
0048: 63 63 2c 20 30 30 30 30 cc, 0000
0050: 30 30 30 30 0000
 

howard_hopkinso

Posts: 21,238   +17
Hello and welcome to Techspot.

2 minidumps crash with memory corruption and a bugcheck of 4E.

2 minidumps crash at ntoskrnl.exe. windows bootup kernel. They have bugchecks of 0A.

2 minidumps crash at w29n51.sys. Wireless network card. They have bugchecks of D1 and 8E.

1 minidump crashes at Ntfs.sys. Windows file system driver. It has a bugcheck of 50.

Update your wireless card drivers.

Also, go HERE and follow the instructions.

You can find the meaning of your bugcheck codes HERE.

Regards Howard :wave: :wave:
 
  • Thread Starter Thread Starter
  • #3
Hi Everyone

So i updated my wireless card drivers and even got 2 new sticks of ram
Still im getting BSOD :(

here some new mini dumps
http://www.members.shaw.ca/asusbsod/newMinidump.zip

Can someone please take a look


thanks


howard_hopkinso said:
Hello and welcome to Techspot.

2 minidumps crash with memory corruption and a bugcheck of 4E.

2 minidumps crash at ntoskrnl.exe. windows bootup kernel. They have bugchecks of 0A.

2 minidumps crash at w29n51.sys. Wireless network card. They have bugchecks of D1 and 8E.

1 minidump crashes at Ntfs.sys. Windows file system driver. It has a bugcheck of 50.

Update your wireless card drivers.

Also, go HERE and follow the instructions.

You can find the meaning of your bugcheck codes HERE.

Regards Howard :wave: :wave:
 
  • Thread Starter Thread Starter
  • #4
could it be the wireless card ? i read that people are having troubles with the intel 2200 b/g which im using now
 

howard_hopkinso

Posts: 21,238   +17
Your latest batch of minidumps crash with the following.

2 with win32k.sys and bugchecks of 8E and 0A. Multi-User Win32 Driver

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).

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Typically due to a bad driver, or faulty or incompatible hardware or software. 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.)

1 with ntoskrnl.exe and a bugcheck of 51. Windows bootup kernel.

0x00000051: REGISTRY_ERROR

This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system problems). This message might also appear due to a memory management error (more common in earlier versions of Windows NT).

1 aswMon2.SYS and a bugcheck of 50. Avast File System Filter Driver for Windows XP.

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).

If you`re sure that your ram is ok, maybe you should check to see if your psu is putting out enough power for your system. Also, check your mobo`s capacitors for bulging or leaking. See HERE for further info.

Regards Howard :)
 
  • Thread Starter Thread Starter
  • #6
howard_hopkinso said:
Your latest batch of minidumps crash with the following.

2 with win32k.sys and bugchecks of 8E and 0A. Multi-User Win32 Driver

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).

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Typically due to a bad driver, or faulty or incompatible hardware or software. 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.)

1 with ntoskrnl.exe and a bugcheck of 51. Windows bootup kernel.

0x00000051: REGISTRY_ERROR

This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system problems). This message might also appear due to a memory management error (more common in earlier versions of Windows NT).

1 aswMon2.SYS and a bugcheck of 50. Avast File System Filter Driver for Windows XP.

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).

If you`re sure that your ram is ok, maybe you should check to see if your psu is putting out enough power for your system. Also, check your mobo`s capacitors for bulging or leaking. See HERE for further info.

Regards Howard :)
Thanks Howard
Its a notebook so i cant really get to the mobo
 

howard_hopkinso

Posts: 21,238   +17
Ok.

Just make sure all your drivers are upto date. If that doesn`t help, I suspect some kind of hardware problem or overheating. In which case it might be a good idea to have your laptop looked at.

Regards Howard :)
 
Status
Not open for further replies.