New
#1
BSOD error 0x000000E1
please help me to fix this, and here my attachment
Last edited by yogareksodirdjo; 16 Jun 2015 at 01:29.
please help me to fix this, and here my attachment
Last edited by yogareksodirdjo; 16 Jun 2015 at 01:29.
The zip you uploaded does not contain any crash dump.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.
Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.
Dont run any disc cleanup tool before you upload another zip.
Attachment 351825hello, iam already fix that, n i can find .dmp file on that folder, n here my new attachment. please help to translate that sir! :) and iam when iam logon this pop up appear after i overwrite registry. how to fix that?
Last edited by yogareksodirdjo; 07 Mar 2015 at 08:36.
Uninstall Hotspot Shield.
Code:BugCheck 1000007E, {ffffffffc0000005, fffff88006e02fbb, fffff8800b096218, fffff8800b095a70} Probably caused by : hssdrv6.sys ( hssdrv6+2fbb ) Followup: MachineOwner --------- 0: 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: fffff88006e02fbb, The address that the exception occurred at Arg3: fffff8800b096218, Exception Record Address Arg4: fffff8800b095a70, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. FAULTING_IP: hssdrv6+2fbb fffff880`06e02fbb 49894308 mov qword ptr [r11+8],rax EXCEPTION_RECORD: fffff8800b096218 -- (.exr 0xfffff8800b096218) ExceptionAddress: fffff88006e02fbb (hssdrv6+0x0000000000002fbb) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800b095a70 -- (.cxr 0xfffff8800b095a70;r) rax=fffff88006e15a20 rbx=fffffa800b083228 rcx=fffffa800b083480 rdx=0000000000000000 rsi=fffff88006e15a20 rdi=0000000000000000 rip=fffff88006e02fbb rsp=fffff8800b096450 rbp=fffffa800b079622 r8=0000000000000000 r9=0000000000000000 r10=0000000000000029 r11=262d4d485e2d4d38 r12=fffffa800b07965d r13=0000000000000000 r14=0000000000000000 r15=fffff8800b096540 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 hssdrv6+0x2fbb: fffff880`06e02fbb 49894308 mov qword ptr [r11+8],rax ds:002b:262d4d48`5e2d4d40=???????????????? Last set context: rax=fffff88006e15a20 rbx=fffffa800b083228 rcx=fffffa800b083480 rdx=0000000000000000 rsi=fffff88006e15a20 rdi=0000000000000000 rip=fffff88006e02fbb rsp=fffff8800b096450 rbp=fffffa800b079622 r8=0000000000000000 r9=0000000000000000 r10=0000000000000029 r11=262d4d485e2d4d38 r12=fffffa800b07965d r13=0000000000000000 r14=0000000000000000 r15=fffff8800b096540 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 hssdrv6+0x2fbb: fffff880`06e02fbb 49894308 mov qword ptr [r11+8],rax ds:002b:262d4d48`5e2d4d40=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b070e8 GetUlongFromAddress: unable to read from fffff80003b07198 ffffffffffffffff FOLLOWUP_IP: hssdrv6+2fbb fffff880`06e02fbb 49894308 mov qword ptr [r11+8],rax BUGCHECK_STR: 0x7E ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre LAST_CONTROL_TRANSFER: from fffff88006e15a20 to fffff88006e02fbb STACK_TEXT: fffff880`0b096450 fffff880`06e15a20 : fffffa80`0b07964d 00000000`00000000 fffffa80`0b079683 00000000`00000000 : hssdrv6+0x2fbb fffff880`0b096458 fffffa80`0b07964d : 00000000`00000000 fffffa80`0b079683 00000000`00000000 fffff880`06e04c14 : hssdrv6+0x15a20 fffff880`0b096460 00000000`00000000 : fffffa80`0b079683 00000000`00000000 fffff880`06e04c14 fffffa80`0b079683 : 0xfffffa80`0b07964d SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: hssdrv6+2fbb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hssdrv6 IMAGE_NAME: hssdrv6.sys DEBUG_FLR_IMAGE_TIMESTAMP: 53727853 STACK_COMMAND: .cxr 0xfffff8800b095a70 ; kb FAILURE_BUCKET_ID: X64_0x7E_hssdrv6+2fbb BUCKET_ID: X64_0x7E_hssdrv6+2fbb ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x7e_hssdrv6+2fbb FAILURE_ID_HASH: {e1fb4e7c-2039-3039-152e-3cf5bc8c8da2} Followup: MachineOwner --------- 0: kd> lmvm hssdrv6 start end module name fffff880`06e00000 fffff880`06e1a000 hssdrv6 T (no symbols) Loaded symbol image file: hssdrv6.sys Image path: hssdrv6.sys Image name: hssdrv6.sys Timestamp: Wed May 14 01:23:55 2014 (53727853) CheckSum: 00014C7E ImageSize: 0001A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
please help my BSOD, i get this 2 times.
You are running an extremely bad setup. Two 667 MHz RAMs and two 800 MHz RAM. That is the worst possible computing.Code:BugCheck A, {fffff980000000e6, 2, 0, fffff80003dad304} Probably caused by : Unknown_Image ( nt!RtlMultiByteToUnicodeN+88 ) Followup: MachineOwner ---------
Remove either two, not for any test but permanently, irrespective of the occurrence of the BSODs.
Let us know the situation after removing the mismatch RAMs.
_______________________________________________________
Code:Device Locator A1_DIMM0 Bank Locator A1_BANK0 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 800MHz Manufacturer UndefinedCode:Bank Locator A1_BANK1 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 667MHz Manufacturer CorsairCode:Device Locator A1_DIMM2 Bank Locator A1_BANK2 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 800MHz Manufacturer UndefinedCode:Device Locator A1_DIMM3 Bank Locator A1_BANK3 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 667MHz Manufacturer Corsair