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 9

post #81 of 98
Thread Starter 
In that case, I'd have to follow this methodology:

(Offline part)
* Install Windows 7 SP1 using MSDN ISO
* Install latest drivers
* Change ASACPI.sys to ASACPI.old (both of them, unless someone can help me find the latest drivers)
* Install MSE instead of ESET Smart Security 5 (Is it good and safe enough?)
* Install desired software (Office, Steam and whatnot, but avoid DAEMON and Apple's stuff)

(Online part)
* Install all updates

How does it look?

My only concern is that this wouldn't explain why the GPU was giving issues. How should we stress the hardware to find out if there are issues?

Also, can we safely discard an HDD issue?
Edited by Icekilla - 5/9/12 at 8:26am
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
post #82 of 98
Quote:
Originally Posted by Icekilla View Post

In that case, I'd have to follow this methodology:
(Offline part)
* Install Windows 7 SP1 using MSDN ISO
* Install latest drivers
* Change ASACPI.sys to ASACPI.old (both of them, unless someone can help me find the latest drivers)
* Install MSE instead of ESET Smart Security 5 (Is it good and safe enough?)
* Install desired software (Office, Steam and whatnot, but avoid DAEMON and Apple's stuff)
(Online part)
* Install all updates
How does it look?
My only concern is that this wouldn't explain why the GPU was giving issues. How should we stress the hardware to find out if there are issues?
Also, can we safely discard an HDD issue?

Looks great. Rather than renaming and such, give me the model of your motherboard and I'll try and get the latest utility that uses ASACPI for you.
post #83 of 98
Thread Starter 
ASUS P5N-E SLI. I'm using Windows 7 x64

And one more thing: My TV tuner doesn't seems to be working even after I installed the latest drivers (Version 5.3. It's an Encore ENLTV-FM). The only solution would be to install the 5.2B drivers, but that would trigger BSOD's, right?.
Edited by Icekilla - 5/9/12 at 9:30pm
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
post #84 of 98
There isn't an Asus utility tool for x64 on Asus' website, so oh well. If Windows did already somehow install a utility from Windows Update, just uninstall it. If it didn't make sure that no Asus utilities are checked in the optional updates page, even though you should never really be using optional updates as optional updates are all driver updates you're supposed to get off of a vendor website. As I said before, the Asus utilities are useless in my opinion as you can monitor voltages and temperatures with any other free hardware monitoring program. If you remove that, the only thing really left in the utility is the connection between the BIOS and the OS to make on-the-fly BIOS changes in the OS itself, which in my opinion is just asking for trouble, and everyone knows traditional method of overclocking (BIOS only, not OS using software) is the way to go.
Quote:
And one more thing: My TV tuner doesn't seems to be working even after I installed the latest drivers (Version 5.3. It's an Encore ENLTV-FM). The only solution would be to install the 5.2B drivers, but that would trigger BSOD's, right?.

Before installing the latest drivers for that, run a test on whatever was crashing you before, etc. Basically, right now we're just trying to reproduce the BSODs you were having before to see if it's hardware related. If you don't BSOD doing what you did before, it was likely just OS corruption / time for a reinstall.

Question, you kept mentioning your video card earlier, what's exactly the issue with it again? A few dumps I've analyzed earlier were the 116 TDR video failure bugchecks, which is like I said (memory, drivers corrupting memory, GPUs or PSU inability to handle load). Now that we've knocked both drivers and memory out of the way, all that's left is GPU(s). If you BSOD again, and it's a 116 code again, it's video card or PSU.
Edited by pjBSOD - 5/9/12 at 10:24pm
post #85 of 98
Thread Starter 
Windows update offers a driver for the ACPI, but I'll ignore it.

The issue with the GPU was that I lost all video and someohw that caused a BSOD when I ran OCCT, but it didn't happen with Furmark. BTW I installed the latest AMD drivers for my GPU, but for some reason Catalyst Control Center won't let me use the "overdrive" overclocking options :S

Also, what will we do about the TV tuner? frown.gif And how will we reproduce the BSOD's?
Edited by Icekilla - 5/10/12 at 11:04am
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
post #86 of 98
Quote:
Originally Posted by Icekilla View Post

Windows update offers a driver for the ACPI, but I'll ignore it.
The issue with the GPU was that I lost all video and someohw that caused a BSOD when I ran OCCT, but it didn't happen with Furmark. BTW I installed the latest AMD drivers for my GPU, but for some reason Catalyst Control Center won't let me use the "overdrive" overclocking options :S
Also, what will we do about the TV tuner? frown.gif And how will we reproduce the BSOD's?

Good, ignore it.

