BSOD randomly and happening more & more.

Britton30 said:

I've asked for help here. Can you manage full pics of screens when you take them?

I'll try, but my camera isn't that good lol. Comes out blurry etc.
So I tested black&white 2, a cd game, ran for a bitty. Computer completely crashed, all lines messed up.
High possibility of hardware issue?. Oh and is anything coming back from the dmps?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff3000b063038, 2, 0, fffff800022d3d00}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

Driver Reference Table - fileinfo.sys

Is Windows completely updated?

Okay so I managed to download and install 9dragons, a different game. Played it for a while ~ desktop actually stayed on for quite a bit, exited it, thought nothing was happening, randomly browsing internet explorer I got this;

STOP code: 0x0000050 appeared but restarted so quickly I couldn't get to see anything else and no save was made.

Also this new one appeared shortly after it - after restarting and booting up windows;

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000058, 0x000000000000000a, 0x0000000000000000, 0xfffff88004b77e83). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 020914-25896-01.



Oh and can I just say, I bought the desktop on the 09/1/14, got it by the 10/1/14, same day experiencing problems 7hours+ later, contacted the people I got it from, they came and picked it up eventually, got it back on the 03/2/14. Apparently it was my dell oem disc that caused all the problems. So they installed there version of windows using my Microsoft key and charged me £35. Since it was a 'user error'. Same day, 7hours+ later exact same problems started happening.

Is it not just safe to say it is an hardware issue?. The only programs I installed when I originally got it was 'league of legends, firefox'.

They didn't give me there windows disc despite charging me so I had to revert and reinstall my version of windows onto the system because of the previous 0x7b error which wouldn't allow me to boot, which I think is completely fine & its all directed towards hardware?.

BSoDs still happening; latest minidmp -

Okay so I went into device manager after remembering I disabled realtek hd audio because I thought it might be conflicting after doing research, anytime I tried to enable it, I would get the 0x0A error. So I've uninstalled it completely. Will tell you if I get anymore bsods like the very first ones -0x1A.

cfos products inculding cFosSpeed Internet Accelerator is a very regular and frequent BSOD causer. You need to uninstall it.

Also, using a BETA display driver is a bad idea, specially for an unstable computer. Uninstall your installed BETA version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• Drivers - Clean Left over Files after Uninstalling

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

Lately we have seen a lot of issues with the latest 13.12 WHQL AMD Catalyst.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Also make it sure that you are not overclocking anything at all.

Let us know the results.
________________________________________________________________________________________

Code:

fffff880`0621f398  fffff880`04598d00Unable to load image \SystemRoot\system32\DRIVERS\cfosspeed6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
 cfosspeed6+0x176d00

Code:

BugCheck D1, {0, 2, 8, 0}

Probably caused by : tcpip.sys ( tcpip!IppSendDatagramsCommon+7ef )

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

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {58, a, 0, fffff88004b77e83}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : hardware ( dxgmms1!VidSchiProfilePerformanceTick+6eb )

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

1: 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: 0000000000000058, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004b77e83, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad100
GetUlongFromAddress: unable to read from fffff800030ad1c0
 0000000000000058 Nonpaged pool

CURRENT_IRQL:  a

FAULTING_IP: 
dxgmms1!VidSchiProfilePerformanceTick+6eb
fffff880`04b77e83 634558          movsxd  eax,dword ptr [rbp+58h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f1b1b0 -- (.trap 0xfffff88002f1b1b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009a58250 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800a477c40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b77e83 rsp=fffff88002f1b340 rbp=0000000000000000
 r8=fffffa80099ef000  r9=0000000000000000 r10=0000000000000000
r11=fffffa8009a3bb10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VidSchiProfilePerformanceTick+0x6eb:
fffff880`04b77e83 634558          movsxd  eax,dword ptr [rbp+58h] ss:0018:00000000`00000058=????????
Resetting default scope

MISALIGNED_IP: 
dxgmms1!VidSchiProfilePerformanceTick+6eb
fffff880`04b77e83 634558          movsxd  eax,dword ptr [rbp+58h]

LAST_CONTROL_TRANSFER:  from fffff80002e75169 to fffff80002e75bc0

