Graphics card failure?

Well, just shut my m17x R3 down after playing games no problem, needed a reboot, turned it back on and the screen resolution had changed and was huge. I reset it back to standard 1920 - 1080 and tried to resume playing. FIFA 12 cannot run. It starts up, goes to main menu, and on entering a game it just loads a black screen, and even the menus before this are a bit sketchy i.e. spelling mistakes, no backgrounds etc. ALAN WAKE cannot run. It loads up fine (this is Steam btw, FIFA is Origin) then when i resume game it jumps all over the place as if I am running the game on a ten year old machine! I haven't a clue whats happened but I am not getting any errors etc. Whats happened??

 

daniel, what grphics card is it?

First thing, i'd reinstall the driver

 

It's the 6990M. The catalyst control center driver? I've just completely shut down removed battery and left for 15 mins so gonna check it now. Can't believe this as am abroad as well till May.

Also something noteworthy, the laptop has BSOD'd for months and months but I am not getting them for this specific issue.

Oh and on another note hello again Slickdude80, good to see you're still here to help

 

Hey Daniel, how are you? I'm always here lol

ya reinstall the amd display driver. catalyst 12.2 works well for me

 

I'm fine, just fed up with the lappy atthe min!

After a I shut down and left it off for a while, I powered it back on and it workedfine. But today it's started again. Cannot play any games as stated above. I installed catalyst 12.2 and done everything i tried yesterday but nothing

Uninstyalled the graphics CCC and re installed both 12.2 which didnt work so i tried to reinstall from my driver disk and I get a message saying it installed with warnings:

Existing packagesAMD Catalyst Install Manager
Microsoft Visual C++ 2010 Redistributable

Packages for install
AMD APP SDK RuntimeFinal Status: Success
Version of Item: 2.4.595.10
Size: 90 Mbytes


Other detected devices

Error messages

Very frustrating now. I cannot re install CCC at all. It begins to install etc after I select custom or express install, then on detecting system setting (about 4 seconds into installation) it shoots right up to finishing point and says the install is complete, with warnings on the way as above. I'm not stuck with a 4.5kg paper weight. Cant even use VLC or media player as it runs terribly.

If i right click the desktop, there isnt even an option for graphics anymore. Is the card goosed??

EDIT updated my intel graphics from device manager and this has solved the watching movies etc problem. However the discreet graphics 6990m is not being foun in device manager, nor is it detected if I hit f2 and check on startup :S

 

Call Dell

I had same exact problems. New part is arriving and being installed today.
hopefully its only the 6990 and not my motherboard

 

Ah. I thought this might have to be the case. Unfortunately I'm out of the country till end of May and wont be in any one place for any length of time to get things sorted either. FORTUNATELY my warranty doesn't run out till September though. In the mean time....I have a gaming laptop that cant game. Poop.

 

I just called back Dell. I am also having my 6990m replaced on Wednesday.

 

Is any way to Contac dell and tell them your situation. Maybe they can send you A card or send it to your US. Address and have someone send it to you, worth A try.

 

Unfortunately not it's far too expensive to be sitting on the phone lines on hold. If I were back in the UK different story. ANd they don't answer e mails. Cheers anyways lads.

 

But you can still do it through the chat online.If you are for at least a week in the same place, is impossible for them not to come over and replace your required 'part'.

+ You have international warranty and you can call dell in the country you are residing now and they will send you a technician within 2-3 days to repair your system...

I travel all the time and wherever I am, if I face a problem with the PC, I call the 'local' dell service and they always have being very helpful.

Regards

 

Back on land again from work, hence the delay so sorry for delayed details etc. Right so in my time away. BSOD has increased 3 fold. It happens increasingly every day. Sometimes it's IRQL_NOT_LESS_THAN_OR_QUAL_TO BSOD, sometimes it's others. There are about 3 different other ones.

When the BSOD happens, and the computer loads back up, things change. I lose passwords sometimes, login details (which is bad if i am using steam at sea on DONT have net), AW Command Center stops workng and I cannot turn background lights off and have to reinstall AWCC every time to do so. Graphics card (Dedicated) will more often than not still be there however it is still vanishing on occasion.

