Overclock.net banner

Somebody read this MiniDump please?

698 Views 14 Replies 6 Participants Last post by  Kornowski
I'd really appreciate it if somebody could read this minidump for me.

Thank you!
1 - 15 of 15 Posts
Why? What do you want to know?
Well, I've been getting regular BSOD's and I was hoping somebody would be able to delve into it and find something a little more specific to help me trouble shoot the problem.
Let me see if I can open/read it..
Looks like a kernel memory panic on a driver and failed with IRQL_NOT_LESS_OR_EQUAL

Code:
Code:
STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPfPutPagesInTransition+6d5
81cc18d7 895cbe1c        mov     dword ptr [esi+edi*4+1Ch],ebx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiPfPutPagesInTransition+6d5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b7fa

IMAGE_NAME:  [B]memory_corruption[/B]

FAILURE_BUCKET_ID:  0xA_nt!MiPfPutPagesInTransition+6d5

BUCKET_ID:  0xA_nt!MiPfPutPagesInTransition+6d5

Followup: MachineOwner
Updated any system level drivers recently? GPU or other low level drivers that might be causing memory corruption? I would revert back or try a re-install but most likely it is GPU related.

Any overclocks? Stable?

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c71ffc30, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81cc18d7, address which referenced memory

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d6b868
Unable to read MiSystemVaType memory at 81d4b420
 c71ffc30

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiPfPutPagesInTransition+6d5
81cc18d7 895cbe1c        mov     dword ptr [esi+edi*4+1Ch],ebx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe
See less See more
  • Rep+
Reactions: 1
Quote:


Originally Posted by Ictinike
View Post

Updated any system level drivers recently? GPU or other low level drivers that might be causing memory corruption? I would revert back or try a re-install but most likely it is GPU related.

Thanks for looking into that for me, I really appreciate it!

Nope, not recently. It's been a while since I've updated my drivers.
I've had an OC, on my CPU, but it's been stable for a while. I've also had problems before, with a different OC. I do have my system at stock now, just to see.

So, it's Memory related, like RAM?
Does the error 'IRQL_NOT_LESS_OR_EQUAL' relate to RAM, too?

Thanks again, buddy! +Rep!
See less See more
Quote:


Originally Posted by Kornowski
View Post

Thanks for looking into that for me, I really appreciate it!

Nope, not recently. It's been a while since I've updated my drivers.
I've had an OC, on my CPU, but it's been stable for a while. I've also had problems before, with a different OC. I do have my system at stock now, just to see.

So, it's Memory related, like RAM?
Does the error 'IRQL_NOT_LESS_OR_EQUAL' relate to RAM, too?

Thanks again, buddy! +Rep!

IRQL_NOT_LESS_OR_EQUAL errors are usually memory related. They indicate that something is wrong with the data that is swirling around on the motherboard. It may be a bad memory stick, something a bad memory stick caused (data corruption), data corruption (bad driver?)from an overclocked memory failure, etc..

Reading memory dump files is like doing an automobile accident investigation by looking at the skid marks. A video of the accident would make it much easier to determine what actually happened. Event Viewer is the equivalent of a video of what is going on in your computer, both the good and the bad.
Open up Event Viewer and look for problems. That will at least stear you in the right direction. You can also use Memtest-86 to check for faulty memory sticks. Run it on one stick at a time.
See less See more
  • Rep+
Reactions: 1
It is video card related. Update your drivers or uninstall NTune
  • Rep+
Reactions: 1
I second the memtest86 idea for looking for RAM related errors.
  • Rep+
Reactions: 1
Yeah, I just ran !analyze -v;r;kv;lmtn in windbg to check your dump, it is your video card drivers. Seems there is a problem with your drivers and ATI Tool not playing right together.
2
Quote:

Originally Posted by billbartuska View Post
IRQL_NOT_LESS_OR_EQUAL errors are usually memory related. They indicate that something is wrong with the data that is swirling around on the motherboard. It may be a bad memory stick, something a bad memory stick caused (data corruption), data corruption (bad driver?)from an overclocked memory failure, etc..

Reading memory dump files is like doing an automobile accident investigation by looking at the skid marks. A video of the accident would make it much easier to determine what actually happened. Event Viewer is the equivalent of a video of what is going on in your computer, both the good and the bad.
Open up Event Viewer and look for problems. That will at least stear you in the right direction. You can also use Memtest-86 to check for faulty memory sticks. Run it on one stick at a time.
Ah right, Ok. That's actually what I wanted to hear, sort of. I was hoping if anything, it was the RAM, as it's the cheapest thing to replace. I'll run Memtest on each stick individually though! Thanks!

Quote:

Originally Posted by h00chi3 View Post
Yeah, I just ran !analyze -v;r;kv;lmtn in windbg to check your dump, it is your video card drivers. Seems there is a problem with your drivers and ATI Tool not playing right together.
I did have ATI install, but I got rid of it about 2 weeks ago, I've deleted all traces of it on my computer. Yet, I was still getting the BSOD's when I didn't have it installed. How could it be causing it?

Thanks guys, +Rep!
See less See more
Go into device manager and make sure the ATI device driver is also uninstalled.
2
Quote:

Originally Posted by h00chi3 View Post
Go into device manager and make sure the ATI device driver is also uninstalled.
What would it be under?
I can't see anything about ATI under my 'System Devices'.

Quote:

Originally Posted by Maddog7771 View Post
i had the same error before and was caused my memory also memtest can be found on most linux disk.

http://www.memtest.org/
So, bad RAM was causing it for you?
I'll run Memtest during the week, thanks man!
See less See more
So, does the mini dump suggest that it's the RAM?
1 - 15 of 15 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top