Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

irql driver less than or equal error


  • Please log in to reply
3 replies to this topic

#1 zerotheliger

zerotheliger

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:04:15 AM

Posted 29 May 2011 - 04:14 PM

ive had this problem 4 days in a row now this is a custom build rig

GA-MA785GM-US2H gigabyte mobo
athlon II X4 640 cpu
ati 3650 sapphire graphics card
forgot my ram name but i already ran a few memory testers and its come back as ok same with hard drives





Loading Dump File [C:\Windows\Minidump\052711-23634-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/symbol
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e50
Debug session time: Fri May 27 23:56:37.041 2011 (UTC - 7:00)
System Uptime: 0 days 0:55:00.977
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffff8e0009e69bc, 2, 1, fffff80002fbb2c2}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Rt64win7.sys ( Rt64win7+298e )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffff8e0009e69bc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80002fbb2c2, address which referenced memory

Debugging Details:
------------------

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002e16000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ba73efa

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP:
nt+1a52c2
fffff800`02fbb2c2 ff411c inc dword ptr [rcx+1Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from fffff80002e85c69 to fffff80002e86700

STACK_TEXT:
fffff880`0a880388 fffff800`02e85c69 : 00000000`0000000a fffff8e0`009e69bc 00000000`00000002 00000000`00000001 : nt+0x70700
fffff880`0a880390 00000000`0000000a : fffff8e0`009e69bc 00000000`00000002 00000000`00000001 fffff800`02fbb2c2 : nt+0x6fc69
fffff880`0a880398 fffff8e0`009e69bc : 00000000`00000002 00000000`00000001 fffff800`02fbb2c2 fffff880`06f9a98e : 0xa
fffff880`0a8803a0 00000000`00000002 : 00000000`00000001 fffff800`02fbb2c2 fffff880`06f9a98e 00000000`00000000 : 0xfffff8e0`009e69bc
fffff880`0a8803a8 00000000`00000001 : fffff800`02fbb2c2 fffff880`06f9a98e 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a8803b0 fffff800`02fbb2c2 : fffff880`06f9a98e 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0a8803b8 fffff880`06f9a98e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1a52c2
fffff880`0a8803c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0x298e


STACK_COMMAND: kb

FOLLOWUP_IP:
Rt64win7+298e
fffff880`06f9a98e ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: Rt64win7+298e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME: Rt64win7.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffff8e0009e69bc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80002fbb2c2, address which referenced memory

Debugging Details:
------------------

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002e16000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ba73efa

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP:
nt+1a52c2
fffff800`02fbb2c2 ff411c inc dword ptr [rcx+1Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from fffff80002e85c69 to fffff80002e86700

STACK_TEXT:
fffff880`0a880388 fffff800`02e85c69 : 00000000`0000000a fffff8e0`009e69bc 00000000`00000002 00000000`00000001 : nt+0x70700
fffff880`0a880390 00000000`0000000a : fffff8e0`009e69bc 00000000`00000002 00000000`00000001 fffff800`02fbb2c2 : nt+0x6fc69
fffff880`0a880398 fffff8e0`009e69bc : 00000000`00000002 00000000`00000001 fffff800`02fbb2c2 fffff880`06f9a98e : 0xa
fffff880`0a8803a0 00000000`00000002 : 00000000`00000001 fffff800`02fbb2c2 fffff880`06f9a98e 00000000`00000000 : 0xfffff8e0`009e69bc
fffff880`0a8803a8 00000000`00000001 : fffff800`02fbb2c2 fffff880`06f9a98e 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a8803b0 fffff800`02fbb2c2 : fffff880`06f9a98e 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0a8803b8 fffff880`06f9a98e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1a52c2
fffff880`0a8803c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0x298e


STACK_COMMAND: kb

FOLLOWUP_IP:
Rt64win7+298e
fffff880`06f9a98e ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: Rt64win7+298e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME: Rt64win7.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:15 AM

Posted 29 May 2011 - 04:19 PM

Please delete everything in your above post after the first paragraph (just to make this thread more manageable). Then follow these steps:

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:02:15 AM

Posted 29 May 2011 - 05:47 PM

You can post a log required by Allan - we may get more info.
From what I can see, so far, it looks like Rt64win7.sys is your problem.
It's Realtek network adapter driver.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#4 Layback Bear

Layback Bear

  • Members
  • 1,880 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Ohio
  • Local time:04:15 AM

Posted 31 May 2011 - 10:41 AM

:thumbup2: thanks Allan.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users