Windows 7: Irql bsod

Sabrac · 09 Aug 2011

Hi everyone,

I've been getting an IRQL driver BSOD for a few days now. I'm not too sure what driver is causing it because my WhoCrashed just says "Unknown".

My graphics, chipset, and BIOS are up to date.

Unfortunately, I can't upload the memory dump because its 400MB and 104MB in a .zip folder, but I can copy and paste what my WhoCrashed said.

Code:

Crash dump file:        C:\Windows\memory.dmp
Date/time:              8/9/2011 2:12:42 PM
Uptime:                 00:37:16
Machine:                
Bug check name:         IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xA
Bug check parm 1:       0xFFFFF6FC401CDE18
Bug check parm 2:       0x2
Bug check parm 3:       0x0
Bug check parm 4:       0xFFFFF80002CAC3EA
Probably caused by:     Unknown
Driver description:     
Driver product:         
Driver company:         
OS build:               
Architecture:           x64 (64 bit)
CPU count:              4
Page size:              4096

Bug check description:
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Comments:
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .

Any help is very appreciated.

Sabrac · 09 Aug 2011

Since posting this thread I've gotten 1 BSOD and my computer has froze 4 times during startup while trying to upload the MiniDump that I now have.

FredeGail · 09 Aug 2011

Hello Sabrac
& Welcome to SevenForums!

BSOD Summary

Code:

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


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.872\080911-22916-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e96650
Debug session time: Tue Aug  9 20:36:00.914 2011 (UTC + 2:00)
System Uptime: 0 days 0:21:57.818
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff9600064eb1e, 8, fffff9600064eb1e, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4621f )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff9600064eb1e, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff9600064eb1e, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f00100
 fffff9600064eb1e 

FAULTING_IP: 
+60c62faf00ebdb44
fffff960`0064eb1e ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009638a60 -- (.trap 0xfffff88009638a60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffc0000005 rbx=0000000000000000 rcx=fffff88009637860
rdx=fffff88009639000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600064eb1e rsp=fffff88009638bf0 rbp=fffff88009638ca0
 r8=fffff88009639000  r9=ffffffffc0000005 r10=fffff88009638c90
r11=fffff88009636fd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff960`0064eb1e ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7ca0c to fffff80002cd0d00

STACK_TEXT:  
fffff880`096388f8 fffff800`02c7ca0c : 00000000`00000050 fffff960`0064eb1e 00000000`00000008 fffff880`09638a60 : nt!KeBugCheckEx
fffff880`09638900 fffff800`02ccee2e : 00000000`00000008 fffff960`0064eb1e 00000000`00000000 fffffa80`07998500 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`09638a60 fffff960`0064eb1e : ffffffff`c901171e fffffa80`07998500 00000000`02997ac8 00000000`00000020 : nt!KiPageFault+0x16e
fffff880`09638bf0 ffffffff`c901171e : fffffa80`07998500 00000000`02997ac8 00000000`00000020 00000000`00000020 : 0xfffff960`0064eb1e
fffff880`09638bf8 fffffa80`07998500 : 00000000`02997ac8 00000000`00000020 00000000`00000020 fffff800`02ccff93 : 0xffffffff`c901171e
fffff880`09638c00 00000000`02997ac8 : 00000000`00000020 00000000`00000020 fffff800`02ccff93 fffffa80`07998500 : 0xfffffa80`07998500
fffff880`09638c08 00000000`00000020 : 00000000`00000020 fffff800`02ccff93 fffffa80`07998500 fffff880`00000000 : 0x2997ac8
fffff880`09638c10 00000000`00000020 : fffff800`02ccff93 fffffa80`07998500 fffff880`00000000 00000000`00000000 : 0x20
fffff880`09638c18 fffff800`02ccff93 : fffffa80`07998500 fffff880`00000000 00000000`00000000 00000000`00000000 : 0x20
fffff880`09638c20 000007fe`fe8613ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`029979f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe8613ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4621f
fffff800`02c7ca0c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4621f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4621f

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4621f

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

To be honest, I think it's your sidebar.exe is the cause here. Could you make a Ctrl + Alt + Delete, and delete the sidebar.exe process?

Best Regards,
FredeGail

Sabrac · 09 Aug 2011

So would uninstalling all my Windows gadgets be able to solve my problem? I currently don't use them that much. They're my CPU usage meter, GPU usage meter, World of Warcraft server checker, and my AVG anti-virus tool.

FredeGail · 09 Aug 2011

Quote: Originally Posted by Sabrac

So would uninstalling all my Windows gadgets be able to solve my problem? I currently don't use them that much. They're my CPU usage meter, GPU usage meter, World of Warcraft server checker, and my AVG anti-virus tool.

Interesting. These gadgets you got is all 3rd party applications. I always love to say this.. Get rid of it!

Microsoft - Gadget, How to Uninstall & More

Best Regards,
FredeGail

Sabrac · 09 Aug 2011

Thanks, I would have never known it was something so simple.

Sadly with my luck, as soon as something is fixed another thing goes wrong.

My computer freezes on the "Starting Windows" screen sometimes and in the morning I have to turn my computer on and off about 20 times(sometimes even taking parts out and putting them back in) to get it to just show video.

I'm curious if my graphics card is breaking on me.
Is there anyway I can check my graphics card to see if there's anything wrong with it?

FredeGail · 09 Aug 2011

Quote: Originally Posted by Sabrac

Thanks, I would have never known it was something so simple.

Sadly with my luck, as soon as something is fixed another thing goes wrong.

My computer freezes on the "Starting Windows" screen sometimes and in the morning I have to turn my computer on and off about 20 times(sometimes even taking parts out and putting them back in) to get it to just show video.

I'm curious if my graphics card is breaking on me.
Is there anyway I can check my graphics card to see if there's anything wrong with it?

You could do a Furmark test. But let's leave your Graphic Card, and to a memory test by using MemTest

That'll be our first step.
FredeGail

Sabrac · 09 Aug 2011

I've done that test may times and gotten errors.
I've switched out RAM sticks until I didn't see errors anymore.

Right now I have 2 stick of the original RAM I had from this computer's base factory setup and 1 stick that I took from an old computer.

I'll do an overnight MemTest tonight and post if I get errors.

FredeGail · 09 Aug 2011

Quote: Originally Posted by Sabrac

I've done that test may times and gotten errors.
I've switched out RAM sticks until I didn't see errors anymore.

Right now I have 2 stick of the original RAM I had from this computer's base factory setup and 1 stick that I took from an old computer.

I'll do an overnight MemTest tonight and post if I get errors.

Nice. Post back your results.

Best Regards,
FredeGail

Sabrac · 10 Aug 2011

MemTest got 6 passes through. No errors at all.

Windows 7: Irql bsod

Irql bsod problems?