[FAQ] PC auto restart/Blue Screen (BSOD)

Lowyat.NET forums

Lowyat.NET Kopitiam Garage Sales

Lowyat.NET Rules and Regulations FAQ Help Search Members

Welcome Guest ( Log In | Register )

Lowyat.NET -> Technical Support

Bump Topic Add Reply RSS Feed

Outline · [ Standard ] · Linear+

[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views

Zyi	Apr 21 2013, 04:00 AM Return to original view \| Post #1
Getting Started Junior Member 172 posts Joined: Oct 2010 From: Kuala Lumpur	QUOTE(Arvinaaaaa @ Apr 19 2013, 01:25 AM) Guys I have bsod..please help me, thank you Please attach your minidump files here and let use debug it. QUOTE(R3turn @ Apr 20 2013, 05:17 PM) Oced processor .. sometime bsod only when !about! to enter window .. if window started .. can run prime test / intel burn test without any error ..games can be played for hours .. any quick idea why ? Attach your minidump files here too.
Card PM	Report Top Like Quote Reply

Zyi	Apr 21 2013, 03:57 PM Return to original view \| Post #2
Getting Started Junior Member 172 posts Joined: Oct 2010 From: Kuala Lumpur	QUOTE(Arvinaaaaa @ Apr 21 2013, 03:33 PM) CODE Opened log file 'c:\Arvinaaaaa.txt' 3: kd> .sympath srvc:\symbolshttp://msdl.microsoft.com/download/symbols Symbol search path is: srvc:\symbolshttp://msdl.microsoft.com/download/symbols Expanded Symbol search path is: srvc:\symbolshttp://msdl.microsoft.com/download/symbols 3: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * 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: fffff8800157f4f0, The address that the exception occurred at Arg3: fffff8800a083498, Exception Record Address Arg4: fffff8800a082cf0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: ndis!ndisParseReceivedNBL+40 fffff880`0157f4f0 8b7928 mov edi,dword ptr [rcx+28h] EXCEPTION_RECORD: fffff8800a083498 -- (.exr 0xfffff8800a083498) .exr 0xfffff8800a083498 ExceptionAddress: fffff8800157f4f0 (ndis!ndisParseReceivedNBL+0x0000000000000040) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800a082cf0 -- (.cxr 0xfffff8800a082cf0) .cxr 0xfffff8800a082cf0 rax=fffffa8006e01250 rbx=fffff8800a083800 rcx=00009c0101000000 rdx=fffffa8006e01120 rsi=fffffa8006e01120 rdi=0000000000000000 rip=fffff8800157f4f0 rsp=fffff8800a0836d0 rbp=0000000000000000 r8=fffff8800a0837a8 r9=fffff8800a0837a0 r10=0000000000000000 r11=fffff8800a083798 r12=fffff8800a0837a0 r13=0000000000000000 r14=fffff8800a0837a8 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 ndis!ndisParseReceivedNBL+0x40: fffff880`0157f4f0 8b7928 mov edi,dword ptr [rcx+28h] ds:002b:00009c01`01000028=???????? .cxr Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031040e0 ffffffffffffffff FOLLOWUP_IP: ndis!ndisParseReceivedNBL+40 fffff880`0157f4f0 8b7928 mov edi,dword ptr [rcx+28h] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff8800157f242 to fffff8800157f4f0 STACK_TEXT: fffff880`0a0836d0 fffff880`0157f242 : fffffa80`06e00000 fffff880`0a083820 00000000`00000000 00000000`00000000 : ndis!ndisParseReceivedNBL+0x40 fffff880`0a083720 fffff880`0157eeb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisSortNetBufferLists+0xc2 fffff880`0a0837a0 fffff880`0154727e : fffffa80`067521a0 00000000`00000003 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0xc5 fffff880`0a083c20 fffff880`01547573 : fffffa80`067521a0 fffffa80`067521a0 00000000`00000080 fffffa80`05d29900 : ndis!ndisDoPeriodicReceivesIndication+0x14e fffff880`0a083c80 fffff880`01530b0c : 00000000`00010300 fffffa80`06753388 00000000`00000080 fffffa80`05d29910 : ndis!ndisPeriodicReceivesWorker+0x63 fffff880`0a083cb0 fffff800`03171166 : 00000000`0af1313b fffffa80`07a6ab60 00000000`00000080 fffffa80`07a6ab60 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0a083d40 fffff800`02eac486 : fffff880`02fd3180 fffffa80`07a6ab60 fffff880`02fddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0a083d80 00000000`00000000 : fffff880`0a084000 fffff880`0a07e000 fffff880`0a083a00 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ndis!ndisParseReceivedNBL+40 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184 STACK_COMMAND: .cxr 0xfffff8800a082cf0; kb FAILURE_BUCKET_ID: X64_0x7E_ndis!ndisParseReceivedNBL+40 BUCKET_ID: X64_0x7E_ndis!ndisParseReceivedNBL+40 Followup: MachineOwner --------- rax=fffffa8006e01250 rbx=fffff8800a083800 rcx=00009c0101000000 rdx=fffffa8006e01120 rsi=fffffa8006e01120 rdi=0000000000000000 rip=fffff8800157f4f0 rsp=fffff8800a0836d0 rbp=0000000000000000 r8=fffff8800a0837a8 r9=fffff8800a0837a0 r10=0000000000000000 r11=fffff8800a083798 r12=fffff8800a0837a0 r13=0000000000000000 r14=fffff8800a0837a8 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 ndis!ndisParseReceivedNBL+0x40: fffff880`0157f4f0 8b7928 mov edi,dword ptr [rcx+28h] ds:002b:00009c01`01000028=???????? Child-SP RetAddr : Args to Child : Call Site fffff880`0a0836d0 fffff880`0157f242 : fffffa80`06e00000 fffff880`0a083820 00000000`00000000 00000000`00000000 : ndis!ndisParseReceivedNBL+0x40 fffff880`0a083720 fffff880`0157eeb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisSortNetBufferLists+0xc2 fffff880`0a0837a0 fffff880`0154727e : fffffa80`067521a0 00000000`00000003 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0xc5 fffff880`0a083c20 fffff880`01547573 : fffffa80`067521a0 fffffa80`067521a0 00000000`00000080 fffffa80`05d29900 : ndis!ndisDoPeriodicReceivesIndication+0x14e fffff880`0a083c80 fffff880`01530b0c : 00000000`00010300 fffffa80`06753388 00000000`00000080 fffffa80`05d29910 : ndis!ndisPeriodicReceivesWorker+0x63 fffff880`0a083cb0 fffff800`03171166 : 00000000`0af1313b fffffa80`07a6ab60 00000000`00000080 fffffa80`07a6ab60 : ndis!ndisReceiveWorkerThread+0x12c fffff880`0a083d40 fffff800`02eac486 : fffff880`02fd3180 fffffa80`07a6ab60 fffff880`02fddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0a083d80 00000000`00000000 : fffff880`0a084000 fffff880`0a07e000 fffff880`0a083a00 00000000`00000000 : nt!KxStartSystemThread+0x16 Unloaded modules: fffff880`01924000 fffff880`01932000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01932000 fffff880`0193e000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0193e000 fffff880`01947000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01947000 fffff880`0195a000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:\Arvinaaaaa.txt Are you using laptop or any sort of wireless network card? This post has been edited by Zyi**: Apr 21 2013, 03:57 PM
Card PM	Report Top Like Quote Reply

Zyi	Apr 21 2013, 04:07 PM Return to original view \| Post #3
Getting Started Junior Member 172 posts Joined: Oct 2010 From: Kuala Lumpur	The driver failed point to your network/lan card issue, have you update anything on your lan/network? What antivirus are you using?
Card PM	Report Top Like Quote Reply

Zyi	Apr 21 2013, 04:27 PM Return to original view \| Post #4
Getting Started Junior Member 172 posts Joined: Oct 2010 From: Kuala Lumpur	QUOTE(Arvinaaaaa @ Apr 21 2013, 04:10 PM) nope never update anything on my lan..drivers are default driver realtek...but the network im using is my university's internet. using avast antivirus.. Open device manager and see any faulty devices there. CODE Start > Device Manager > Expend all of the devices and see any yellow mark stand for faulty Try updating your Realtek Network driver. Before any update, make sure you create a system restore first. CODE Right click Computer > Properties > System protection > Create system restore
Card PM	Report Top Like Quote Reply

« Next Oldest · Technical Support · Next Newest »

Add Reply Options

Change to:

0.0533sec

0.40

7 queries

GZIP Disabled
Time is now: 9th December 2025 - 12:58 PM

All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)

Removal Request

Powered by Invision Power Board © 2025 IPS, Inc.