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 after working 3 weeks and crash

14 Jan 2014   #1
kamili23

win 7 professional x64
 
 
BSOD after working 3 weeks and crash

I got this bsod when notebook works for 3 weeks, and crash. And so on..


Quote:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\011414-8252-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305d6d0
Debug session time: Tue Jan 14 07:30:57.938 2014 (UTC + 1:00)
System Uptime: 11 days 14:07:55.676
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88007a1f2ce, fffff8800c9e9b80, 0}

Unable to load image ks.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ks.sys ( ks+1f2ce )

Followup: MachineOwner



My System SpecsSystem Spec
.
14 Jan 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

My System SpecsSystem Spec
15 Jan 2014   #3
kamili23

win 7 professional x64
 
 

I posted it but it was in polish so you know. :P

Anyway posted.
My System SpecsSystem Spec
.

15 Jan 2014   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_15-01-2014\011414-8252-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305d6d0
Debug session time: Tue Jan 14 12:30:57.938 2014 (UTC + 6:00)
System Uptime: 11 days 14:07:55.676
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88007a1f2ce, fffff8800c9e9b80, 0}

*** WARNING: Unable to verify timestamp for AtihdW76.sys
*** ERROR: Module load completed but symbols could not be loaded for AtihdW76.sys
Probably caused by : ks.sys ( ks!KspPinPropertyHandler+17a )

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

1: kd> lmvm AtihdW76
start             end                 module name
fffff880`07815000 fffff880`07831000   AtihdW76 T (no symbols)           
    Loaded symbol image file: AtihdW76.sys
    Image path: AtihdW76.sys
    Image name: AtihdW76.sys
    Timestamp:        Sat Jul 06 00:10:37 2013 (51D70C1D)
    CheckSum:         0001AA85
    ImageSize:        0001C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
the HD audio driver AtihdW76.sys is an element of Catalyst. It will be a good first attempt to update the display driver to the latest.

Download Drivers

Code:
fffff880`07013000 fffff880`070b1000   atikmpag   (deferred)             
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sun Sep 29 09:54:58 2013 (5247AB9A)
    CheckSum:         0009EF9D
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
16 Jan 2014   #5
kamili23

win 7 professional x64
 
 

I done this since they show out. So I'm up to date with driver display.
My System SpecsSystem Spec
17 Jan 2014   #6
kamili23

win 7 professional x64
 
 

Today same got same bsod.
My System SpecsSystem Spec
17 Jan 2014   #7
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Upload SF log.
My System SpecsSystem Spec
17 Jan 2014   #8
kamili23

win 7 professional x64
 
 

Here you go.
My System SpecsSystem Spec
Reply

 BSOD after working 3 weeks and crash




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Various BSOD over the last few weeks
Hi I have always had BSOD at various time and varying degrees happening one a week to once a month. Recently I have started to get BSOD every morning sometime as many as 3 then the system mostly runs without an issue. When the BSOD occur I could be browsing the internet, looking through...
BSOD Help and Support
Windows display manager stopped working+firefox crash+BSOD
Please help! ill make post quick before this crashes again. It started with random freezes, then it escalated to display manager crashes+firefox crashes, and now they are just random BSOD (around 5 minutes after starting the computer) Dump files coming next post Have tried updating...
BSOD Help and Support
Custom PC, Working several weeks, Sudden BSOD on any game
"STOP: 0X0000007E" Just built a new PC only a couple weeks ago. I don't have much on it, simply because I wish to use it as a gaming rig. The two programs I use most often is FF14 and SWTOR. Initial problem (which may be the root): When I got my disc for the OS, I got it through a discount...
BSOD Help and Support
explorer.exe Crash (not working), sometimes lead to bsod
Hello guys, Recently I encountered many times of this error, I wasn't doing a lot of work with my PC thought expect playing games. My system specs: OS win 7 home premium 64bit CPU Amd Phenom X4 955 BE Motherboard msi870A-G54 Memory Team Xtreme Dark 2x2GB Graphics Card Digital...
BSOD Help and Support
System crash at night every other night past 2 weeks
Not EXACTLY every other night, but it seems that way. This is my office machine, Dell Studio XPS 8100, purchased October 2010: - Win7 x64 Pro - Core i7 Quad 870 2.93 GHz - 12 GB DDR3 SDRAM - ATI Radeon HD 5770 1GB This is in an office with a Server 2003 machine as the domain controller,...
BSOD Help and Support
6 BSoD's in 2 weeks
I've had a BSoD 6 times since I upgraded to 7 about 2 weeks ago. Each time it has happened while browsing the internet so I would almost assume it had something to do with either the browser or the wireless drivers. but I could be wrong. Also I'd really like to learn how to diagnose and treat this...
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 03:18.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App