Problem is really doing my head in now and I know when I get home in MAy, I have roughly 2 weeks before I work again to sort this prob out and more than likely if they send a technician out, the laptop will be in one of its hours where it functions almost correctly! Sods law.

This is definitely graphics card related though yes? Are AW likely to replace this or?

 

Zip and upload your dump files from C:\Windows\Minidump and I'll analyze them for you.

 

Uploaded here, hope it works and thanks in advance!

 

Wow...you've had quite a few BSOD's! It'll take me some time to go over them. I'll post back when I have more info for you.

Your dumps are kind of all over the place but the majority of them are 0x0A IRQL_NOT_LESS_OR_EQUAL stop errors with the odd TDR error or 0x01000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.

The drivers that popped up most as the cause was cmdguard.sys and cmdagent.exe:

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {22c7000, 2, 0, fffff800030922e0}

Unable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
Probably caused by : cmdguard.sys ( cmdguard+154fd )

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

6: 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: 00000000022c7000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800030922e0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032a90e0
 00000000022c7000

CURRENT_IRQL:  2

FAULTING_IP:
nt!MmProbeAndLockPages+130
fffff800`030922e0 410fb601        movzx   eax,byte ptr [r9]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  cmdagent.exe

TRAP_FRAME:  fffff880032731d0 -- (.trap 0xfffff880032731d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030922e0 rsp=fffff88003273360 rbp=0000000000000000
 r8=fffffa800a65e040  r9=00000000022c7000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmProbeAndLockPages+0x130:
fffff800`030922e0 410fb601        movzx   eax,byte ptr [r9] ds:3560:00000000`022c7000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003071aa9 to fffff80003072540

STACK_TEXT: 
fffff880`03273088 fffff800`03071aa9 : 00000000`0000000a 00000000`022c7000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03273090 fffff800`03070720 : fffffa80`0cc6c001 ffffffff`ffffffff 00000000`0000007f fffff880`0195d6a1 : nt!KiBugCheckDispatch+0x69
fffff880`032731d0 fffff800`030922e0 : 00000000`00000000 fffffa80`0d052378 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x260
fffff880`03273360 fffff800`0343c9f9 : fffffa80`0a65e010 fffff800`0330e301 00000000`00000001 00000000`022c7000 : nt!MmProbeAndLockPages+0x130
fffff880`03273470 fffff880`015a3e45 : 00000000`00000000 fffff880`00000001 fffffa80`0e254c60 00000000`00000000 : nt!MmProbeAndLockProcessPages+0x59
fffff880`032734e0 fffff880`01c154fd : fffff880`03273a80 fffffa80`0e234010 fffffa80`0f86a8f0 fffffa80`00000708 : fltmgr!FltSendMessage+0x295
fffff880`03273610 fffff880`03273a80 : fffffa80`0e234010 fffffa80`0f86a8f0 fffffa80`00000708 fffffa80`0e234020 : cmdguard+0x154fd
fffff880`03273618 fffffa80`0e234010 : fffffa80`0f86a8f0 fffffa80`00000708 fffffa80`0e234020 fffff880`032736b8 : 0xfffff880`03273a80
fffff880`03273620 fffffa80`0f86a8f0 : fffffa80`00000708 fffffa80`0e234020 fffff880`032736b8 fffff880`032736c0 : 0xfffffa80`0e234010
fffff880`03273628 fffffa80`00000708 : fffffa80`0e234020 fffff880`032736b8 fffff880`032736c0 00000000`00000001 : 0xfffffa80`0f86a8f0
fffff880`03273630 fffffa80`0e234020 : fffff880`032736b8 fffff880`032736c0 00000000`00000001 fffffa80`0f86a8e0 : 0xfffffa80`00000708
fffff880`03273638 fffff880`032736b8 : fffff880`032736c0 00000000`00000001 fffffa80`0f86a8e0 fffffa80`0e234010 : 0xfffffa80`0e234020
fffff880`03273640 fffff880`032736c0 : 00000000`00000001 fffffa80`0f86a8e0 fffffa80`0e234010 fffffa80`00a600a4 : 0xfffff880`032736b8
fffff880`03273648 00000000`00000001 : fffffa80`0f86a8e0 fffffa80`0e234010 fffffa80`00a600a4 fffff880`03273a80 : 0xfffff880`032736c0
fffff880`03273650 fffffa80`0f86a8e0 : fffffa80`0e234010 fffffa80`00a600a4 fffff880`03273a80 fffffa80`025000a4 : 0x1
fffff880`03273658 fffffa80`0e234010 : fffffa80`00a600a4 fffff880`03273a80 fffffa80`025000a4 fffffa80`0f86a920 : 0xfffffa80`0f86a8e0
fffff880`03273660 fffffa80`00a600a4 : fffff880`03273a80 fffffa80`025000a4 fffffa80`0f86a920 00000000`00000000 : 0xfffffa80`0e234010
fffff880`03273668 fffff880`03273a80 : fffffa80`025000a4 fffffa80`0f86a920 00000000`00000000 fffff880`06fe1d00 : 0xfffffa80`00a600a4
fffff880`03273670 fffffa80`025000a4 : fffffa80`0f86a920 00000000`00000000 fffff880`06fe1d00 fffff880`06fe1cf0 : 0xfffff880`03273a80
fffff880`03273678 fffffa80`0f86a920 : 00000000`00000000 fffff880`06fe1d00 fffff880`06fe1cf0 fffff880`06fdf7d2 : 0xfffffa80`025000a4
fffff880`03273680 00000000`00000000 : fffff880`06fe1d00 fffff880`06fe1cf0 fffff880`06fdf7d2 00000000`00000000 : 0xfffffa80`0f86a920


STACK_COMMAND:  kb

FOLLOWUP_IP:
cmdguard+154fd
fffff880`01c154fd ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  cmdguard+154fd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmdguard

IMAGE_NAME:  cmdguard.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f15d1ed

FAILURE_BUCKET_ID:  X64_0xA_cmdguard+154fd

BUCKET_ID:  X64_0xA_cmdguard+154fd

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

These are Comodo firewall guard driver system driver files. As such, the first step I would suggest in troubleshooting this would be uninstalling Comodo firewall, installing Microsoft Security Essentials and using Windows Firewall. This alone *should* cut down the number of BSOD's you get if not eliminate them completely.
__________________________________________________________

Other stop errors were caused by you GPU drivers:

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8011213010, fffff8800704f44c, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+744c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8011213010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800704f44c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+744c
fffff880`0704f44c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
fffff880`09bb4988 fffff880`070f5000 : 00000000`00000116 fffffa80`11213010 fffff880`0704f44c 00000000`00000000 : nt!KeBugCheckEx
fffff880`09bb4990 fffff880`070f4d0a : fffff880`0704f44c fffffa80`11213010 fffffa80`0f98bd50 fffffa80`0f94f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09bb49d0 fffff880`0740ff07 : fffffa80`11213010 00000000`00000000 fffffa80`0f98bd50 fffffa80`0f94f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`09bb4a00 fffff880`07439b75 : 00000000`ffffffff 00000000`000003a5 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`09bb4ae0 fffff880`074382bb : 00000000`00000102 00000000`00000002 00000000`000003a5 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`09bb4b10 fffff880`0740b2c6 : ffffffff`ff676980 fffffa80`0f94f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`09bb4bb0 fffff880`07437e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0e308c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`09bb4cc0 fffff800`03315726 : 00000000`01cc906e fffffa80`0f1fdb60 fffffa80`0a35c890 fffffa80`0f1fdb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`09bb4d00 fffff800`03054ac6 : fffff800`031efe80 fffffa80`0f1fdb60 fffff800`031fdc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`09bb4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+744c
fffff880`0704f44c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+744c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df18388

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Uninstall them, reboot, use CCleaner or Driversweeper in safe mode to clean remnants of the driver, reinstall with the latest drivers with a clean install. This being the second most common culprit in your BSOD's, eliminating this issue should cut back the number of BSOD's even further.
_________________________________________________

