Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Sudden BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL ?


  • Please log in to reply

#1
xDokii

xDokii

    Member

  • Member
  • PipPip
  • 64 posts
Hello Geeks To Go,

Today I was just on my computer doing my usual thing when I suddenly got the blue screen of death saying:

A problem has been detected and windows has shut down to prevent damage to your computer.

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any hardware or software is properly installed. if this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select safe Mode.

Technical information:

*** STOP: 0x000000D1 (0x00000014, 0x00000002, 0x00000000, 0xF50313C0)

*** rdbss.sys - Address F50313C0 base at F5031000, DateStamp 48025ee6

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance


Upon restarting the computer it told me that the system had just recovered from a serious error and i clicked to see the error report which read:

BCCode: 100000d1 BCP1: 00000014 BCP2: 00000002 BCP3: 00000000
BCP4: F50313C0 OSVer: 5_1_26000 SP: 3_0 Product: 768_1


I am not sure why it suddenly happened because it was the first time it happened. Not long ago I came here asking for help with malware but it has been fixed but maybe it has come back up?? :S I am not experienced with computers and IT so please excuse me if I ask what things are!
  • 0

Advertisements


#2
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
Download WhoCrashed, using the link in my list below. Run the program and attach the log to your next post.
  • 0

#3
xDokii

xDokii

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
Thanks for the reply :D

Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sat 02/10/2010 19:41:23 your computer crashed
This was likely caused by the following module: rdbss.sys
Bugcheck code: 0x100000D1 (0x14, 0x2, 0x0, 0xF50313C0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini100210-01.dmp
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 20/08/2010 02:10:15 your computer crashed
This was likely caused by the following module: fltmgr.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x806F0753, 0xF8AC9C28, 0xF8AC9924)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini082010-01.dmp
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 07/08/2010 22:28:47 your computer crashed
This was likely caused by the following module: catchme.sys
Bugcheck code: 0x10000050 (0xFF920000, 0x1, 0xF3DAB08D, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini080710-02.dmp



On Sat 07/08/2010 12:49:58 your computer crashed
This was likely caused by the following module: catchme.sys
Bugcheck code: 0x10000050 (0xFD03A000, 0x1, 0xF4D6B08D, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini080710-01.dmp



On Sat 06/03/2010 02:12:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D4 (0xF64BE0B8, 0x2, 0x1, 0x804DBC9A)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini030610-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 05/03/2010 00:32:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D4 (0xF61B90B8, 0x2, 0x1, 0x804DBC9A)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini030510-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 04/03/2010 21:51:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D4 (0xF64C50B8, 0x2, 0x1, 0x804DBC9A)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini030410-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 02/03/2010 01:00:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D4 (0xF67CC0B8, 0x2, 0x1, 0x804DBC9A)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini030210-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 13:42:43 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x81654680, 0x816547F4, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-07.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 13:38:31 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x821FC948, 0x821FCABC, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-06.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 11:17:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE27C24D0, 0xC0000005, 0x7C9101B3, 0x115ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
Dump file: C:\WINDOWS\Minidump\Mini022710-05.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 11:12:13 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x817E9930, 0x817E9AA4, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-04.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 03:43:46 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x816D0DA0, 0x816D0F14, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-03.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 03:38:47 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8203A958, 0x8203AACC, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-02.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 03:31:13 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x82108DA0, 0x82108F14, 0x805FA210)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini022710-01.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 22/01/2010 22:03:31 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D4 (0xF66240B8, 0x2, 0x1, 0x804DBC9A)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini012210-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Edited by xDokii, 03 October 2010 - 06:04 AM.

  • 0

#4
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
There is a variety of system file failures which indicate to a RAM problem. There are two indication to catchme.sys which could be malware.

To test the RAM: download memtest from my list below. Create a bootable CD, boot with the new CD and run at least one full pass. If there are any errors (red lines) your RAM is faulty.

Please report after the RAM test and we'll continue from this [point.
  • 0

#5
xDokii

xDokii

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
Sorry, but could you explain what a bootable CD is,how to create one and how to boot into it??
  • 0

#6
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
A bootable CD is a CD which allows you to boot the computer when it is placed in the CD drive. The CD drive must be set as first-priority-boot-dvice. You set the boot priority in the BIOS. There is a good chance that your computer is already set correctly, so don't do anything as far as boot priority is concerned.

To make a bootable CD of memtest click the link in my list of programs below. In the page that opens scroll down to middle of the page, just below the three blue demo screens. Among the download options click the first one and save the file to your desktop.

Now you have to burn the file to a CD. Being an ISO file you have to burn it somewhat differently. To do that very simply download BurnCDCC from my links and install the program. It's a very simple program, dedicated to burning ISO files.

Insert the new CD to the drive and boot the computer. Memtest will load and immediately start scanning the RAM.
  • 0

#7
xDokii

xDokii

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
May I ask what type of CD do I burn it to?? A CD that you burn music to?? or DVDs??
  • 0

#8
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
The simplest, 700MB CD.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP