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

Win764h cannot chkdsk


  • Please log in to reply
12 replies to this topic

#1 Phr3d

Phr3d

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 23 July 2017 - 10:44 PM

Hello, I had a very strange system hang (never had one before) opening a video file, 720p mkv.

I was forced to press the big button as nothing (ctrl-alt-del, for instance) would respond, video file refused to close.

Upon restarting win7 64 home, I immediately scheduled a chkdsk, and after checking the other two volumes, I restart.

Win7 start win colors, switch to chkdsk countdown, then nothing. The "E:" volume light runs a bit, and that is odd, but forced to hard button reset to get going, skip chkdsk at countdown (with wired kbd).

System seems to be running fine, but I've retried 3 times now, no go on "C:" drive chkdsk (Samsung M.2 SSD, magician running).

 

Last Successful chkdsk approx two weeks ago, one program installed since then, now removed.

 

Thanks for your help

 

 


carpe` cervesi
knf


BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:07:32 PM

Posted 23 July 2017 - 11:33 PM

Check your Windows system files with

sfc /scannow

from an elevated command prompt.



#3 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 24 July 2017 - 01:24 PM

Output to txt file, result is:

 

 

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
 

so far so good?


carpe` cervesi
knf


#4 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:07:32 PM

Posted 24 July 2017 - 03:46 PM

We'll try another way then.

 

Tap F8 continuously on reboot to get to advanced boot options, select Repair your Computer and then click Startup Repair from the menu that comes up.

 

Chkdsk is a part of the startup repair process as well as fixing other boot issues.

 

Working now?



#5 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 12 August 2017 - 06:23 PM

I tried with my wireless and couldn't get the 'next' button to work, so set out to find wired kbd/mouse (obviously took a while)

Same result, I am unable to get the first window (country selection) to respond to key or mouse input, nothing.