There was also a memory corruption error in there:

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800030bcd75, fffff88003569518, fffff88003568d80}

Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030bcd75, The address that the exception occurred at
Arg3: fffff88003569518, Exception Record Address
Arg4: fffff88003568d80, Context Record Address

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!MiGetNextNode+15
fffff800`030bcd75 48394808        cmp     qword ptr [rax+8],rcx

EXCEPTION_RECORD:  fffff88003569518 -- (.exr 0xfffff88003569518)
ExceptionAddress: fffff800030bcd75 (nt!MiGetNextNode+0x0000000000000015)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  fffff88003568d80 -- (.cxr 0xfffff88003568d80)
rax=0000000000000000 rbx=fffffa800a35b680 rcx=fffffa800a47e148
rdx=fffffa800e97f935 rsi=fffffa800f937d48 rdi=fffffa800a47e148
rip=fffff800030bcd75 rsp=fffff88003569758 rbp=fffffa800e979840
 r8=0000000000000006  r9=00000000000007ff r10=0000000000000801
r11=0000000000000743 r12=fffff8a001c99000 r13=0000000000000000
r14=fffff8a001c994b0 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010217
nt!MiGetNextNode+0x15:
fffff800`030bcd75 48394808        cmp     qword ptr [rax+8],rcx ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  cmdagent.exe

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c10e0
 0000000000000008

