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: BSOD can't pinpoint what is triggering it

18 Apr 2012   #1
toscakat

windows 7 home premium 64 bit?
 
 
BSOD can't pinpoint what is triggering it

I've been getting a BSOD about 5 times a day for the last week or 2. I ran a debug program and it was saying something about symbols so I downloaded a symbol pack. Computer was fine for 2 days then today it happened again while I was just doing homework on internet explorer. I ran another debug and this one came up with different things. I have no idea what I'm doing so I've given up trying to figure it out on my own. Not sure what exactly I'm supposed to post so I'm hoping this is the right thing. Thanks for any help.


Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\symbols\041812-41387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02eaa650
Debug session time: Wed Apr 18 17:37:43.277 2012 (UTC - 4:00)
System Uptime: 2 days 19:59:46.791
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.............................
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff8a001079c68, ffffffffc000009d, b4947860, fffff96000204368}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : win32k.sys ( win32k+184368 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff8a001079c68, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 00000000b4947860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff96000204368, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: win32k

FAULTING_MODULE: fffff80002c66000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d52f12 to fffff80002ce2c80

STACK_TEXT:
fffff880`0ba28cb8 fffff800`02d52f12 : 00000000`0000007a fffff8a0`01079c68 ffffffff`c000009d 00000000`b4947860 : nt+0x7cc80
fffff880`0ba28cc0 00000000`0000007a : fffff8a0`01079c68 ffffffff`c000009d 00000000`b4947860 fffff960`00204368 : nt+0xecf12
fffff880`0ba28cc8 fffff8a0`01079c68 : ffffffff`c000009d 00000000`b4947860 fffff960`00204368 ffffffff`ffffffff : 0x7a
fffff880`0ba28cd0 ffffffff`c000009d : 00000000`b4947860 fffff960`00204368 ffffffff`ffffffff 00000000`c000009d : 0xfffff8a0`01079c68
fffff880`0ba28cd8 00000000`b4947860 : fffff960`00204368 ffffffff`ffffffff 00000000`c000009d fffffa80`00000000 : 0xffffffff`c000009d
fffff880`0ba28ce0 fffff960`00204368 : ffffffff`ffffffff 00000000`c000009d fffffa80`00000000 fffff960`00204368 : 0xb4947860
fffff880`0ba28ce8 ffffffff`ffffffff : 00000000`c000009d fffffa80`00000000 fffff960`00204368 fffff800`02d0a005 : win32k+0x184368
fffff880`0ba28cf0 00000000`c000009d : fffffa80`00000000 fffff960`00204368 fffff800`02d0a005 fffffa80`03ecdf80 : 0xffffffff`ffffffff
fffff880`0ba28cf8 fffffa80`00000000 : fffff960`00204368 fffff800`02d0a005 fffffa80`03ecdf80 fffffa80`03ecdf80 : 0xc000009d
fffff880`0ba28d00 fffff960`00204368 : fffff800`02d0a005 fffffa80`03ecdf80 fffffa80`03ecdf80 fffffa80`06a46190 : 0xfffffa80`00000000
fffff880`0ba28d08 fffff800`02d0a005 : fffffa80`03ecdf80 fffffa80`03ecdf80 fffffa80`06a46190 fffffa80`021dbd50 : win32k+0x184368
fffff880`0ba28d10 fffffa80`03ecdf80 : fffffa80`03ecdf80 fffffa80`06a46190 fffffa80`021dbd50 00000000`00002000 : nt+0xa4005
fffff880`0ba28d18 fffffa80`03ecdf80 : fffffa80`06a46190 fffffa80`021dbd50 00000000`00002000 fffff8a0`01079c68 : 0xfffffa80`03ecdf80
fffff880`0ba28d20 fffffa80`06a46190 : fffffa80`021dbd50 00000000`00002000 fffff8a0`01079c68 ffffffff`ffffffff : 0xfffffa80`03ecdf80
fffff880`0ba28d28 fffffa80`021dbd50 : 00000000`00002000 fffff8a0`01079c68 ffffffff`ffffffff fffffa80`01688dc0 : 0xfffffa80`06a46190
fffff880`0ba28d30 00000000`00002000 : fffff8a0`01079c68 ffffffff`ffffffff fffffa80`01688dc0 00000000`00000000 : 0xfffffa80`021dbd50
fffff880`0ba28d38 fffff8a0`01079c68 : ffffffff`ffffffff fffffa80`01688dc0 00000000`00000000 fffffa80`05da8480 : 0x2000
fffff880`0ba28d40 ffffffff`ffffffff : fffffa80`01688dc0 00000000`00000000 fffffa80`05da8480 fffff880`06be7c00 : 0xfffff8a0`01079c68
fffff880`0ba28d48 fffffa80`01688dc0 : 00000000`00000000 fffffa80`05da8480 fffff880`06be7c00 fffffa80`021dbd50 : 0xffffffff`ffffffff
fffff880`0ba28d50 00000000`00000000 : fffffa80`05da8480 fffff880`06be7c00 fffffa80`021dbd50 fffff8a0`01079c68 : 0xfffffa80`01688dc0


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+184368
fffff960`00204368 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: win32k+184368

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

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


My System SpecsSystem Spec
.
18 Apr 2012   #2
carwiz

Windows 7 Pro-x64
 
 

It helps to follow the directions at the top of the page for "Posting Instructions". Your symbols file(s) are incorrect and don't supply any info for the dumps.

In any case, the problem is a page fault. This could be caused by a memory error or disk drive read error. That would be the places to start. Check with the mfg of the disk drive(s) to see if have a utility to check the drive(s). The disk drive containing your "page file" would be the one to test.
My System SpecsSystem Spec
Reply

 BSOD can't pinpoint what is triggering it




Thread Tools




Similar help and support threads
Thread Forum
BSOD - Hardware error but cannot pinpoint
Hi All. Started having random BSOD after installing new ATI Beta drivers. So, I backed up, and reinstalled windows 7. Same issues occurred: Error is often: STOP code 0x0000001E - Random BSOD, on Starting Windows, or once logged in (the max uptime is about 15 minutes) - Random Windows...
BSOD Help and Support
random bsod can't pinpoint.
i can't seem to find out why it keeps blue screening, ran malwarebytes, hijack this, spybot, updated windows, checked drivers but nothing. any help appreciated. The bugcheck is 0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff88000e5d294)
BSOD Help and Support
BSOD Unable to pinpoint cause
I have run the SF Diagnostic tool and attached the .zip . I've been dealing with 2-3 bsod a day for a few months now. I can go a day without crashing if I'm lucky. The problem is my pc will crash when I'm playing games , but it also has crashed after a fresh start with no programs running...
BSOD Help and Support
Event Triggering in Windows --anybody know how to do it.
Hi all It's AGES and AGES since I did any programming -- but is it possible to run some sort of script / program when say a user defined event occurs. I know most OS'es have some sort of event triggering mechanism but getting at it is the problem. This sort of stuff is second nature in Linux...
General Discussion
BSOD on Win 7 startup- trying to pinpoint cause
Hi guys/girls, I am at my wits end with this thing. I have tried a number of approaches following instructions on the net but unable to pin point the error. I am considering using the tower to practise my shotput. I am in no way an expert but Im not a caveman with a keyboard either. Before...
BSOD Help and Support
BSOD problems...can't pinpoint...help!?
I think it has to do with bad memory or my graphics card. It does it randomly, somtimes just while on the desktop, or in applications. I did update my drivers. Thanks.
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:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App