carpe` cervesi
knf


#6 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:07:32 PM

Posted 12 August 2017 - 08:04 PM

Yeah, you wouldn't expect the wireless mouse to work in that situation.

 

Let's have a look at some other things, see what we can find.

 

acucz8_th.jpgPlease download MiniToolBox, save it to your desktop and run it.

Checkmark the following checkboxes:

  • list IP config
  • list Winsock
  • last 10 events
  • list devices *only problems
  • list users, partitions, memory size

Click Go and note the saved Result.txt on your desktop, to copy into your reply



#7 joseibarra

joseibarra

  • Members
  • 1,240 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:05:32 AM

Posted 15 August 2017 - 04:59 AM

You say:

 

Upon restarting win7 64 home, I immediately scheduled a chkdsk, and after checking the other two volumes, I restart.

 

Was the chkdsk you scheduled a chkdsk with error correction (chkdsk  /r)?

 

What does "after checking the other two volumes" mean?  Checked them how and for what?

 

Does that mean you scheduled a chkdsk with error correction on restart for three volumes at once?

 

Why don't you see if you can clean up any messes by clearing any pending/scheduled chkdsk commands by opening a Command Prompt as Administrator and entering this command:

 

chkntfs  /d

 

Then from a Command Prompt opened as Administrator check the dirty bit on each of your volumes and report the status of each:

 

 

To query the dirty bit on drive C, in the Command Prompt window enter the following command:

fsutil  dirty  query  C:

 

 

Sample output should be one or the other of:

 

Volume C: is dirty
Volume C is NOT dirty

You should check each of your volumes or each of your hard drives (C, D, E, etc.).

Enter 'exit' to close the Command Prompt window.

 

Report back the dirty but status on each of your volumes.


Edited by joseibarra, 15 August 2017 - 05:00 AM.

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#8 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:07:32 PM

Posted 15 August 2017 - 07:04 AM

Please download MiniToolBox, save it to your desktop and run it.

Checkmark the following checkboxes:

  • list IP config
  • list Winsock
  • last 10 events
  • list devices *only problems
  • list users, partitions, memory size

Click Go and note the saved Result.txt on your desktop, to copy into your reply



#9 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 17 August 2017 - 10:26 PM

Hiya,

 

----------

No dirty bits on C: D: E:

----------

 

 

Here is the MTB return (I removed the USB drives from list)

 

begin:

MiniToolBox by Farbar  Version: 17-06-2016
Ran by knf (administrator) on 17-08-2017 at 22:11:11
Running from "C:\handbrake\T"
Microsoft Windows 7 Home Premium   (X64)
Model: D54250WY Manufacturer: INTEL_
Boot Mode: Normal
***************************************************************************

========================= Flush DNS: ===================================

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.
========================= IP Configuration: ================================

Intel® Ethernet Connection I218-V = Local Area Connection (Connected)
Bluetooth Device (Personal Area Network) = Bluetooth Network Connection 3 (Hardware not present)


# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset
set global icmpredirects=enabled


popd
# End of IPv4 configuration



Windows IP Configuration

   Host Name . . . . . . . . . . . . : NUC-i5
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel® Ethernet Connection I218-V
   Physical Address. . . . . . . . . : C0-3F-D5-6D-77-EC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2604:2d80:4038:cbe3:d82f:7d7b:d875:794c(Preferred)
   Temporary IPv6 Address. . . . . . : 2604:2d80:4038:cbe3:8834:3d1f:111f:9c49(Preferred)
   Link-local IPv6 Address . . . . . : fe80::d82f:7d7b:d875:794c%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.21(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, August 15, 2017 3:28:20 PM
   Lease Expires . . . . . . . . . . : Friday, August 18, 2017 3:28:32 PM
   Default Gateway . . . . . . . . . : fe80::b27f:b9ff:fe73:7bb2%14
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 297811925
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-67-8F-52-C0-3F-D5-6D-77-EC
   DNS Servers . . . . . . . . . . . : 2607:fdc8:800::11
                                       2607:fdc8:1400::12
                                       97.64.168.12
                                       97.64.183.165
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{235846F3-F798-4B57-B20B-1686F81B1C0B}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Server:  UnKnown
Address:  2607:fdc8:800::11

Name:    google.com
Addresses:  2607:f8b0:4009:812::200e
      172.217.6.110


Pinging google.com [2607:f8b0:4009:80d::200e] with 32 bytes of data:
Reply from 2607:f8b0:4009:80d::200e: time=27ms
Reply from 2607:f8b0:4009:80d::200e: time=29ms

Ping statistics for 2607:f8b0:4009:80d::200e:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 29ms, Average = 28ms
Server:  UnKnown
Address:  2607:fdc8:800::11

Name:    yahoo.com
Addresses:  2001:4998:44:204::a7
      2001:4998:c:a06::2:4008
      2001:4998:58:c02::a9
      98.138.253.109
      98.139.180.149
      206.190.36.45


Pinging yahoo.com [2001:4998:44:204::a7] with 32 bytes of data:
Reply from 2001:4998:44:204::a7: time=45ms
Reply from 2001:4998:44:204::a7: time=72ms

Ping statistics for 2001:4998:44:204::a7:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 72ms, Average = 58ms

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
 14...c0 3f d5 6d 77 ec ......Intel® Ethernet Connection I218-V
  1...........................Software Loopback Interface 1
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.21     10
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.0.0    255.255.255.0         On-link      192.168.0.21    266
     192.168.0.21  255.255.255.255         On-link      192.168.0.21    266
    192.168.0.255  255.255.255.255         On-link      192.168.0.21    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.0.21    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.0.21    266
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 14    266 ::/0                     fe80::b27f:b9ff:fe73:7bb2
  1    306 ::1/128                  On-link
 14     18 2604:2d80:4038:cbe3::/64 On-link
 14    266 2604:2d80:4038:cbe3:8834:3d1f:111f:9c49/128
                                    On-link
 14    266 2604:2d80:4038:cbe3:d82f:7d7b:d875:794c/128
                                    On-link
 14    266 fe80::/64                On-link
 14    266 fe80::d82f:7d7b:d875:794c/128
                                    On-link
  1    306 ff00::/8                 On-link
 14    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [51712] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\winrnr.dll [20992] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\napinsp.dll [52224] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 07 C:\Windows\SysWOW64\wshbth.dll [35840] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 11 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [70144] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\winrnr.dll [28672] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\napinsp.dll [68096] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 07 C:\Windows\System32\wshbth.dll [46592] (Microsoft Corporation)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 11 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)

========================= Event log errors: ===============================

Application errors:
==================
Error: (08/17/2017 07:22:23 PM) (Source: Application Error) (User: )
Description: Faulting application name: firefox.exe, version: 55.0.2.6435, time stamp: 0x5991c363
Faulting module name: xul.dll, version: 55.0.2.6435, time stamp: 0x5991c7a5
Exception code: 0x80000003
Fault offset: 0x00893bf0
Faulting process id: 0x1d80
Faulting application start time: 0xfirefox.exe0
Faulting application path: firefox.exe1
Faulting module path: firefox.exe2
Report Id: firefox.exe3

Error: (08/17/2017 07:22:19 PM) (Source: Application Error) (User: )
Description: Windows cannot access the file  for one of the following reasons:
there is a problem with the network connection, the disk that the file is stored on, or the storage
drivers installed on this computer; or the disk is missing.
Windows closed the program Firefox because of this error.

Program: Firefox
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again.
This situation might be a temporary problem that corrects itself when the program runs again.
2.
If the file still cannot be accessed and
    - It is on the network,
your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for
further assistance.

Additional Data
Error value: C000026E
Disk type: 0

Error: (08/17/2017 07:22:19 PM) (Source: Application Error) (User: )
Description: Faulting application name: firefox.exe, version: 55.0.2.6435, time stamp: 0x5991c363
Faulting module name: xul.dll, version: 55.0.2.6435, time stamp: 0x5991c7a5
Exception code: 0xc0000006
Fault offset: 0x00223a24
Faulting process id: 0x1e60
Faulting application start time: 0xfirefox.exe0
Faulting application path: firefox.exe1
Faulting module path: firefox.exe2
Report Id: firefox.exe3

Error: (08/12/2017 11:30:02 PM) (Source: Application Error) (User: )
Description: Faulting application name: NETGEARGenie.exe, version: 2.4.1.0, time stamp: 0x00030000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x3d736e00
Faulting process id: 0xb6c
Faulting application start time: 0xNETGEARGenie.exe0
Faulting application path: NETGEARGenie.exe1
Faulting module path: NETGEARGenie.exe2
Report Id: NETGEARGenie.exe3

Error: (08/12/2017 05:40:46 PM) (Source: System Restore) (User: )
Description: The restore point selected was damaged or deleted during the restore (Windows Update).

Error: (08/10/2017 07:16:58 PM) (Source: Application Hang) (User: )
Description: The program mpc-hc64.exe version 1.7.11.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 37fc

Start Time: 01d30e700d560fbd

Termination Time: 56

Application Path: C:\Program Files\MPC-HC\mpc-hc64.exe

Report Id: 60c0301d-7e2a-11e7-a9a2-c03fd56d77ec

Error: (08/09/2017 03:03:57 AM) (Source: Application Hang) (User: )
Description: The program seamonkey.exe version 49.0.2.6191 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 2790

Start Time: 01d310b3e3852e7a

Termination Time: 58

Application Path: C:\Program Files (x86)\SeaMonkey\seamonkey.exe

Report Id: 4321d842-7cd9-11e7-a9a2-c03fd56d77ec

Error: (07/24/2017 04:52:59 AM) (Source: Application Error) (User: )
Description: Faulting application name: NETGEARGenie.exe, version: 2.4.1.0, time stamp: 0x00030000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00002f65
Faulting process id: 0xbe4
Faulting application start time: 0xNETGEARGenie.exe0
Faulting application path: NETGEARGenie.exe1
Faulting module path: NETGEARGenie.exe2
Report Id: NETGEARGenie.exe3

Error: (07/23/2017 09:15:28 PM) (Source: System Restore) (User: )
Description: The restore point selected was damaged or deleted during the restore (Windows Update).

Error: (07/19/2017 05:37:51 AM) (Source: Application Error) (User: )
Description: Faulting application name: NETGEARGenie.exe, version: 2.4.1.0, time stamp: 0x00030000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x88130a04
Faulting process id: 0x3b70
Faulting application start time: 0xNETGEARGenie.exe0
Faulting application path: NETGEARGenie.exe1
Faulting module path: NETGEARGenie.exe2
Report Id: NETGEARGenie.exe3


System errors:
=============
Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.

Error: (08/17/2017 05:36:19 PM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk4\DR4.


Microsoft Office Sessions:
=========================
Error: (08/17/2017 07:22:23 PM) (Source: Application Error)(User: )
Description: firefox.exe55.0.2.64355991c363xul.dll55.0.2.64355991c7a58000000300893bf01d8001d31767b12813d0D:\Program Files (x86)\Mozilla Firefox\firefox.exeD:\Program Files (x86)\Mozilla Firefox\xul.dll4db1ce87-83ab-11e7-abcc-c03fd56d77ec

Error: (08/17/2017 07:22:19 PM) (Source: Application Error)(User: )
Description: FirefoxC000026E0

Error: (08/17/2017 07:22:19 PM) (Source: Application Error)(User: )
Description: firefox.exe55.0.2.64355991c363xul.dll55.0.2.64355991c7a5c000000600223a241e6001d31767af460651D:\Program Files (x86)\Mozilla Firefox\firefox.exeD:\Program Files (x86)\Mozilla Firefox\xul.dll4b693588-83ab-11e7-abcc-c03fd56d77ec

Error: (08/12/2017 11:30:02 PM) (Source: Application Error)(User: )
Description: NETGEARGenie.exe2.4.1.000030000unknown0.0.0.000000000c00000053d736e00b6c01d313bd6e15d79fC:\Program Files (x86)\NETGEAR Genie\bin\NETGEARGenie.exeunknown122e6728-7fe0-11e7-abcc-c03fd56d77ec

Error: (08/12/2017 05:40:46 PM) (Source: System Restore)(User: )
Description: Windows Update

Error: (08/10/2017 07:16:58 PM) (Source: Application Hang)(User: )
Description: mpc-hc64.exe1.7.11.037fc01d30e700d560fbd56C:\Program Files\MPC-HC\mpc-hc64.exe60c0301d-7e2a-11e7-a9a2-c03fd56d77ec

Error: (08/09/2017 03:03:57 AM) (Source: Application Hang)(User: )
Description: seamonkey.exe49.0.2.6191279001d310b3e3852e7a58C:\Program Files (x86)\SeaMonkey\seamonkey.exe4321d842-7cd9-11e7-a9a2-c03fd56d77ec

Error: (07/24/2017 04:52:59 AM) (Source: Application Error)(User: )
Description: NETGEARGenie.exe2.4.1.000030000unknown0.0.0.000000000c000000500002f65be401d30425c9c984fdC:\Program Files (x86)\NETGEAR Genie\bin\NETGEARGenie.exeunknowndfc50a4a-7055-11e7-a9a2-c03fd56d77ec

Error: (07/23/2017 09:15:28 PM) (Source: System Restore)(User: )
Description: Windows Update

Error: (07/19/2017 05:37:51 AM) (Source: Application Error)(User: )
Description: NETGEARGenie.exe2.4.1.000030000unknown0.0.0.000000000c000000588130a043b7001d3003edeade95dC:\Program Files (x86)\NETGEAR Genie\bin\NETGEARGenie.exeunknown506f5dac-6c6e-11e7-ad00-c03fd56d77ec


========================= Devices: ================================

Name: Motorola USB Device
Description: Motorola USB Device
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Manufacturer: Motorola
Service: motusbdevice
Device ID: USB\VID_0000&PID_0000\7&2534B3E7&0&2
Problem: : This device is disabled because the firmware of the device did not give it the required resources. (Code 29)
Resolution: Enable the device in the BIOS of the device.

Name: Bluetooth Device (Personal Area Network) #3
Description: Bluetooth Device (Personal Area Network)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: BthPan
Device ID: BTH\MS_BTHPAN\6&21BE6E0C&1&2
Problem: : This device is disabled. (Code 22)
Resolution: In Device Manager, click "Action", and then click "Enable Device". This starts the Enable Device wizard. Follow the instructions.

Name: Bluetooth Peripheral Device
Description: Bluetooth Peripheral Device
Class Guid:
Manufacturer:
Service:
Device ID: BTHENUM\{00001131-0000-1000-8000-00805F9B34FB}_VID&0001000F_PID&0000\7&B1360D2&0&1C965AF9BEC0_C00000000
Problem: : The drivers for this device are not installed. (Code 28)
Resolution: To install the drivers for this device, click "Update Driver", which starts the Hardware Update wizard.


========================= Memory info: ===================================

Percentage of memory in use: 53%
Total physical RAM: 15832.11 MB
Available physical RAM: 7301.46 MB
Total Virtual: 17878.25 MB
Available Virtual: 8574.12 MB

========================= Partitions: =====================================

1 Drive c: (TEK_SYS_764) (Fixed) (Total:209.37 GB) (Free:70.49 GB) NTFS
2 Drive d: (RAID_10_1) (Fixed) (Total:7451.81 GB) (Free:803.56 GB) NTFS
3 Drive e: (RAID_10_2) (Fixed) (Total:7451.81 GB) (Free:287.45 GB) NTFS



========================= Users: ========================================

User accounts for \\NUC-I5

Administrator            Guest                    knf                      


**** End of log ****
 

:end

 

Bluetooth error (I believe) is my headset that win7-64h doesn't like.

The HD error was apparently caused by overheating of the 3rd-of-4 disks in a pack, temp back below 50C, problem has not recurred.

 

Thank You!

P


Edited by Phr3d, 17 August 2017 - 10:28 PM.

carpe` cervesi
knf


