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

random hangs even after reset


  • Please log in to reply
6 replies to this topic

#1 twists

twists

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:16 AM

Posted 23 November 2016 - 08:42 AM

Laptop: Acer S3-392G with Windows 10.

I’ve been struggling with random hangs (complete freezes with audio buzzing) for a while now, and eventually resorted to a complete reset of my laptop. However, the resets have still continued. I realise that this might just be a hardware issue but I’d really like to explore every avenue before I cave in and buy a new hard drive/laptop/whatever.

 

Interesting things:

  • Current drivers have been installed using a combination of Snappy Driver and Windows Update.

  • dism /online /cleanup-image /restorehealth and sfc /scannow have both been run.

  • There are no hangs when in safe mode which suggests to me it's a driver problem?

  • Driver verifier with the suggested settings doesn’t pick up anything. Driver verifier with the settings suggested by Microsoft picks up a DRIVER_VERIFIER_DETECTED_VIOLATION with ISCTD64.sys - Intel Smart Connect. Any attempt to uninstall smart connect from device manager --> system devices just leads to it reappearing at the next restart. I would deactivate it from the BIOS but the insyde h20 bios is locked from advanced settings!

  • Event Viewer has no interesting errors apart from several Event ID 37 - Kernel-Processor-Power and Event ID 219 - The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\3&11583659&0. Some googling has brought up ACPI\ACPI0008\ as something to do with the light sensor, but I’m not sure what to do with this information.

  • Before my reset, I would occasionally get WHEA_UNCORRECTABLE_ERROR bsods but the laptop would hang/freeze before any BSOD info could be collected. Also DRIVER IRQL_LESS_OR_NOT_EQUAL for netwbw02.sys, I think?

 
 
any suggestions would be hugely appreciated :)

Edited by twists, 23 November 2016 - 08:46 AM.


BC AdBot (Login to Remove)

 


#2 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 23 November 2016 - 08:44 AM

 

Laptop: Acer S3-392G with Windows 10.

I’ve been struggling with random hangs (complete freezes with audio buzzing) for a while now, and eventually resorted to a complete reset of my laptop. However, the resets have still continued. I realise that this might just be a hardware issue but I’d really like to explore every avenue before I cave in and buy a new hard drive/laptop/whatever.

 

Interesting things:

  • Current drivers have been installed using a combination of Snappy Driver and Windows Update.

  • There are no hangs when in safe mode which suggests to me it's a driver problem?

  • Driver verifier with the suggested settings doesn’t pick up anything. Driver verifier with the settings suggested by Microsoft picks up ISCTD64.sys - Intel Smart Connect. Any attempt to uninstall smart connect from device manager --> system devices just leads to it reappearing at the next restart. I would deactivate it from the BIOS but the insyde h20 bios is locked from advanced settings!

  • Event Viewer has no interesting errors apart from several Event ID 37 - Kernel-Processor-Power and Event ID 219 - The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\3&11583659&0. Some googling has brought up ACPI\ACPI0008\ as something to do with the light sensor, but I’m not sure what to do with this information.

  • Before my reset, I would occasionally get WHEA_UNCORRECTABLE_ERROR bsods but the laptop would hang/freeze before any BSOD info could be collected. Also DRIVER IRQL_LESS_OR_NOT_EQUAL for netwbw02.sys, I think?

 
 
any suggestions would be hugely appreciated :)

 

Hi,

You want to upload the BSOD dump here so that we can analyze what's the cause.

Please also run Mini-Toolbox (Link: http://www.bleepingcomputer.com/download/minitoolbox/ ) and attach the report here.

Thanks.



#3 twists

twists
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:16 AM

Posted 23 November 2016 - 11:44 AM

 

 

Laptop: Acer S3-392G with Windows 10.

I’ve been struggling with random hangs (complete freezes with audio buzzing) for a while now, and eventually resorted to a complete reset of my laptop. However, the resets have still continued. I realise that this might just be a hardware issue but I’d really like to explore every avenue before I cave in and buy a new hard drive/laptop/whatever.

 

Interesting things:

  • Current drivers have been installed using a combination of Snappy Driver and Windows Update.

  • There are no hangs when in safe mode which suggests to me it's a driver problem?

  • Driver verifier with the suggested settings doesn’t pick up anything. Driver verifier with the settings suggested by Microsoft picks up ISCTD64.sys - Intel Smart Connect. Any attempt to uninstall smart connect from device manager --> system devices just leads to it reappearing at the next restart. I would deactivate it from the BIOS but the insyde h20 bios is locked from advanced settings!

  • Event Viewer has no interesting errors apart from several Event ID 37 - Kernel-Processor-Power and Event ID 219 - The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\3&11583659&0. Some googling has brought up ACPI\ACPI0008\ as something to do with the light sensor, but I’m not sure what to do with this information.

  • Before my reset, I would occasionally get WHEA_UNCORRECTABLE_ERROR bsods but the laptop would hang/freeze before any BSOD info could be collected. Also DRIVER IRQL_LESS_OR_NOT_EQUAL for netwbw02.sys, I think?

 
 
any suggestions would be hugely appreciated :)

 

