 | Diablo 3 crash BSOD(1) | Category: Technical SupportMay-21-2014 6:53 AM PDT (9 years ago)  |
| Today I play again Diablo 3 and my PC randomly crashes with this BSOD error: 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.18409.amd64fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e53890 Debug session time: Wed May 21 09:42:57.918 2014 (UTC - 4:00) System Uptime: 1 days 5:52:10.746 ******************************************************************************* * * * 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: 0000000000013a62, 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: fffff80002cb6036, 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 fffff80002ebd100 GetUlongFromAddress: unable to read from fffff80002ebd1c0 0000000000013a62 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveTransitionFault+136 fffff800`02cb6036 488b10 mov rdx,qword ptr [rax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: Diablo III.exe TRAP_FRAME: fffff88007b945c0 -- (.trap 0xfffff88007b945c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000013a62 rbx=0000000000000000 rcx=0000000000000004 rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cb6036 rsp=fffff88007b94750 rbp=fffff8a008e03008 r8=ffffffffffffffff r9=000000003e1ec860 r10=0000000000000000 r11=0000058000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiResolveTransitionFault+0x136: fffff800`02cb6036 488b10 mov rdx,qword ptr [rax] ds:00000000`00013a62=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c85169 to fffff80002c85bc0 STACK_TEXT: fffff880`07b94478 fffff800`02c85169 : 00000000`0000000a 00000000`00013a62 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`07b94480 fffff800`02c83de0 : fffff880`07b94880 00000000`00000000 00000000`c0000001 00000000`3e1ec860 : nt!KiBugCheckDispatch+0x69 fffff880`07b945c0 fffff800`02cb6036 : 4dc00001`dac6b025 00000001`dac6b121 fffffa80`05905410 fffffa80`071273f8 : nt!KiPageFault+0x260 fffff880`07b94750 fffff800`02ca3b35 : 00000000`00000000 00000000`3e1ec860 00000000`00000355 fffffa80`071273f8 : nt!MiResolveTransitionFault+0x136 fffff880`07b947e0 fffff800`02ca24f3 : 00000000`00157ee2 00000000`00df8eb0 fffff680`00006fc0 fffffa80`071273f8 : nt!MiResolveProtoPteFault+0x325 fffff880`07b94870 fffff800`02c92179 : 00000000`00000000 00000000`00df8eb0 fffffa80`0c102060 00000000`00000000 : nt!MiDispatchFault+0x1c3 fffff880`07b94980 fffff800`02c83cee : 00000000`00000008 00000000`00df8eb0 00000000`0018f501 00000000`00000000 : nt!MmAccessFault+0x359 fffff880`07b94ae0 00000000`00df8eb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0018f884 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xdf8eb0 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveTransitionFault+136 fffff800`02cb6036 488b10 mov rdx,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveTransitionFault+136 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+136 BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+136 Followup: MachineOwner I mentioned I have all drivers up to date.Besides this,always I have randomly disconnect from battle net,and my ISP is working excellent. | ||
 | Diablo 3 crash BSOD(2) | May-21-2014 5:35 PM PDT (9 years ago) |
| ghost1, Please post your DXDIAG file so we can get more information about your computer. Here's a support article that will show you how to get the DXDIAG: Obtaining System Files Once you have the DXDIAG file, open it and copy/paste the entire file into your next reply. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Diablo 3 crash BSOD(4) | May-21-2014 7:58 PM PDT (9 years ago) |
| ghost1, Let's try a different video driver to see if that helps. Uninstall the current driver by using AMD Clean Uninstall Utility. This program will ensure that all previous driver files are completely removed. Here's a link to the AMD Clean Uninstall Utility download. Once downloaded, run the AMD Clean Uninstall Utility and follow the steps outlined on the download page. When the utility is done removing the AMD files, restart the system when asked to do so. Then download and install the driver linked below. Here's a link for the new driver download: http://support.amd.com/en-us/download/desktop/previous/detail?os=Windows%207%20-%2064&rev=13.1#amd-catalyst-packages ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Diablo 3 crash BSOD(7) | May-22-2014 1:30 PM PDT (9 years ago) |
| ghost1, 1. The driver that I linked is not the newest one. The newest drivers aren't always the most stable, so I linked you an older version that seems to have the least amount of issues. 2. The other issue that you are asking about is not going to be related to the BSODs. Let's focus on one issue at a time so we don't end up getting confused. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Diablo 3 crash BSOD(9) | May-25-2014 2:19 PM PDT (9 years ago) |
| ghost1, OK, let's look at the other issue then. Let's try deleting the Battle.net tools folder and the Battle.net Cache folder to see if that helps. Once those are deleted, run the launcher as an admin by right clicking on the launcher and selecting "Run as admin". ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Diablo 3 crash BSOD(11) | May-26-2014 4:25 PM PDT (9 years ago) |
| ghost1, Don't worry about it. Just go ahead and delete the entire Battle.net folder. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Diablo 3 crash BSOD(12) | May-26-2014 5:25 PM PDT (9 years ago) |
| ghost1, Sound Capture Devices --------------------- Description: Capture (Pinnacle PCTV 100i Stereo NTSC Capture Device) I also noticed that you have a Pinnacle PCTV sound capture device installed. If possible, try disabling or uninstalling this device to see if that helps. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