#10 joseibarra

joseibarra

  • Members
  • 1,240 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:05:32 AM

Posted 18 August 2017 - 01:21 AM

I asked for several pieces of information and only got back some information and looking at the original post I'm not even sure what the problem is anymore,

 

So I'm going into lurking mode on this one.


The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#11 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 18 August 2017 - 03:24 PM

@joseibarra,

I was confused as well, but completed your instructions confirming no dirty bits, however I could have answered the questions directly (you seemed to have answered them, I was mistaken):

 

Upon restarting win7 64 home, I immediately scheduled a chkdsk, and after checking the other two volumes, I restart.

 

"Was the chkdsk you scheduled a chkdsk with error correction (chkdsk  /r)?"

-- yes

 

"What does "after checking the other two volumes" mean?  Checked them how and for what?"

-- The RAID volumes do not need to be dismounted. I am effectively checking ALL volumes after a BSOD, then restarting to Complete the 'scheduled" chkdsk /r of the C: volume, which then hangs after the countdown - I must push the power button long to turn off.

 

"Does that mean you scheduled a chkdsk with error correction on restart for three volumes at once?"

-- No

 

"Why don't you see if you can clean up any messes by clearing any pending/scheduled chkdsk commands by opening a Command Prompt as Administrator and entering this command:

 

