My laptop started blue screening randomly. At first it just shut off and then back on by itself randomly but now it'll blue screen instead.
Toshiba Satellite A135-S4447, laptop is about 4-5 years old.
Currently running Windows 7 Ultimate x86
Fresh retail install, about 3 days old. Previous OS was Vista.
Any help would be appreciated. Thanks in advance.
Mr Eleventy hi and welocme
these two crashes were blamed on your video driver. HOWEVER, there is a problem with your win 7 image. The file sizes and dates are incorrect so we cant analyze the dmp files correctly.
Where did you get the image?
Did you download it or purchase it from MS?
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Let us know if you need further assistance
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\090610-15740-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x8280d000 PsLoadedModuleList = 0x8294c570 Debug session time: Mon Sep 6 19:34:03.834 2010 (GMT-4) System Uptime: 0 days 0:21:46.144 *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list ...... 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 001904fb Arg2: a8ba7a98 Arg3: a8ba7670 Arg4: 878cdaab Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: Ntfs FAULTING_MODULE: 8280d000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf45 EXCEPTION_RECORD: a8ba7a98 -- (.exr 0xffffffffa8ba7a98) ExceptionAddress: 878cdaab (Ntfs!NtfsFindPrefixHashEntry+0x00000113) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 123bf87a Attempt to read from address 123bf87a CONTEXT: a8ba7670 -- (.cxr 0xffffffffa8ba7670) eax=00001000 ebx=00000fff ecx=123bf83f edx=855a4b48 esi=a5493884 edi=a8ba7c7c eip=878cdaab esp=a8ba7b60 ebp=a8ba7ba4 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 Ntfs!NtfsFindPrefixHashEntry+0x113: 878cdaab 23d9 and ebx,ecx Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x24 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 878ce65b to 878cdaab STACK_TEXT: a8ba7ba4 878ce65b 8481c298 855a4b48 891c4d08 Ntfs!NtfsFindPrefixHashEntry+0x113 a8ba7c00 878d0c5c 8481c298 84911e00 891c4d08 Ntfs!NtfsFindStartingNode+0x7b6 a8ba7cdc 87857210 8481c298 84911e00 a5493884 Ntfs!NtfsCommonCreate+0x65f a8ba7d1c 8286a056 a549381c 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20 WARNING: Stack unwind information not available. Following frames may be wrong. a8ba7d98 8286a14d 00000009 00000000 a5493758 nt!KeRemoveQueueEx+0x1d89 a8ba7d9c 00000000 00000000 a5493758 00000023 nt!KeRemoveQueueEx+0x1e80 FOLLOWUP_IP: Ntfs!NtfsFindPrefixHashEntry+113 878cdaab 23d9 and ebx,ecx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsFindPrefixHashEntry+113 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: Ntfs.sys STACK_COMMAND: .cxr 0xffffffffa8ba7670 ; kb BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
Quote