Hi,

You want to upload the BSOD dump here so that we can analyze what's the cause.

Please also run Mini-Toolbox (Link: http://www.bleepingcomputer.com/download/minitoolbox/ ) and attach the report here.

Thanks.

 

Can you expand on what you mean by run Mini-Toolbox? Which options do I tick?

 

I've attached the minidump zip with 2 dump files.

Attached Files



#4 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 23 November 2016 - 11:59 PM

 

 

 

Laptop: Acer S3-392G with Windows 10.

I’ve been struggling with random hangs (complete freezes with audio buzzing) for a while now, and eventually resorted to a complete reset of my laptop. However, the resets have still continued. I realise that this might just be a hardware issue but I’d really like to explore every avenue before I cave in and buy a new hard drive/laptop/whatever.

 

Interesting things:

  • Current drivers have been installed using a combination of Snappy Driver and Windows Update.

  • There are no hangs when in safe mode which suggests to me it's a driver problem?

  • Driver verifier with the suggested settings doesn’t pick up anything. Driver verifier with the settings suggested by Microsoft picks up ISCTD64.sys - Intel Smart Connect. Any attempt to uninstall smart connect from device manager --> system devices just leads to it reappearing at the next restart. I would deactivate it from the BIOS but the insyde h20 bios is locked from advanced settings!

  • Event Viewer has no interesting errors apart from several Event ID 37 - Kernel-Processor-Power and Event ID 219 - The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\3&11583659&0. Some googling has brought up ACPI\ACPI0008\ as something to do with the light sensor, but I’m not sure what to do with this information.

  • Before my reset, I would occasionally get WHEA_UNCORRECTABLE_ERROR bsods but the laptop would hang/freeze before any BSOD info could be collected. Also DRIVER IRQL_LESS_OR_NOT_EQUAL for netwbw02.sys, I think?

 
 
any suggestions would be hugely appreciated :)

 

Hi,

You want to upload the BSOD dump here so that we can analyze what's the cause.

Please also run Mini-Toolbox (Link: http://www.bleepingcomputer.com/download/minitoolbox/ ) and attach the report here.

Thanks.

 

Can you expand on what you mean by run Mini-Toolbox? Which options do I tick?

 

I've attached the minidump zip with 2 dump files.

 

Hi,
 

Kindly check for the following:
 
- List last 10 Event Viewer Errors
- List Installed Programs
- List all
- List Minidump Files.

Thanks.


#5 twists

twists
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:16 AM

Posted 24 November 2016 - 05:16 AM

 

 

 

 

Laptop: Acer S3-392G with Windows 10.

I’ve been struggling with random hangs (complete freezes with audio buzzing) for a while now, and eventually resorted to a complete reset of my laptop. However, the resets have still continued. I realise that this might just be a hardware issue but I’d really like to explore every avenue before I cave in and buy a new hard drive/laptop/whatever.

 

Interesting things:

  • Current drivers have been installed using a combination of Snappy Driver and Windows Update.

  • There are no hangs when in safe mode which suggests to me it's a driver problem?

  • Driver verifier with the suggested settings doesn’t pick up anything. Driver verifier with the settings suggested by Microsoft picks up ISCTD64.sys - Intel Smart Connect. Any attempt to uninstall smart connect from device manager --> system devices just leads to it reappearing at the next restart. I would deactivate it from the BIOS but the insyde h20 bios is locked from advanced settings!

  • Event Viewer has no interesting errors apart from several Event ID 37 - Kernel-Processor-Power and Event ID 219 - The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\3&11583659&0. Some googling has brought up ACPI\ACPI0008\ as something to do with the light sensor, but I’m not sure what to do with this information.

  • Before my reset, I would occasionally get WHEA_UNCORRECTABLE_ERROR bsods but the laptop would hang/freeze before any BSOD info could be collected. Also DRIVER IRQL_LESS_OR_NOT_EQUAL for netwbw02.sys, I think?

 
 
any suggestions would be hugely appreciated :)

 