What happens when you try to use it? If you installed 12.4, that's a relatively known issue, so I'd recommend rolling back to a stable driver for the time being like 12.1.

As far as the TV Tuner goes, let's wait a week or so and see if you don't BSOD without it installed. The TV Tuner may be causing those 116 bugchecks.
post #87 of 98
Thread Starter 
The TV tuner is not even usable. As soon as I launch the TV app, it gives me an error saying the TV card was not found. The latest drivers are NOT working. mad.gif

And yes, it's CCC 12.4
Edited by Icekilla - 5/10/12 at 3:10pm
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
post #88 of 98
Quote:
Originally Posted by Icekilla View Post

The TV tuner is not even usable. As soon as I launch the TV app, it gives me an error saying the TV card was not found. The latest drivers are NOT working. mad.gif

This may be an issue with your TV Tuner card then my friend, which may have been causing those previous BSODs you were getting. It would make sense. When the display driver can recover from a crash, the screen will go black, but will be able to recover and Windows will say "the display driver successfully recovered". A 116 TDR video failure bugcheck means the display driver was unable to recover from a crash, which will then shoot a 116 TDR bugcheck, which may have been caused by your TV Tuner card.
Edited by pjBSOD - 5/10/12 at 3:00pm
post #89 of 98
Thread Starter 
And, we start with the catch up game, again...

http://dl.dropbox.com/u/21018119/051012-28392-01.dmp
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
fr0sty
(20 items)
 
SnowFlake
(5 items)
 
 
CPURAMHard DriveHard Drive
Intel Core i7 3520M  Corsair Vengeance DDR3 2x 8GB Samsung EVO SSD Hitachi Apple Hard Drive 5400RPM 
OS
macOS Sierra 
  hide details  
Reply
post #90 of 98
Thanks for the latest dump! When did this happen, what were you doing?

It's a C2 bugcheck pointing to dxgmms1.sys (DirectX kernel). 116 TDR bugchecks and dxgmms1.sys culprits are usually always related to a dying GPU. At this point my friend, it is most definitely hardware and I would contact the manufacturer of your GPU and let them know you're having nonstop 116 TDR video failure BSODs and dxgmms1.sys culprit BSODs. This could also be related to your PSU, so before sending it off for RMA, I would recommend (you don't have to, but I recommend it) swapping out a different PSU to see if it's not the PSU unable to handle load voltages, etc.

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\051012-28392-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.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e46670
Debug session time: Thu May 10 18:33:06.750 2012 (UTC - 4:00)
System Uptime: 0 days 1:13:42.544
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 7449c57b, fffffa8008ee2a70}

GetPointerFromAddress: unable to read from fffff80002eb0100
GetUlongFromAddress: unable to read from fffff80002e1ea38
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 000000007449c57b, Memory contents of the pool block
Arg4: fffffa8008ee2a70, Address of the block of pool being deallocated

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

GetUlongFromAddress: unable to read from fffff80002e1ea38

POOL_ADDRESS:  fffffa8008ee2a70 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dabbe9 to fffff80002c811c0

STACK_TEXT:  
fffff880`09eb3558 fffff800`02dabbe9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`7449c57b : nt!KeBugCheckEx
fffff880`09eb3560 fffff880`044535ec : 00000000`00000000 00000000`00000001 fffff8a0`14dd0670 00000000`00000001 : nt!ExDeferredFreePool+0x1201
fffff880`09eb3610 fffff880`04439ecc : 00000000`00000000 00000000`00000000 fffffa80`0a5985e0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x264
fffff880`09eb36e0 fffff880`05531ccc : 00000000`00000000 fffff8a0`1491c000 fffff8a0`1491c000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`09eb3710 fffff880`0553165f : fffff8a0`1491c000 fffff8a0`1491d300 fffff8a0`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`09eb3800 fffff880`055318e1 : fffff8a0`1491c000 fffff8a0`1491c000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`09eb3850 fffff880`0553579c : fffff8a0`12f05700 fffff880`09eb3ca0 fffffa80`08ca7000 fffff880`054fc3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`09eb38a0 fffff880`05537e57 : fffff8a0`1491c000 fffff880`09eb39b0 00000000`7efdb001 fffff880`054fd001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`09eb3930 fffff960`001af7ce : 00000000`0014fd01 fffffa80`0789cb50 00000000`00000020 00000000`74b66168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`09eb3bf0 fffff800`02c80453 : 00000000`06c6a964 fffff880`09eb3ca0 00000000`04f07130 00000000`7efdb000 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`09eb3c20 00000000`74b8141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014db38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74b8141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
fffff880`044535ec 488b4b20        mov     rcx,qword ptr [rbx+20h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xc2_7_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

BUCKET_ID:  X64_0xc2_7_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

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

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?