*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003530433, fffff88007da3da0, 0}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+e3 )
Followup: MachineOwner
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003534433, fffff88009440da0, 0}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+e3 )
Followup: MachineOwner
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 2, 1, fffff800034bf5a2}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
Followup: MachineOwner
I'm not sure about this?TVicPort64.SYS Wed Mar 30 10:12:54 2005: Do you have a TV card installed on your system?
This passed with no errors or anything wrong.Also please find command prompt, right click on it and run as administrator. Type:
sfc /scannow
Press enter and await results.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 2, 1, fffff80003501202}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
Followup: MachineOwner
The above was highlighted simply because of the date. It's ancient and needs to be updated. Check your device manager or installed programs to try and determine what it is.TVicPort64.SYS Wed Mar 30 10:12:54 2005: Do you have a TV card installed on your system?
Yes, I have Ccleaner installed and around the time I was getting many BSOD I did run a duplicator remover of some sort.Have you used anything like a registry cleaner or similar
I did this just now and the dump file I have uploaded should be from that.If the bsod still continues then let's try and flush the driver out (if it is driver related) by using the driver verifier. The guide below will show you how to go on and please post the dump files after:
http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {fffff980a6298ff0, fffff980a629806f, c9c018, 32}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+5eb )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980a6298ff0, address trying to free
Arg2: fffff980a629806f, address where one bit is corrupted
Arg3: 0000000000c9c018, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
Debugging Details:
------------------
BUGCHECK_STR: 0xC1_32
SPECIAL_POOL_CORRUPTION_TYPE: 32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: PathOfExileSte
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff800035502a3 to fffff800034bda40
STACK_TEXT:
fffff880`097261c8 fffff800`035502a3 : 00000000`000000c1 fffff980`a6298ff0 fffff980`a629806f 00000000`00c9c018 : nt!KeBugCheckEx
fffff880`097261d0 fffff800`035c8d23 : 00000000`00000000 00000000`00000001 00000000`00000003 00000000`00000001 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`09726210 fffff800`035f4985 : 00000000`00000174 00000000`6d4d6956 00000000`0019b458 00000000`00000000 : nt!MmFreeSpecialPool+0x1d3
fffff880`09726350 fffff880`1232e06f : 00000000`00000000 00000000`00000000 fffff8a0`02236000 00000000`00000001 : nt!ExAllocatePoolWithTag+0x16bd
fffff880`09726400 fffff880`123408b8 : fffff8a0`02236000 00000000`00000000 00000000`00000000 fffff8a0`02236068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
fffff880`097264f0 fffff880`12325815 : fffff980`fffffeda fffff980`614c8f40 fffff8a0`02236000 fffffa80`0a630000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`09726560 fffff880`12363fee : fffffa80`06c96300 fffffa80`0a630000 fffff980`614c8f40 fffff980`614c8fc0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`09726590 fffff880`12363984 : fffff900`c4d38cd0 00000000`00000000 00000000`00000001 fffff900`c4d38cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`09726640 fffff960`000c7914 : 00000000`00001088 fffff900`c4d38cd0 00000000`00000000 fffff900`c4d38cd0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`097266d0 fffff960`000c7017 : 00000000`00000000 fffff880`09726ae0 fffffa80`083eab50 00000000`00000001 : win32k!GdiProcessCallout+0x244
fffff880`09726750 fffff800`037920bd : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`083eab00 : win32k!W32pProcessCallout+0x6b
fffff880`09726780 fffff800`03776d1d : 00000000`cfffffff 00000000`00000001 00000000`78457300 fffffa80`0895a060 : nt!PspExitThread+0x4d1
fffff880`09726880 fffff800`034b123a : 00000000`0000000b fffff880`60000000 00000000`00000008 fffff800`034e9650 : nt!PsExitSpecialApc+0x1d
fffff880`097268b0 fffff800`034b1580 : 00000000`00000246 fffff880`09726930 fffff800`03776c90 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`09726930 fffff800`034bcd77 : fffff880`09726b60 fffff800`034c7e42 00000000`0000002a 00000000`73762450 : nt!KiInitiateUserApc+0x70
fffff880`09726a70 00000000`73762e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`04aeec28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73762e09
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
fffff880`1232e06f 4d8b5d30 mov r11,qword ptr [r13+30h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539e411c
IMAGE_VERSION: 6.1.7601.18510
FAILURE_BUCKET_ID: X64_0xC1_32_VRF_dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
BUCKET_ID: X64_0xC1_32_VRF_dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc1_32_vrf_dxgkrnl!dxgdevice::destroyallocations+5eb
FAILURE_ID_HASH: {eeff9e28-9d03-f893-3d2e-8ece8903a34d}
Followup: MachineOwner
I did this 1 time, and found no error, do I need to run it for 12hrs like memtest86?The above dump file basically means a driver is writing to an incorrect place. It looks like the graphics were involved too. Check your Vram using this app:
http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en
Did this too, the AMD auto detect and install program said I have latest updates.atikmdag.sys Fri Nov 21 02:30:27 2014: AMD GPU driver. Try removing this driver using DDU (display driver uninstaller):
http://www.wagnardmobile.com/DDU/
Install the latest beta driver from AMD:
http://support.amd.com/en-us
What do you mean? What stick? And how do I run my PC on one stick?. In cases like these the best way to check for a dodgy stick is to run the machine on one stick at a time. Play the game and if the machine bsod's then swap sticks and try again. See if there is a stick which does bsod and one that doesn't.
Not that I know of, so I don't think so.TVicPort64.SYS Wed Mar 30 10:12:54 2005: Do you have a TV card installed on your system?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 148bc001, 0, fffff70001080000}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0 )
Followup: MachineOwner
I was referring to sticks of RAM. You'll need to open up the pc and remove a stick of RAM. Follow the advice above regarding testing. If your unsure on how to remove sticks of RAM then try running Memtest86 again but run it for as long as possible 24hrs if need be.What do you mean? What stick? And how do I run my PC on one stick?
Yes but you have to search for the beta manually. Even if you don't install the latest beta I'd would consider re-installing the driver again as the last two dump files both mention graphics which may mean the driver is corrupted or the gpu has an issue.Did this too, the AMD auto detect and install program said I have latest updates.
No. Once is enough.I did this 1 time, and found no error, do I need to run it for 12hrs like memtest86?
If this is the case then you'll need to repair Windows. Do you have an installation disk or a restore point you could go back to?Also I was running the duplicator remover every now and then, because I thought it would free some space and remove unnecessary files. So I dont exactly remember what happend first. But I belive I ran the Ccleaner and then all turned to shit. So yeah I probably removed something I needed.