Bsod

DJexs · 01-01-2009, 03:04 PM

ok my computer keeps crashing going to a blue screen and i dont know why will some1 please help me figure out why and how to fix

i have been cleaning up deleteing stuff i dont want or need and maybe i deleted something i shouldnt by accident

here my specs

Code:

os: windows vista home premium (6.0,build 6001)
system manufacturer:HP-Pavilion
model: gx624aa-aba a6303w
bios date: 12/31/07 10:10:58 ver 5.15
processor: 2 intel pentium dual cpu @1.60ghz
memory: 2046mb ram
page file: ysed 1032mb , available 3301mb
directx version 10

Display 
NVIDIA GeForce 9600GT
integrated ramdac
appx total memort 1268mb
disploy mode 1680 c 1050 32bit 60hz
monitor HP w2007 wide lcd monitor

directx featurs all enabled

driver 
main: nvd3dum.dlll,nvwgf2um.dll
version 7.15.0011.8048(english)
ddi version 10

heres is what i got from minidump file (didnt really know how to open these so followed a tutorial so if i did something wrong tell me)

Code:

1: 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: c0000005, The exception code that was not handled
Arg2: 8240c890, The address that the exception occurred at
Arg3: 88f6fa30, Exception Record Address
Arg4: 88f6f72c, 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!RtlUpcaseUnicodeString+71
8240c890 0fb70c51        movzx   ecx,word ptr [ecx+edx*2]

EXCEPTION_RECORD:  88f6fa30 -- (.exr 0xffffffff88f6fa30)
ExceptionAddress: 8240c890 (nt!RtlUpcaseUnicodeString+0x00000071)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000002
Attempt to read from address 00000002

CONTEXT:  88f6f72c -- (.cxr 0xffffffff88f6f72c)
eax=8902064c ebx=ad30c298 ecx=00000000 edx=00000001 esi=8490fcf8 edi=88f6fb50
eip=8240c890 esp=88f6faf8 ebp=88f6fb2c iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!RtlUpcaseUnicodeString+0x71:
8240c890 0fb70c51        movzx   ecx,word ptr [ecx+edx*2] ds:0023:00000002=????
Resetting default scope

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000002

READ_ADDRESS: GetPointerFromAddress: unable to read from 8233b868
Unable to read MiSystemVaType memory at 8231b420
 00000002 

FOLLOWUP_IP: 
fileinfo!FIStreamQueryWorker+76
87f7b38a 85c0            test    eax,eax

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 824151e0 to 8240c890

STACK_TEXT:  
88f6fb2c 824151e0 88f6fb50 8490fcf8 00000001 nt!RtlUpcaseUnicodeString+0x71
88f6fbac 87f5c669 9ff428d4 9ff7fb20 87f52e00 nt!FsRtlIsNameInExpression+0x29
88f6fbe0 87f60601 86d81020 8490fcc8 9ff428d4 fltmgr!FltpQueryInformationFile+0xc3
88f6fc14 87f616ec 86d81020 9ff7fb20 88f6fc40 fltmgr!FltpGetFileName+0x63
88f6fc24 87f5ea04 9ff7fb20 00000000 9ff7fb20 fltmgr!FltpGetOpenedFileName+0x18
88f6fc40 87f6176c 9ff7fb20 00000000 9ff7fb20 fltmgr!FltpCallOpenedFileNameHandler+0x8a
88f6fc5c 87f61f07 9ff7fb20 00000000 9ff428d4 fltmgr!FltpGetNormalizedFileNameWorker+0x16
88f6fc74 87f5f1a1 9ff7fb20 00000000 9ff7fb20 fltmgr!FltpGetNormalizedFileName+0x19
88f6fc8c 87f4a1df 9ff7fb20 8490fcc8 00000000 fltmgr!FltpCreateFileNameInformation+0x81
88f6fcbc 87f5f713 87b25d94 00000001 00000000 fltmgr!FltpGetFileNameInformation+0x31d
88f6fcd0 87f7b38a 8490fcc8 872afb60 9ff7fb20 fltmgr!FltGetFileNameInformationUnsafe+0x59
88f6fd10 87f65ba2 872ae7c8 872afb60 00003b1f fileinfo!FIStreamQueryWorker+0x76
88f6fd44 8223c445 00000000 00000000 84086ad0 fltmgr!FltpProcessGenericWorkItem+0x38
88f6fd7c 823d9b18 872ae7c8 a9ced29f 00000000 nt!ExpWorkerThread+0xfd
88f6fdc0 82232a2e 8223c348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  fileinfo!FIStreamQueryWorker+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47918be3