chkntfs  /d "

 

-- Done

 

"Then from a Command Prompt opened as Administrator check the dirty bit on each of your volumes and report the status of each:"

 

-- Done x3, reports no dirty bits

 

Hope this was clearer,

Thanks!

P


carpe` cervesi
knf


#12 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 26 August 2017 - 11:52 AM

finally back:

 

hmm, there was a reply, now missing.

 

command above (the now MIA post), elev command prompt,

 

command:

 

C:\Windows\System32>reg   query   "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\C
ontrol\Session Manager"   /v   BootExecute

returns:

    BootExecute    REG_EXPAND_SZ    autocheck autochk /K:CDEFGHIJKLMNOPQRSTUVWXY
Z *

 

P


Edited by Phr3d, 26 August 2017 - 11:52 AM.

carpe` cervesi
knf


#13 Phr3d

Phr3d
  • Topic Starter

  • Members
  • 54 posts
  • OFFLINE
  •  
  • Location:midwest
  • Local time:04:32 AM

Posted 06 September 2017 - 06:56 PM

Try once more:

 

When I try to do a chkdsk on my OS drive, C:, and schedule, I restart win764 hp, it does the standard countdown to 0 to begin the scheduled chkdsk, but then hangs there, refusing to respond to input or move to the chkdsk phase. When I press the on/off button, and hard shut down, then turn back on, Windows comes up normally, but obviously not having done a chkdsk on my (NVM,Samsung) system drive.

 

Any help appreciated.


carpe` cervesi
knf





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users