Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD after waking PC from sleep


  • Please log in to reply
No replies to this topic

#1 eliasgusta

eliasgusta

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:32 AM

Posted 04 May 2018 - 12:00 PM

going to follow these steps, scanned with malwarebytes https://i.imgur.com/WiSSUCh.png
hopefully this will have fixed it, i don't overclock, psu is ok i had it checked twice last month and mem sticks are new
these seem to be the typical causes although since mine only did it after waking PC from sleep it does seem weird
(overclocking, incorrect voltages, incorrect BIOS settings, memory failure)
 
i normally put PC to sleep, never shut down and last week i had a BSOD after waking PC from sleep
didn't think much of it, i pretty much let it run for about 5 days in a row without sleep or turning it off
never had any errors otherwise, running games etc... everything works normal 
today same error after waking PC up again. so i wanted to see what's up
 
system specs: win 7 ultimate SP1

PSU                 Corsair CP-9020048, CX 600W

MOBO             Gigabyte Z77-D3H, socket 1155

CPU                 Intel Core i5 3570 ivy bridge socket 1155 LGA

RAM                Dual Channel Corsair 32GB (4 x 8GB), DDR3, 1600MHz (CL11)

GPU                Radeon R9 270x

 
i had 8gb of ram before, which never caused any issues and since ram is only thing i upgraded i feel it might be the culprit
it's pretty strange tho, this error only appearing after waking PC up from sleep mode so hopefully some of you gurus can help me out
 
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
 
Additional information about the problem:
  BCCode: 1000007e
  BCP1: FFFFFFFFC0000005
  BCP2: FFFFF8800F934030
  BCP3: FFFFF880009EB548
  BCP4: FFFFF880009EADA0
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1
 
i attached the file, some of this is pasted from windbg. googled some of it, no idea what to make of it
is this an error caused by windbg not being able to read the symbol?
 
Symbol search path is: srv*
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23455.amd64fre.win7sp1_ldr.160516-0600
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`0305b730
Debug session time: Sat Apr 21 11:20:07.667 2018 (UTC + 3:00)
System Uptime: 3 days 9:33:12.683
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
...............
 
************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified
 
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000007E, {ffffffffc0000005, fffff8800f90b030, fffff880009e4548, fffff880009e3da0}
 
***** 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************

Edited by eliasgusta, 04 May 2018 - 01:44 PM.


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users