Blue Screen on a Toshiba laptop (l650-11r)
Hello there. I have a 8 months old Toshiba Satelite l650-11r laptop and lately I've been experiencing blue screens of deadth. Unfortunately I cannot really say when they started happening (I delete my logs every few months). I have Windows 7 Home Premium installed which was installed by a manufacturer together with all necessary drivers for network, graphic adapter, etc. I haven't had a chance to format and reinstall Windows because I need my laptop in school on a daily basis. I must say that Blue Screens are not so frequently (like every 2 weeks) but it is very annoying when I leave my laptop turned on and when I come back I see either "Disk Error occured. Press ctrl+alt + sth to reboot" or Blue Screen. Sometimes I get a Blue Screen even when I'm working. I've included logs from event viewer but I had to translate them because they are not in English. I hope you can help me with information I provided because I would really want to know if these blue screens are hardware or software related. Thank you in advance for your help. I've included logs from event viewer and minidump files. You can find them here -> http://cid-f579d52f31585d80.skydrive.live.com/redir.aspx?resid=F579D52F31585D80!458
May 15th, 2011 10:57am

******************************************************************************* * * * 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: fffff80002cdbbfa, The address that the exception occurred at Arg3: fffff880077a1f98, Exception Record Address Arg4: fffff880077a17f0, 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: nt!ExAcquireFastMutex+1a fffff800`02cdbbfa f00fba3100 lock btr dword ptr [rcx],0 EXCEPTION_RECORD: fffff880077a1f98 -- (.exr 0xfffff880077a1f98) Cannot read Exception record @ fffff880077a1f98 CONTEXT: fffff880077a17f0 -- (.cxr 0xfffff880077a17f0) rax=0000000000000001 rbx=00fffa800800bb70 rcx=00fffa800800bb70 rdx=ffffffdff97bf9e0 rsi=fffff8a0025f9000 rdi=0000000000000000 rip=fffff80002cdbbfa rsp=fffff880077a21d0 rbp=ffff0000025f0000 r8=0000000000000000 r9=0000000000000000 r10=0055005c003a0043 r11=fffff8a00dfe2c80 r12=fffff880077a2358 r13=0000000000000005 r14=fffffa8007aa0ae0 r15=ffffffffffffffff iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!ExAcquireFastMutex+0x1a: fffff800`02cdbbfa f00fba3100 lock btr dword ptr [rcx],0 ds:002b:00fffa80`0800bb70=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1 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 fffff80002efa0e8 ffffffffffffffff FOLLOWUP_IP: srvnet!SrvAdminRegisterFile+123 fffff880`06791c43 440fb6b424a0000000 movzx r14d,byte ptr [rsp+0A0h] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88006791c43 to fffff80002cdbbfa STACK_TEXT: fffff880`077a21d0 fffff880`06791c43 : fffffa80`096d0498 fffffa80`07aa0b50 fffffa80`07aa0ae0 fffff880`06622110 : nt!ExAcquireFastMutex+0x1a fffff880`077a2200 fffff880`0662c6e3 : fffff8a0`037e0250 fffffa80`07aa0830 fffffa80`07aa0ae0 fffffa80`07aa0b50 : srvnet!SrvAdminRegisterFile+0x123 fffff880`077a22a0 fffff880`0662d0c4 : fffff880`04254cf0 fffffa80`043bc480 fffffa80`00000002 fffffa80`07aa0be8 : srv2!SrvCreateFile+0x8b3 fffff880`077a2ac0 fffff880`066290a7 : fffffa80`07aa0ae0 fffff880`06622110 fffffa80`07aa0830 fffff880`06622110 : srv2!Smb2ExecuteCreateReal+0x1c4 fffff880`077a2c20 fffff880`066295d0 : fffffa80`07aa0830 fffffa80`071ad320 fffff880`06622110 fffff880`06622110 : srv2!Smb2ExecuteProviderCallback+0x97 fffff880`077a2c80 fffff880`0662923a : 00000000`0000000e 00000000`000007fa fffffa80`08394d00 fffffa80`07aa0840 : srv2!SrvProcessPacket+0xa0 fffff880`077a2cc0 fffff800`02f66cce : 00000000`0402ffc0 fffffa80`084f1b60 00000000`00000080 fffffa80`03b55b30 : srv2!SrvProcWorkerThread+0x15a fffff880`077a2d40 fffff800`02cbafe6 : fffff880`033d3180 fffffa80`084f1b60 fffffa80`07d0bb60 fffff880`01667384 : nt!PspSystemThreadStartup+0x5a fffff880`077a2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: srvnet!SrvAdminRegisterFile+123 FOLLOWUP_NAME: MachineOwner MODULE_NAME: srvnet IMAGE_NAME: srvnet.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79478 STACK_COMMAND: .cxr 0xfffff880077a17f0 ; kb FAILURE_BUCKET_ID: X64_0x7E_srvnet!SrvAdminRegisterFile+123 BUCKET_ID: X64_0x7E_srvnet!SrvAdminRegisterFile+123 Followup: MachineOwner --------- 2: kd> lmvm srvnet start end module name fffff880`0678f000 fffff880`067c0000 srvnet (pdb symbols) c:\symbols\srvnet.pdb\BFBEF45790B94BD2BBF8C671976645B82\srvnet.pdb Loaded symbol image file: srvnet.sys Mapped memory image file: c:\symbols\srvnet.sys\4CE7947831000\srvnet.sys Image path: \SystemRoot\System32\DRIVERS\srvnet.sys Image name: srvnet.sys Timestamp: Sat Nov 20 10:27:20 2010 (4CE79478) CheckSum: 00034967 ImageSize: 00031000 File version: 6.1.7601.17514 Product version: 6.1.7601.17514 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.6 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: SRVNET.SYS OriginalFilename: SRVNET.SYS ProductVersion: 6.1.7601.17514 FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850) FileDescription: Server Network driver LegalCopyright: © Microsoft Corporation. All rights reserved. -------------------------------------------------------------------------------------------------------- Bug Check Code 0x1000007e: http://msdn.microsoft.com/en-us/library/ff557196(VS.85).aspx Your BSOD was cause by srvnet.sys driver which belongs to Microsoft server network driver file. Update your NIC card drivers and check if this solve your problem. Do you have AVG installed? This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2011 12:08pm

So basically all BSOD were caused by this network driver ?
May 15th, 2011 1:14pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics