Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?
New Posts  All Forums:Forum Nav:

Can anyone help me read these minidump files? - Page 4

post #31 of 98
Thread Starter 
I just had another BSOD :/

Here's the link

http://dl.dropbox.com/u/21018119/050712-24585-01.dmp

Sorry if I can't fix the issues. I'm WAY too busy with finals frown.gif
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
post #32 of 98
1e bugcheck mentioning the same things I did earlier. Until you have time to enable Driver Verifier and attach a verifier enabled dump, just hold off on the dumps as they're going to more than likely at this point be the same thing over & over again, or wrong anyway.
post #33 of 98
Thread Starter 
Another BSOD and another dump.

http://dl.dropbox.com/u/21018119/050712-19515-01.dmp

I can't wait to get new pieces or do a clean install! frown.gif BTW I JUST activated Driver verifier.
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
post #34 of 98
Latest BSOD attached doesn't look like it's verifier enabled, so I assume you enabled it after that BSOD.

That dump attached is a 3B pointing to memory corruption, so it sounds like your memory is on its way out, or a 3rd party driver is really corrupting memory here. If Driver Verifier shows nothing, the next thing I'd like you to do is Memtest. We'll worry about that when we need to.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050712-19515-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030ab650
Debug session time: Mon May  7 16:42:15.654 2012 (UTC - 4:00)
System Uptime: 0 days 1:01:22.246
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f8e37f, fffff88007871c90, 0}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f8e37f, Address of the instruction which caused the bugcheck
Arg3: fffff88007871c90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiIdentifyPfn+26f
fffff800`02f8e37f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh

CONTEXT:  fffff88007871c90 -- (.cxr 0xfffff88007871c90)
rax=0000000000000001 rbx=020000000017ba6a rcx=0200000000000020
rdx=00000000000d6151 rsi=0000000000000000 rdi=fffffa8007447720
rip=fffff80002f8e37f rsp=fffff88007872670 rbp=fffffa8009309b30
 r8=00000000000d5d92  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=fffff80003058e80 r13=0000000000000000
r14=fda30e931c218e6d r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiIdentifyPfn+0x26f:
fffff800`02f8e37f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:002b:fda30e93`1c218eb5=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f8e37f

STACK_TEXT:  
fffff880`07872670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiIdentifyPfn+0x26f


FOLLOWUP_IP: 
nt!MiIdentifyPfn+26f
fffff800`02f8e37f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiIdentifyPfn+26f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

STACK_COMMAND:  .cxr 0xfffff88007871c90 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+26f

BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+26f

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

post #35 of 98
Thread Starter 
What? o_O I ran memtest last December because of a similar issue and I had no problems. Also, this RAM was bought that same month... frown.gif
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
post #36 of 98
Quote:
Originally Posted by Icekilla View Post

What? o_O I ran memtest last December because of a similar issue and I had no problems. Also, this RAM was bought that same month... frown.gif

Such is the way of hardware, my Corsair Vengeance just recently kicked the bucket, wasn't even a year old, had to send it for RMA. Regardless, there's no for sure it's memory yet, it could be a 3rd party driver faulting and corrupting memory thus causing a memory corruption probable cause. We'll find out of that's the case from Driver Verifier.

If you don't BSOD within ~48 hours at most with Verifier enabled, it's likely memory and we'll run Memtest.
post #37 of 98
Thread Starter 
I hope it's not memory frown.gif

Either way, seems like evrything's pointing out to a faulty driver, right?
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
post #38 of 98
Quote:
Originally Posted by Icekilla View Post

I hope it's not memory frown.gif
Either way, seems like evrything's pointing out to a faulty driver, right?

So far, that would be the most accurate and best case scenario. If Driver Verifier doesn't come back with a culprit driver, with the memory corruption culprits and other bugchecks / culprits I've seen so far, memory would be the next most accurate. We'll see soon.
post #39 of 98
Thread Starter 
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
Vanessa
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
  hide details  
Reply
post #40 of 98
Verifier enabled dumps are showing no culprit drivers, just the usual Microsoft files and drivers. Memtest time, my friend. Settle for no less than 7-8 passes. This will take many hours, so run it while you're out at work or before bed and check in the morning.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050712-18392-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e650
Debug session time: Mon May  7 18:59:48.728 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:50.523
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e3, fffffa8008c10531, 6d0ef50, 0}

Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffffa8008c10531, Address inside the driver making the incorrect API call.
Arg3: 0000000006d0ef50, User-mode address used as API parameter.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_e3

FAULTING_IP: 
+6637643263363463
fffffa80`08c10531 85c0            test    eax,eax

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff800`0335f3dc cc              int     3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000335f3dc to fffff80002ed6c80

STACK_TEXT:  
fffff880`08501458 fffff800`0335f3dc : 00000000`000000c4 00000000`000000e3 fffffa80`08c10531 00000000`06d0ef50 : nt!KeBugCheckEx
fffff880`08501460 fffff800`0335fec5 : fffffa80`071e7980 fffff800`0336e09a fffff880`084fc000 fffff880`08502000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`085014a0 fffff800`0336139e : 00000000`00000000 00000000`00000028 fffffa80`08c103b9 fffff800`0000051e : nt!ViZwCheckAddress+0x35
fffff880`085014e0 fffff800`03361426 : fffff880`08501628 fffff880`08501628 00000000`00000000 00000000`00000000 : nt!ViZwCheckUnicodeString+0x2e
fffff880`08501520 fffff800`03364d99 : fffffa80`08c10531 00000000`00000000 00000000`70616745 00000000`00000000 : nt!ViZwCheckObjectAttributes+0x26
fffff880`08501550 fffffa80`08c10531 : 00000000`06d0ef50 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc : nt!VfZwOpenFile+0x49
fffff880`08501590 00000000`06d0ef50 : 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 : 0xfffffa80`08c10531
fffff880`08501598 00000000`00000000 : 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 00000000`00000021 : 0x6d0ef50


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff80003108000
THREAD fffffa800a9cf060  Cid 06f4.0838  Teb: 000000007ef98000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80003047ba4
Owning Process            fffffa800a8feb30       Image:         ekrn.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      7081         
Context Switch Count      3167             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000000006e65cf50
Stack Init fffff88008501db0 Current fffff88008501790
Base fffff88008502000 Limit fffff880084fc000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`08501458 fffff800`0335f3dc : 00000000`000000c4 00000000`000000e3 fffffa80`08c10531 00000000`06d0ef50 : nt!KeBugCheckEx
fffff880`08501460 fffff800`0335fec5 : fffffa80`071e7980 fffff800`0336e09a fffff880`084fc000 fffff880`08502000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`085014a0 fffff800`0336139e : 00000000`00000000 00000000`00000028 fffffa80`08c103b9 fffff800`0000051e : nt!ViZwCheckAddress+0x35
fffff880`085014e0 fffff800`03361426 : fffff880`08501628 fffff880`08501628 00000000`00000000 00000000`00000000 : nt!ViZwCheckUnicodeString+0x2e
fffff880`08501520 fffff800`03364d99 : fffffa80`08c10531 00000000`00000000 00000000`70616745 00000000`00000000 : nt!ViZwCheckObjectAttributes+0x26
fffff880`08501550 fffffa80`08c10531 : 00000000`06d0ef50 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc : nt!VfZwOpenFile+0x49
fffff880`08501590 00000000`06d0ef50 : 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 : 0xfffffa80`08c10531
fffff880`08501598 00000000`00000000 : 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 00000000`00000021 : 0x6d0ef50

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?