bjornk Posted May 22, 2016 Posted May 22, 2016 Copy and paste in your post. The first thing you should do however is to deal with your BIOS. Preferably change it back to what it was before the BIOS update.
Ark of Truth Posted May 22, 2016 Author Posted May 22, 2016 Copy and paste in your post. The first thing you should do however is to deal with your BIOS. Preferably change it back to what it was before the BIOS update. I just use default from within the settings menu, always have. Currently using my computer now to type this.
bjornk Posted May 22, 2016 Posted May 22, 2016 The "default" or the "optimized" settings may not be the best for the RAM you have. Does your RAM support XMP SPD? If it does use it.
Ark of Truth Posted May 22, 2016 Author Posted May 22, 2016 May 20th 2016 14:15:28 Primary Analysis Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045 Machine Name: Kernel base = 0xfffff800`03c01000 PsLoadedModuleList = 0xfffff800`03e43730 Debug session time: Fri May 20 14:15:28.237 2016 (UTC - 4:00) System Uptime: 0 days 0:01:30.408 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffff900c253cba0, the pool entry being checked. Arg3: fffff900c253cba0, the read back flink freelist value (should be the same as 2). Arg4: effff900c253cba0, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003da770f to fffff80003c70400 STACK_TEXT: fffff880`08a37738 fffff800`03da770f : 00000000`00000019 00000000`00000003 fffff900`c253cba0 fffff900`c253cba0 : nt!KeBugCheckEx fffff880`08a37740 fffff800`03da91a1 : fffff900`c0220050 fffff900`c074c9b0 fffff900`c074c9c0 00000000`00000001 : nt!ExFreePool+0x763 fffff880`08a377d0 fffff960`00188168 : fffff900`c074cbf8 fffff900`c24c9010 00000000`35316847 00000000`00000031 : nt!ExFreePoolWithTag+0x411 fffff880`08a37880 fffff960`00188936 : 00000000`00000000 fffff900`c074c9c0 00000000`00000000 fffff900`c074cbf8 : win32k!FreeObject+0x58 fffff880`08a378b0 fffff960`00188acc : fffff900`00000000 fffff900`00000000 fffff900`c074c9c0 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x58a fffff880`08a37a00 fffff960`00188a6d : fffff900`c074c5f0 fffff900`c074c9c0 00000000`00000000 00000000`00000000 : win32k!bDeleteSurface+0x34 fffff880`08a37a30 fffff960`001c1fe7 : 00000000`000101e3 00000000`05402cd0 00000000`00000000 00000000`00000020 : win32k!GreDeleteObject+0x6d fffff880`08a37a60 fffff960`0018fde3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!CleanupCursorObject+0xdb fffff880`08a37a90 fffff960`00139e34 : fffff880`08a37b70 00000000`00000001 fffff900`c2294270 00000000`00000000 : win32k!DestroyCursor+0x53 fffff880`08a37ac0 fffff800`03c6f693 : fffffa80`06e95570 00000000`00000000 00000000`00000020 00000000`2d01024a : win32k!NtUserDestroyCursor+0x84 fffff880`08a37af0 00000000`770fceca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`03d1e9b8 fffff800`03c67a50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770fceca fffff880`08a37cd0 00000000`03d1f7a8 : fffff800`041eeb7f 00000000`00000030 fffff880`08a37dd0 00000000`00000000 : nt!KiCallUserMode fffff880`08a37cd8 fffff800`041eeb7f : 00000000`00000030 fffff880`08a37dd0 00000000`00000000 fffff880`08a38700 : 0x3d1f7a8 fffff880`08a37ce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalSendSoftwareInterrupt+0x48 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExFreePool+763 fffff800`03da770f cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExFreePool+763 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+763 BUCKET_ID: X64_0x19_3_nt!ExFreePool+763 Followup: Pool_corruption May 20th 2016 14:13:21 Primary Analysis Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045 Machine Name: Kernel base = 0xfffff800`03c68000 PsLoadedModuleList = 0xfffff800`03eaa730 Debug session time: Fri May 20 14:13:21.322 2016 (UTC - 4:00) System Uptime: 0 days 1:41:40.493 ******************************************************************************* * * * 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: ffffea8053936938, 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: fffff80003cf646f, address which referenced memory Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003f14100 GetUlongFromAddress: unable to read from fffff80003f141c8 ffffea8053936938 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveProtoPteFault+13f fffff800`03cf646f 488b00 mov rax,qword ptr [rax] DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: chrome.exe TRAP_FRAME: fffff88008a68650 -- (.trap 0xfffff88008a68650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffea8053936938 rbx=0000000000000000 rcx=0000000000000004 rdx=000000000001b25e rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003cf646f rsp=fffff88008a687e0 rbp=fffff8a02146f328 r8=0000000000000000 r9=0000058000000000 r10=000007fede5fc000 r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe nc nt!MiResolveProtoPteFault+0x13f: fffff800`03cf646f 488b00 mov rax,qword ptr [rax] ds:ffffea80`53936938=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003cd69a9 to fffff80003cd7400 STACK_TEXT: fffff880`08a68508 fffff800`03cd69a9 : 00000000`0000000a ffffea80`53936938 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`08a68510 fffff800`03cd5620 : 00000000`131b5121 fffff880`08a686d0 fffffa80`003951f0 00000000`1b25e121 : nt!KiBugCheckDispatch+0x69 fffff880`08a68650 fffff800`03cf646f : 77f00000`1f85d025 00000000`1f85d121 fffffa80`09b47ea0 fffff880`08a688f0 : nt!KiPageFault+0x260 fffff880`08a687e0 fffff800`03cf4cf3 : 00000000`00000d49 000007fe`de5fc000 fffff683`ff6f2fe0 fffffa80`0a93e7f8 : nt!MiResolveProtoPteFault+0x13f fffff880`08a68870 fffff800`03ce4679 : 00000000`00000000 000007fe`de5fc000 fffffa80`537dab50 fffffa80`00000000 : nt!MiDispatchFault+0x1c3 fffff880`08a68980 fffff800`03cd552e : 00000000`00000000 000007fe`de5fc000 00000000`02b15e01 000007fe`de5fc000 : nt!MmAccessFault+0x359 fffff880`08a68ae0 000007fe`ec595125 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0029ea80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ec595125 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveProtoPteFault+13f fffff800`03cf646f 488b00 mov rax,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveProtoPteFault+13f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 5708972e IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+13f BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+13f Followup: MachineOwner
windpl Posted May 22, 2016 Posted May 22, 2016 Well this crash dump dosen't says anything mostly it is like "something went wrong". But at last you know that ram is good Most companies have a lifetime warranty on ram so check into that if it is the case. Might get a replacment lifetime* ** *** * In germany lifetime is 10 years ** Everywhere, it is till exact model is still manufactured *** Does not include physical damaged, so if it was factory damaged and you discovered it later then you are fucked.
Ark of Truth Posted May 22, 2016 Author Posted May 22, 2016 Well I have put my PC back together I using it. Hoping whatever the issue was went away when I cleaned the RAM ports (which had some dust in them) and memtest is giving false positives. We will soon see. I wonder if battle encoder shirase had anything to do with it.....
bjornk Posted May 22, 2016 Posted May 22, 2016 Out of curiosity, have you reinstalled your graphics drivers recently? Or any other driver?
Ark of Truth Posted May 22, 2016 Author Posted May 22, 2016 Out of curiosity, have you reinstalled your graphics drivers recently? Or any other driver? I did get a bluescreen error related to my graphics driver. After I got it I removed all graphics drivers completely and reinstalled latest stable one. Apart from that I haven't really installed anything new apart from some new games which I wasn't even playing at time of crash.
RitualClarity Posted May 22, 2016 Posted May 22, 2016 Well this crash dump dosen't says anything mostly it is like "something went wrong". But at last you know that ram is good Most companies have a lifetime warranty on ram so check into that if it is the case. Might get a replacment lifetime* ** *** * In germany lifetime is 10 years ** Everywhere, it is till exact model is still manufactured *** Does not include physical damaged, so if it was factory damaged and you discovered it later then you are fucked. Which in most case you mention would still be covered short of physical damage or abuse. DDR3 isn't 10 years old yet and his is likely less than 5 years old (model). Since it isn't PC100 ram he should still be covered under the *lifetime* warranty . Well I have put my PC back together I using it. Hoping whatever the issue was went away when I cleaned the RAM ports (which had some dust in them) and memtest is giving false positives. We will soon see. I wonder if battle encoder shirase had anything to do with it..... Doubt any program would cause that issue with the memory, now blue screens maybe.
bjornk Posted May 22, 2016 Posted May 22, 2016 * In germany lifetime is 10 yearsThat sounds like the amount of time a manufacturer have to support their product (keeping spare parts in stock etc), not the time "lifetime warranty" covers, otherwise they'd just say "10 year warranty".
Ark of Truth Posted May 23, 2016 Author Posted May 23, 2016 Well been playing Kenshi all day and no bluescreens. With some Getamped 2.
oticon Posted May 24, 2016 Posted May 24, 2016 a couple of ?'s for you, is your date and time correct? since your last few tests have you changed or corrected your Memory paging file? also check to make certain your Sata hard drives are firmly connected, as the paging file for your memory also manages the paging file for all ram disk buffers
Ark of Truth Posted June 1, 2016 Author Posted June 1, 2016 Well in the end I reinstalled Windows 7 completely and still get odd Bluescreen. Latest one was this, which makes no sense. Fresh install with only Chrome, Avast and Radeon Settings. Whats even more annoying is sometimes the computer can go a whole day without a single bluescreen. But it is looking like a hardware fault somewhere.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.