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


  • Please log in to reply
1 reply to this topic

#1 blocka

blocka

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Local time:08:45 AM

Posted 09 March 2017 - 01:14 AM

Attached files for Irql not less or equal  problem attached.

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:15 PM

Posted 09 March 2017 - 09:47 AM

3: kd> .bugcheck
Bugcheck code 0000000A
Arguments ffffbe0b`7300a8d8 00000000`00000002 00000000`00000001 fffff803`6dc7e590
*** WARNING: Unable to verify timestamp for GUBootStartup.sys
*** ERROR: Module load completed but symbols could not be loaded for GUBootStartup.sys
Probably caused by : GUBootStartup.sys ( GUBootStartup+1103 )
ffff8380`9d9108a0  fffff808`370d3150Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0xd3150
ffff8380`9d910958  fffff808`37a96482Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
 aswSP+0x16482
3: kd> lmvm GUBootStartup; lmvm aswSnx; lmvm aswSP
start             end                 module name
fffff808`378b0000 fffff808`378b9000   GUBootStartup T (no symbols)           
    Loaded symbol image file: GUBootStartup.sys
    Image path: \??\C:\Windows\System32\drivers\GUBootStartup.sys
    Image name: GUBootStartup.sys
    Timestamp:        Sun Jun 22 22:56:24 2014 (53A79758)
    CheckSum:         0000A768
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
start             end                 module name
fffff808`37000000 fffff808`370f2000   aswSnx   T (no symbols)           
    Loaded symbol image file: aswSnx.sys
    Image path: \SystemRoot\system32\drivers\aswSnx.sys
    Image name: aswSnx.sys
    Timestamp:        Fri Feb 24 01:41:55 2017 (58AFD5B3)
    CheckSum:         000F83F2
    ImageSize:        000F2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
start             end                 module name
fffff808`37a80000 fffff808`37b29000   aswSP    T (no symbols)           
    Loaded symbol image file: aswSP.sys
    Image path: \SystemRoot\system32\drivers\aswSP.sys
    Image name: aswSP.sys
    Timestamp:        Fri Feb 24 01:50:31 2017 (58AFD7B7)
    CheckSum:         00089F33
    ImageSize:        000A9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL bugcheck blaming a Glary Utilities Startup Manager Tool driver. Please uninstall any GlarySoft programs you have. Digging into the raw stack, we see several avast! drivers. ONLY if issues persist AFTER uninstalling Glary Utilities, uninstall avast!, run their cleaning tool, and use Windows Defender for protection temporarily.

 

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users