STACK_COMMAND:  .cxr 0xffffffff88f6f72c ; kb

FAILURE_BUCKET_ID:  0x7E_fileinfo!FIStreamQueryWorker+76

BUCKET_ID:  0x7E_fileinfo!FIStreamQueryWorker+76

Followup: MachineOwner
---------

1: kd> lmvm fileinfo
start    end        module name
87f74000 87f84000   fileinfo   (pdb symbols)          c:\symbolds\fileinfo.pdb\84E22230534C4E86AB8601A52ADC3ED51\fileinfo.pdb
    Loaded symbol image file: fileinfo.sys
    Mapped memory image file: c:\symbolds\fileinfo.sys\47918BE310000\fileinfo.sys
    Image path: \SystemRoot\system32\drivers\fileinfo.sys
    Image name: fileinfo.sys
    Timestamp:        Fri Jan 18 23:34:27 2008 (47918BE3)
    CheckSum:         0001D398
    ImageSize:        00010000
    File version:     6.0.6001.18000
    Product version:  6.0.6001.18000
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     FileInfo.sys
    OriginalFilename: FileInfo.sys
    ProductVersion:   6.0.6001.18000
    FileVersion:      6.0.6001.18000 (longhorn_rtm.080118-1840)
    FileDescription:  FileInfo Filter Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

theres some info if there is any more info you need just say so and i will do my best to find it, thanks

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.0.6001.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    1000007f
  BCP1:    00000008
  BCP2:    803D3130
  BCP3:    00000000
  BCP4:    00000000
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini123108-07.dmp
  C:\Users\Danny\AppData\Local\Temp\WER-68266-0.sysdata.xml
  C:\Users\Danny\AppData\Local\Temp\WER128.tmp.version.txt

i started writing down the errors here are the last 3 i got

Code:

***STOP 0x0000007e (0x00000008, 0x80152000, 0x00000000, 0x00000000)

Code:

***STOP 0x0000007e (0xc0000005, 0x8244e890, 0x8916fa30, 0x8910f72c)

Code:

***STOP 0x0000007e (0xc0000005, 0x82454840, 0x86f5fa30, 0x88f5f72c)

i have no idea what is doing this i get random crashes and i cant download stuff from microsoft website it says conection lost please try again. will some1 please help thank you

edit: also do not have a disc for vista i dont have any backups and no restore point far enough back

USMC0351 · 01-01-2009, 03:59 PM

Go here http://support.microsoft.com/kb/330182 let us know if this helps solve your problem

DJexs · 01-01-2009, 05:05 PM

no that doesnt help i have vista 2 not xp

**jcgriff2** · 01-01-2009, 06:03 PM

Hi -

The bugcheck 0x7e = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED = a system thread generated an exception - 2 of your BSODs show an exception code of 0xc0000005 - a memory access violation.

I'll look into this for you, but need system information. Please follow THESE instructions carefully. I cannot stress the importance of running the batch file in that link at an elevated administrative level - right-click, select Run as Administrator.

Attach the resulting zip file to your next post.

Regards. . .

jcgriff2

.

DJexs · 01-02-2009, 10:29 AM

thank you both very much for the help here is the file

01-01-2009, 03:59 PM	#2 (permalink)
USMC0351 Registered User Join Date: Aug 2008 Location: Florida Posts: 35 OS: Vista Home Premium SP1 & XP Pro sp3 My System	Re: Bsod Go here http://support.microsoft.com/kb/330182 let us know if this helps solve your problem

01-01-2009, 05:05 PM	#3 (permalink)
DJexs Registered User Join Date: Jan 2009 Posts: 6 OS: vista home premium sp1	Re: Bsod no that doesnt help i have vista 2 not xp

01-01-2009, 06:03 PM	#4 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: Palm Springs, California / Southern New Jersey Posts: 10,067 OS: Windows 7, Vista Ultimate My System	Re: Bsod Hi - The bugcheck 0x7e = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED = a system thread generated an exception - 2 of your BSODs show an exception code of 0xc0000005 - a memory access violation. I'll look into this for you, but need system information. Please follow THESE instructions carefully. I cannot stress the importance of running the batch file in that link at an elevated administrative level - right-click, select Run as Administrator. Attach the resulting zip file to your next post. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread My availability will be limited through ~ December 1, 2009