Hi,

You want to upload the BSOD dump here so that we can analyze what's the cause.

Please also run Mini-Toolbox (Link: http://www.bleepingcomputer.com/download/minitoolbox/ ) and attach the report here.

Thanks.

 

Can you expand on what you mean by run Mini-Toolbox? Which options do I tick?

 

I've attached the minidump zip with 2 dump files.

 

Hi,
 

Kindly check for the following:
 
- List last 10 Event Viewer Errors
- List Installed Programs
- List all
- List Minidump Files.

Thanks.

 

attached!

Attached Files

  • Attached File  MTB.txt   37.36KB   2 downloads


#6 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 24 November 2016 - 07:59 AM

Hi,

Hope this helps to unlock the insyde bios, so that you can disable it. (Link : https://713itsupport.com/blog/2012/01/how-to-remove-a-bios-password-from-an-insyde-h2o-efi-bios-updated/ )

Your BSOD report shows that you are on the right track :
 

 
Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\JinXiang\Downloads\minidump\112116-21515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff800`9f81f000 PsLoadedModuleList = 0xfffff800`9fb24060
Debug session time: Mon Nov 21 21:16:05.022 2016 (UTC + 8:00)
System Uptime: 0 days 0:00:09.046
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck C4, {2000, fffff80b415d9154, 0, 54435349}
 
*** WARNING: Unable to verify timestamp for ISCTD64.sys
*** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys
Probably caused by : ISCTD64.sys ( ISCTD64+9154 )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, subclass of driver violation.
Arg2: fffff80b415d9154
Arg3: 0000000000000000
Arg4: 0000000054435349
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0xc4_2000
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff8009ff2b360 to fffff8009f969510
 
STACK_TEXT:  
ffff9400`a3ec61f8 fffff800`9ff2b360 : 00000000`000000c4 00000000`00002000 fffff80b`415d9154 00000000`00000000 : nt!KeBugCheckEx
ffff9400`a3ec6200 fffff800`9fa3df0b : ffffbc83`2b1fe330 fffff800`9ff23482 fffff800`9ff1d8a0 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x48
ffff9400`a3ec6240 fffff800`9ff23370 : 00000000`54435349 fffff800`9fb16820 fffff80b`415d9154 ffff9400`a3ec6460 : nt!VfReportIssueWithOptions+0x103
ffff9400`a3ec6290 fffff800`9ff21355 : 00000000`54435349 ffff9400`a3ec6460 00000000`00000000 00000000`001c001a : nt!VfCheckPoolType+0x90
ffff9400`a3ec62d0 fffff80b`415d9154 : 00000000`00000000 ffffbc83`2b5978c0 ffffbc83`2b5f0034 fffff80b`415de073 : nt!VerifierExAllocatePoolEx+0x21
ffff9400`a3ec6310 00000000`00000000 : ffffbc83`2b5978c0 ffffbc83`2b5f0034 fffff80b`415de073 00000000`00000000 : ISCTD64+0x9154
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
ISCTD64+9154
fffff80b`415d9154 488905cd200000  mov     qword ptr [ISCTD64+0xb228 (fffff80b`415db228)],rax
 
SYMBOL_STACK_INDEX:  5
 
SYMBOL_NAME:  ISCTD64+9154
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: ISCTD64
 
IMAGE_NAME:  ISCTD64.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  50b51a02
 
FAILURE_BUCKET_ID:  0xc4_2000_VRF_ISCTD64+9154
 
BUCKET_ID:  0xc4_2000_VRF_ISCTD64+9154
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0xc4_2000_vrf_isctd64+9154
 
FAILURE_ID_HASH:  {24c30a79-4d83-26c6-3572-0cca8782e76f}
 
Followup: MachineOwner
---------
 
3: kd> lmvm ISCTD64
start             end                 module name
fffff80b`415d0000 fffff80b`415e1000   ISCTD64  T (no symbols)           
    Loaded symbol image file: ISCTD64.sys
    Image path: \SystemRoot\System32\drivers\ISCTD64.sys
    Image name: ISCTD64.sys
    Timestamp:        Wed Nov 28 03:52:34 2012 (50B51A02)
    CheckSum:         0000CC32
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
-----------------------------------------------------------------------------------------------------------------------------------------------------------

Please revert if it's not working.

Thanks.


#7 twists

twists
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:16 AM

Posted 24 November 2016 - 08:50 PM

 

Hi,

Hope this helps to unlock the insyde bios, so that you can disable it. (Link : https://713itsupport.com/blog/2012/01/how-to-remove-a-bios-password-from-an-insyde-h2o-efi-bios-updated/ )

Your BSOD report shows that you are on the right track :
 

 
Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\JinXiang\Downloads\minidump\112116-21515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff800`9f81f000 PsLoadedModuleList = 0xfffff800`9fb24060
Debug session time: Mon Nov 21 21:16:05.022 2016 (UTC + 8:00)
System Uptime: 0 days 0:00:09.046
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck C4, {2000, fffff80b415d9154, 0, 54435349}
 
*** WARNING: Unable to verify timestamp for ISCTD64.sys
*** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys
Probably caused by : ISCTD64.sys ( ISCTD64+9154 )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, subclass of driver violation.
Arg2: fffff80b415d9154
Arg3: 0000000000000000
Arg4: 0000000054435349
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0xc4_2000
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff8009ff2b360 to fffff8009f969510
 
STACK_TEXT:  
ffff9400`a3ec61f8 fffff800`9ff2b360 : 00000000`000000c4 00000000`00002000 fffff80b`415d9154 00000000`00000000 : nt!KeBugCheckEx
ffff9400`a3ec6200 fffff800`9fa3df0b : ffffbc83`2b1fe330 fffff800`9ff23482 fffff800`9ff1d8a0 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x48
ffff9400`a3ec6240 fffff800`9ff23370 : 00000000`54435349 fffff800`9fb16820 fffff80b`415d9154 ffff9400`a3ec6460 : nt!VfReportIssueWithOptions+0x103
ffff9400`a3ec6290 fffff800`9ff21355 : 00000000`54435349 ffff9400`a3ec6460 00000000`00000000 00000000`001c001a : nt!VfCheckPoolType+0x90
ffff9400`a3ec62d0 fffff80b`415d9154 : 00000000`00000000 ffffbc83`2b5978c0 ffffbc83`2b5f0034 fffff80b`415de073 : nt!VerifierExAllocatePoolEx+0x21
ffff9400`a3ec6310 00000000`00000000 : ffffbc83`2b5978c0 ffffbc83`2b5f0034 fffff80b`415de073 00000000`00000000 : ISCTD64+0x9154
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
ISCTD64+9154
fffff80b`415d9154 488905cd200000  mov     qword ptr [ISCTD64+0xb228 (fffff80b`415db228)],rax
 
SYMBOL_STACK_INDEX:  5
 
SYMBOL_NAME:  ISCTD64+9154
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: ISCTD64
 
IMAGE_NAME:  ISCTD64.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  50b51a02
 
FAILURE_BUCKET_ID:  0xc4_2000_VRF_ISCTD64+9154
 
BUCKET_ID:  0xc4_2000_VRF_ISCTD64+9154
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0xc4_2000_vrf_isctd64+9154
 
FAILURE_ID_HASH:  {24c30a79-4d83-26c6-3572-0cca8782e76f}
 
Followup: MachineOwner
---------
 
3: kd> lmvm ISCTD64
start             end                 module name
fffff80b`415d0000 fffff80b`415e1000   ISCTD64  T (no symbols)           
    Loaded symbol image file: ISCTD64.sys
    Image path: \SystemRoot\System32\drivers\ISCTD64.sys
    Image name: ISCTD64.sys
    Timestamp:        Wed Nov 28 03:52:34 2012 (50B51A02)
    CheckSum:         0000CC32
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
-----------------------------------------------------------------------------------------------------------------------------------------------------------

Please revert if it's not working.

Thanks.

 

I've followed the method in the link, but sadly that would only work if there was a password on my bios. I think the core difficulty is that the UEFI only has certain areas available for the user to choose from, and the main way to access the other (advanced) areas is by flashing the BIOS was another unofficial version. thanks for the help anyway! I'll have a dig around on google and see if I can find anything.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users