Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD Win 7 Ultimate x86

06 Sep 2010   #1
MrEleventy

Windows 7 Ultimate x86
 
 
Random BSOD Win 7 Ultimate x86

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.


My System SpecsSystem Spec
.
06 Sep 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by MrEleventy View Post
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
---------
My System SpecsSystem Spec
Reply

 Random BSOD Win 7 Ultimate x86




Thread Tools






Similar help and support threads
Thread Forum
Random shutdown with no BSOD Win 7 Ultimate 32 bit
I cant find a "crash and debugging" forum section? I keep ending up here? But i have no BSOD. Is this the best place to post this? If not pls move? We have 3 systems from 6/30/11 Windows 7 Ultimate 32 bit. DB65AL motherboard. Intel i5-2300 2.8GHz, 4GB RAM All ran flawlessly for about a...
BSOD Help and Support
Random BSOD, Windows 7 Ultimate x64
Hi all, I am having random BSOD. Ran Windows Memory Diagnostic and it found no errors. BIOS updated. Drivers updated as far as I know. Here is the details from the last crash: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: ...
BSOD Help and Support
Random BSOD Win7 Ultimate x64
Helping a friend fix his PC, but can't seem to pinpoint to what is causing the BSOD. It happens at random time. I had already reinstalled Win7 Ultimate x64 (student edition). Any help would be appreciated. I have attached the minidump and perfmon report. i5-760 @ 2.8 ghz EVGA P55-SLI EVGA...
BSOD Help and Support
Windows 7 Ultimate x64 Random BSOD
Greetings, I have been plagued by these random BSOD's for 6 months or so now, but have simply put up with it. Time has come when I can stand it no longer! :o I have some Minidump files if someone wouldn't mind looking at them - I am clueless when it comes to debugging. :( Thanks in advance...
BSOD Help and Support
Random BSOD 64 bit Ultimate on a New Machine
Hi guys, I've had this computer for about two months, it was bought built without an OS and i've got a technet subscription so i've put Windows 7 Ultimate 64 bit on it. It runs fine most of the time but now and then it'll stop with a BSOD, usually the message is MACHINE_CHECK_EXCEPTION. ...
BSOD Help and Support
W7 Ultimate x64 random BSOD's
Hello all, In the last few days I have been getting crashes seemingly at random. So far I have had a few while playing games, and some while just on the internet. I have attempted to determine the cause myself from the dumps, but I have been unable to. Maybe someone who is a little better at...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 16:33.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App