FOLLOWUP_IP:
nt!MiGetNextNode+15
fffff800`030bcd75 48394808        cmp     qword ptr [rax+8],rcx

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80003422c40 to fffff800030bcd75

STACK_TEXT: 
fffff880`03569758 fffff800`03422c40 : fffff880`03569780 fffffa80`0a35b680 fffff880`00000006 fffff8a0`01c92190 : nt!MiGetNextNode+0x15
fffff880`03569760 fffff800`03466a91 : fffffa80`0f937b30 00000000`00001404 fffffa80`107b8000 00000000`00000002 : nt!MmEnumerateAndReferenceImages+0x160
fffff880`035697e0 fffff800`03466d04 : fffffa80`0f937b30 fffff800`00000098 fffff800`03466b00 fffff880`03569900 : nt!EtwpEnumerateImages+0x51
fffff880`03569830 fffff800`0341e436 : fffffa80`0fa75b30 fffffa80`0f937b30 fffff800`03466b30 fffff880`03569900 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`035698b0 fffff800`03466e51 : fffff880`035699e8 fffffa80`0a30ac01 fffffa80`0a30a900 fffffa80`0a30a900 : nt!PsEnumProcesses+0x26
fffff880`035698e0 fffff800`03466ea7 : 00000000`00000000 00000000`00000002 fffff800`0322d470 fffffa80`0a30a9c0 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`03569930 fffff800`034d201c : 00000000`00401802 fffffa80`0a30ac68 fffffa80`0a30a9c0 fffff800`031ff350 : nt!EtwpKernelTraceRundown+0x47
fffff880`03569960 fffff800`034d250c : 00000000`00000000 fffff8a0`01c921c0 00000000`00000080 fffffa80`0a342890 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`03569a60 fffff800`033eecc2 : 00000000`00000000 fffffa80`0a30a9c0 fffff800`032370c8 fffff800`03203e80 : nt!EtwpUpdateTrace+0x36c
fffff880`03569ae0 fffff800`034f9246 : 00000000`00000008 00000000`00000001 fffff880`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5636e
fffff880`03569b50 fffff800`034f944a : fffffa80`00000010 ffffffff`80000a90 ffffffff`ffffffff fffffa80`0dd87af0 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`03569c30 fffff800`030976e1 : fffff800`0322e500 fffff800`034f9260 fffff800`0322e5f8 fffffa80`0a35b680 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`03569c70 fffff800`03329726 : ffffffff`fddfdffe fffffa80`0a35b680 00000000`00000080 fffffa80`0a342890 : nt!ExpWorkerThread+0x111
fffff880`03569d00 fffff800`03068ac6 : fffff880`03371180 fffffa80`0a35b680 fffff880`0337c0c0 7cf6afef`64ffdbf7 : nt!PspSystemThreadStartup+0x5a
fffff880`03569d40 00000000`00000000 : fffff880`0356a000 fffff880`03564000 fffff880`03568f00 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetNextNode+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

STACK_COMMAND:  .cxr 0xfffff88003568d80 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+15

BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+15

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

So it wouldn't hurt to run a few passes of memtest: RAM - Test with Memtest86+. There was only one instance of this so it most likely isn't a RAM issue but I would recommend a scan to eliminate it as a possibility. If there's no issues with your RAM then all is good.

There's other stuff from your dumps that I haven't gone over yet but these are the things that stick out as the most likely cause. I'll post again if I find anything else. In the meantime, please try each solution that I have suggested in order and see after each one if you still get BSOD's.

 

Aznpos531 - Thanks so much for doing this! I will have to do this over the weekend as at the moment as you are probably aware I'm working abroad so things take a little time.

Yes you're right, quite a few BSOD's and there were a lot more before my numerous clean installs prior to them. I appreciate this man, I know you'll want me to follow those steps ASAP and I will do as soon as possible! Well saying that I can do pretty much all except the clean install till the weekend. Here goes!

 

Excellent effort AZN! +rep when i can

 

Take your time! haha no rush. I'm still looking through a few of your dump files now. It seems that some of the dump files were somehow corrupted. I'm trying to see if I can recover them. When you do get the chance to try things out do keep us updated!

I've learned a lot from the forums and we've got a great community here. Just trying to give back by helping where I can

 

Right so my firsttime on land since the last message. As soon as I hit the hotel I ran a clean install. Comodo is gone. Everything wiped. Everything was alright until lastnight I used the HDMI cable to watch a movie on TV and i got the IRQL NOT EQUAL TO OR LESS BSOD error again...only the one though over the last few days since clean install. However my laptop does seem to be running differently i.e. slightly slower than before. Switching between internet windows takes a second (trivial i know but still noticable) longer than before as does opening files etc. Just doesnt feel the same. I cant run a RAM test as my flash is dead and difficult to get hold of in the areas I'm operating in.

Did you analyze the other dumps mate? Not sure what to make of this now.

And when I move windows around it creates a thousand windows in its shaddow until it catches up, def not the same laptop anymore grrrr

 

By clean install, do you mean a clean install of Windows or just the GPU drivers? I'll need to see the dump from your latest BSOD so see if anything new popped up so please upload that when you get a chance. For memtest you can also burn it to a cd and boot from that instead of a USB flash drive.

 

Daniel, do you have AlienAutopsy installed?

I was having an issue with TRD failures that would cause my MX17 R-3 to crash and then lockup eventually. It just started a few days ago. Just playing videos would crash my lappy! I was getting worried.

Anyway I found that some of my Alienware apps were GONE, including AlienAutopsy. I did a google search and found the download link on Dells sight. After downloading it and running it I found that it has some very cool features. Under System Tools > Utilities > Performance and Configuration > Critical Events (click on the red squares), you can actually look at error and crash dump information. Using this I found that my audio drivers were failing. Don't know why that impacted my video drivers, but I reinstalled them and now I think Im running rock solid. I ran system stress gaming test for over an hour and did NOT crash!!! Yeah ME!!

Use the link below to see more info!

http://forum.notebookreview.com/alienware/627152-alienware-alien-autopsy.html#post8102029

Oh and my system had been running a bit slower lately too. I wonder if this thing I also found on my system was somewhat to blame, no idea what it is but its gone now!

Google searching it yielded no results!

Startup Item - {2F3756DE-EC90-5CE4-FCCC-1A42A20B24E9}
Manufacture - Unknown
Command - "C:\Users\Rusty\AppData\Roaming\Qzisi\xafiy.exe
Location - HKLM\Software\Microsoft\Windows\CurrentVersion\Run

 

Aznpos531 - Yeah I meant I formatted my SSD (With OS on it) and reinstalled windows 7. Also, all drivers were reinstalled from the CD that came with the laptop. And in correct order of course, restarting the laptop after each prompt. Latest BSOD also attached.

Daspazz - I've downloaded that AlienAutopsy but it seems to just stop working and/or restart my laptop for some reason. Gonna give it another bash so cheers for pointing me in that direction, hopefully it may help somewhat.

Oh and before I forget I'm going to download the memtest to and burn to a disc today hopefully.

EDIT: AlienAutopsy definitely crashes my computer.

 

Get your drivers from the website. The ones from the DVD may not be up to date. I'm at work right now but I'll check out your latest dump when I get home.

 

I second that! All my drivers are from the support sight!

I would post my link but it has my service tag number in it. Sorry!!!

I think if you update then AA will stop crashing. Then one you an I downlaoed is newer than the old version on the DVD/CD. And it needs the newest drivers to work correctly.

 

Here's your latest dump:

Spoiler

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1b, 2, 0, fffff88004a9ac30}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : hardware ( atikmdag+27dc30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000001b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004a9ac30, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0
 000000000000001b

CURRENT_IRQL:  2

FAULTING_IP:
atikmdag+27dc30
fffff880`04a9ac30 02751a          add     dh,byte ptr [rbp+1Ah]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c390 -- (.trap 0xfffff80000b9c390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a09f590
rdx=fffffa800a09f580 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004a9ac30 rsp=fffff80000b9c528 rbp=0000000000000001
 r8=0000000010b6b783  r9=0000000001cd2194 r10=fffff80002c1c000
r11=fffff80000b9c570 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
atikmdag+0x27dc30:
fffff880`04a9ac30 02751a          add     dh,byte ptr [rbp+1Ah] ss:0018:00000000`0000001b=??
Resetting default scope

MISALIGNED_IP:
atikmdag+27dc30
fffff880`04a9ac30 02751a          add     dh,byte ptr [rbp+1Ah]

LAST_CONTROL_TRANSFER:  from fffff80002c8bb29 to fffff80002c8c5c0

STACK_TEXT: 
fffff800`00b9c248 fffff800`02c8bb29 : 00000000`0000000a 00000000`0000001b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c250 fffff800`02c8a7a0 : 00000000`0000000a fffff800`00b9c5c0 fffff800`02e06e80 fffff800`02c98c60 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c390 fffff880`04a9ac30 : fffff800`02c9812e fffff800`00b9c5c0 00000000`00018510 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c528 fffff800`02c9812e : fffff800`00b9c5c0 00000000`00018510 00000000`00000000 00000000`00000055 : atikmdag+0x27dc30
fffff800`00b9c530 fffff800`02c97c76 : fffffa80`0e197c68 fffffa80`0e197c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02c9834e : 00000003`ee55fdcc fffff800`00b9cc18 00000000`0001a6c2 fffff800`02e0aac8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02c97b57 : 00000000`d79df0c2 00000000`0001a6c2 00000000`d79df077 00000000`000000c2 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02c94d8a : fffff800`02e06e80 fffff800`02e14c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
atikmdag+27dc30
fffff880`04a9ac30 02751a          add     dh,byte ptr [rbp+1Ah]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+27dc30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys

BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys

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

It points to your GPU drivers and although there was hardware involvement I believe installing the latest GPU drivers with a clean install will solve the issue. I'm not 100% familiar with ATI drivers but generally speaking, to perform a clean installation of the GPU drivers go to Control Panel>Programs and Features. Uninstall all the GPU drivers. Restart into Safe Mode (after POST and BIOS screen, before the Windows loading screen, repeatedly tap F8 and choose Safe Mode (first option)). In Safe Mode, run CCleaner or DriverSweeper and remove the remaining registry entries for the GPU drivers. Restart normally and reinstall with the latest drivers. I'm not sure if the ATI installation has it but with nVidia drivers there's an option to "perform a clean install" when you choose a custom install. If there is such an option, make sure it's selected.

 

also make sure windows sp1 is installed. I always had GPU BSOD's with my 460m for some reason till I got Sp1 installed and it magically went away. Not sure why it always did that though.

 

^ good point. Make sure your Windows Updates as well as all your drivers are up to date.