STACK_TEXT:  
fffff880`02f1b068 fffff800`02e75169 : 00000000`0000000a 00000000`00000058 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b070 fffff800`02e73de0 : 00000000`00000002 fffff880`02f1b7d0 00000000`ffffffff fffffa80`099f04e0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b1b0 fffff880`04b77e83 : fffffa80`06cb4040 fffff800`02e5aa72 00000000`003a0294 fffffa80`08640000 : nt!KiPageFault+0x260
fffff880`02f1b340 fffff880`04b74666 : fffffa80`099f04e0 fffffa80`09971010 fffffa80`099ef000 fffffa80`099ef000 : dxgmms1!VidSchiProfilePerformanceTick+0x6eb
fffff880`02f1b400 fffff880`04b7417e : fffffa80`099ef000 00000000`00000000 fffffa80`00000001 fffff880`02f1b5a0 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x1da
fffff880`02f1b490 fffff880`04b73f82 : fffffa80`00000b61 fffffa80`08a83f30 fffffa80`099e5000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x1ea
fffff880`02f1b4e0 fffff880`04a7b13f : fffffa80`096e2480 00000000`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02f1b510 fffff880`048c54aa : fffffa80`0a97cc58 00000000`00000001 fffff880`02f1b5c9 fffff980`1e6f4c10 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02f1b540 fffffa80`0a97cc58 : 00000000`00000001 fffff880`02f1b5c9 fffff980`1e6f4c10 fffff880`02f1b750 : atikmpag+0x464aa
fffff880`02f1b548 00000000`00000001 : fffff880`02f1b5c9 fffff980`1e6f4c10 fffff880`02f1b750 fffff880`02d2b438 : 0xfffffa80`0a97cc58
fffff880`02f1b550 fffff880`02f1b5c9 : fffff980`1e6f4c10 fffff880`02f1b750 fffff880`02d2b438 fffff980`1e6f4f68 : 0x1
fffff880`02f1b558 fffff980`1e6f4c10 : fffff880`02f1b750 fffff880`02d2b438 fffff980`1e6f4f68 fffff800`02e5ccab : 0xfffff880`02f1b5c9
fffff880`02f1b560 fffff880`02f1b750 : fffff880`02d2b438 fffff980`1e6f4f68 fffff800`02e5ccab fffff880`00000000 : 0xfffff980`1e6f4c10
fffff880`02f1b568 fffff880`02d2b438 : fffff980`1e6f4f68 fffff800`02e5ccab fffff880`00000000 fffff980`00000000 : 0xfffff880`02f1b750
fffff880`02f1b570 fffff980`1e6f4f68 : fffff800`02e5ccab fffff880`00000000 fffff980`00000000 fffff980`1e6f4c00 : 0xfffff880`02d2b438
fffff880`02f1b578 fffff800`02e5ccab : fffff880`00000000 fffff980`00000000 fffff980`1e6f4c00 fffffa80`0a97cc58 : 0xfffff980`1e6f4f68
fffff880`02f1b580 00000000`00000b61 : 00000000`00000000 fffff880`02f1b718 00000000`00000000 fffff980`1e7f4ea0 : nt!ExFreeToNPagedLookasideList+0x27
fffff880`02f1b5b0 00000000`00000000 : fffff880`02f1b718 00000000`00000000 fffff980`1e7f4ea0 fffff980`1e6f4c10 : 0xb61


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProfilePerformanceTick+6eb
fffff880`04b77e83 634558          movsxd  eax,dword ptr [rbp+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProfilePerformanceTick+6eb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18126

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned_dxgmms1.sys

FAILURE_ID_HASH:  {9d092e7f-b602-fc7d-b143-ab40a5d1b66d}

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

1: kd> lmvm atikmpag
start             end                 module name
fffff880`0487f000 fffff880`04921000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Feb 01 00:58:51 2014 (52EBF973)
    CheckSum:         000A9D84
    ImageSize:        000A2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

** At the rate and frequency the bugcheck codes and probable causes are changing, it is not a very good sign. And, as it is continuing over a long time, it is time to narrowing things down. So, if any test is suggested in this post is done earlier too, do those and report back accordingly. Those will serve the documentation need to narrowing things down.

So upon uninstalling realtek I've not had anymore 0x0A or IRQL related bsods.
I was playing 9dragons, exited, casually surfing the net, computer turned off 'no power to mouse,keyboard or monitor; went back on, upon boot I got; 0x00000024 (0x0000000001904FB, 0xFFFFF88003199078 and can't see the rest.

Also getting the old 1A again which I've included in the attachment , back on track no more device driver errors, please look.

& will attempt to follow what you have said in previous post.

Edit- uninstalled cfos and another one which was fast usb. uninstalled both.

Also got a rather weirdly funny bsod, with no technical information; will attach picture.

It points to the hardware again.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 1056, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )

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

And with another bugcheck code.

Take the hardware tests again ....
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the CPU.
Hardware - Stress Test With Prime95

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

If all those are OK, then replace the PSU with another one.

If it is still the same, we will have no other way but blaming the motherboard.

Arc said:

It points to the hardware again.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 1056, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )

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

And with another bugcheck code.

Take the hardware tests again ....
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the CPU.
Hardware - Stress Test With Prime95

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

If all those are OK, then replace the PSU with another one.

If it is still the same, we will have no other way but blaming the motherboard.

I know for a fact its all pointing to hardware.
After disabling the realtek hd audio, thats where the IRQL bsods etc appeared from 0xD1.
Now we are back onto 0x1A errors and 0x24.
I will attempt to do the tests again, this is the proof I've been needing
edit - awfully loud noise coming from the desktop itself.