Computer Dead Locking

Toggle sidebar Toggle sidebar
FlashGuard

FlashGuard

Reputable
Mar 22, 2017
47
0
4,530
CPU: AMD FX - 8350 4.0Ghz
3 Month Old Custom Build


Heatsink: Cool Master 212x

GPU: Nvidia GeForce 1060 sc acx 2.0 3gb

MOBO: M5A97 R2.0

RAM: 16GB DDR3 G skill 340pin 1600

PSU: EVGA 80 plus 600w

the case has 5x 120mm fans in it

COOLING IS NOT AN ISSUE

My system is not overheating.
There are no RAM errors
The HDD shows no errors in scf "Windows Resource Protection did not find any integrity violations."

I did a clean install about 4 days ago. Not freezing in gaming just randomly.

All the drivers have been updated. I installed the Nvidia and MOBO Site drivers.

The keyboard is not responding while it locks.

i work from home so i cannot afford the system freezing a lot :c


Current Errors EVENT VIEWER

--------------------------------------------------------------------------------------------
System

- Provider

[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager

- EventID 7023

[ Qualifiers] 49152

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated

[ SystemTime] 2017-05-09T22:37:56.367570200Z

EventRecordID 1427

Correlation

- Execution

[ ProcessID] 860
[ ThreadID] 2272

Channel System

Computer

Security


- EventData

param1 Connected Devices Platform Service
param2 %%2147500037
4300440050005300760063000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00440043 00530050 00630076 0000


In Bytes

0000: 43 00 44 00 50 00 53 00 C.D.P.S.
0008: 76 00 63 00 00 00 v.c...
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

- System

- Provider

[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM

- EventID 10010

[ Qualifiers] 0

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated

[ SystemTime] 2017-05-09T22:40:47.729646000Z

EventRecordID 1429

Correlation

- Execution

[ ProcessID] 108
[ ThreadID] 1816

Channel System

Computer

- Security

[ UserID] S-1-5-21-463010648-1299404987-4269536756-1001


- EventData

param1 {37998346-3765-45B1-8C66-AA88CA6B20B8}

-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------

- System

- Provider

[ Name] hcmon

- EventID 0

[ Qualifiers] 32768

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2017-05-09T22:34:52.924004100Z

EventRecordID 1420

Channel System

Computer

Security


- EventData

\Device\hcmon
\Driver\pci
00000000020028000000000000000080000000000000000000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00000000 00280002 00000000 80000000
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000


In Bytes

0000: 00 00 00 00 02 00 28 00 ......(.
0008: 00 00 00 00 00 00 00 80 .......€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

------------------------------------------------------------------------------
------------------------------------------------------------------------------

- System

- Provider

[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}

EventID 19

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2017-05-09T18:06:10.217299300Z

EventRecordID 1248

- Correlation

[ ActivityID] {9BD2A6A7-2E8A-49CA-8EE1-5170C66B67E8}

- Execution

[ ProcessID] 1544
[ ThreadID] 8300

Channel System

Computer

- Security

[ UserID] S-1-5-19


- EventData

ErrorSource 1
ApicId 0
MCABank 1
MciStat 0x8c00002000010151
MciAddr 0x13fa543
MciMisc 0xc00a0fff00000000
ErrorType 9
TransactionType 0
Participation 256
RequestType 5
MemorIO 256
MemHierarchyLvl 1
Timeout 256
OperationType 256
Channel 256
Length 928
RawData 435045521002FFFFFFFF03000200000002000000A003000009061200090511140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89074F7FDCF76C7D20100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010300010000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000200F6000000808000B32983EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0054000000000043A53F010000000000000000000000000000000000000000000000000000000001000000020000002BD065EFEEC8D201000000000000000000000000000000000000000001000000510101002000008C43A53F010000000000000000FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000


-------------------------------------------------------------------------------
 
Sort by date Sort by votes



there is no BSOD so there are no errors logged. Event Viewer shows only error codes
19 WHEA-Logger
7023 Service Control Manager
10016 DistributedCOM
0 hcmon
 
Upvote 0 Downvote


temps have not changed since i made the rig. Nor has this issue stated before. This is the first issue.

MOBO 31 C
CPU 39 C
GPU 52 C

ALL THE HARDWARE IS NEW. Never had temp issues or overheating of any kind. Video card was OC'd for about a week but then i stopped. I have since ran it at stock.
 
Upvote 0 Downvote
Looking at the services my DISK was at 99% consistently. I disabled the program "razor cortex" and then disabled Superfetch.msc. Then i ran in admin CMD "Dism /Online /Cleanup-Image /RestoreHealth".

This was found here

http://www.tomshardware.com/forum/id-2791310/service-host-local-system-high-memory-usage.html

I will get back and see if this issue is fixed. Its odd though. since ive been running Cortex the whole time i have had this pc.

--------------------------------------------------------------------------------------------------

I used Bluescreenviewer after using windows Verifer. it found that there where two issues,

ntoskrnl.exe

Which was caused by YSDrv.sys From what i can gather it was from Vmware Horison. I think maybe it installed incorrectly or it was not the actual install. So i uninstalled it and deleted that sys file.

I also backed up my video driver. Which caused some issue with my last post.

so now time will tell.
 
Upvote 0 Downvote
sfc /scannow just checks system files, if the freezing was caused by hdd you should have run chkdsk instead.

that evil ntoskrnl again, if only it was useful... oh wait, it stands for new technology operating system kernel... guess it might do something useful after all... like run windows. It gets blamed for so many errors.
 
Upvote 0 Downvote


well if found the issue YSDrv.sys

However now im getting yet ANOTHER issue. A BSOD WHEA. which is usually CPU i take it right? Well i just updated all Drivers. Hell i even went into Bios to change the settings for the CPU so its set for "Thermal Operation" and not Auto Voltage change. So now it is set to run without TURBO. Also let me point out that this CPU IS 3 MONTHS OLD and has NEVER been OVERCLOCKED. Ive been running it STOCK

 
Upvote 0 Downvote
WHEA are usually CPU as you say but can be other things as well

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote
is it a coincidence how many people have had WHEA errors using the same motherboard ? i know it's a popular mobo but i seem to see threads with multitude of problems and the common factor is this motherboard . i'm not saying it's your motherboard btw but i'm not saying it isn't either .. just asking a question
 
Upvote 0 Downvote


maybe it is. But the brand is supposed to be good quality. Nextime im going with MSI :c
 
Upvote 0 Downvote
Might just be the model as every Asus motherboard I have used has been fine. I think my last 4 computers had Asus motherboards, that is going back 16 years

YSDrv.sys - BigNox VM VirtualBox might be VboxUSB

Have you recently connected a mobile phone or used android games to run virtually on your windows pc?
VboxUSB would work similar to an emulator.
Click to expand...

https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/What-is-this-program/td-p/3390057

i know you ran bluescreenview but this just puts it in a different structure - Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do :)

if you create the minidumps like I asked for above we might figure out whea errors, they might not be the CPU
 
Upvote 0 Downvote
not disputing the quality of Asus. i could be wrong but i thought i would say something because it might be worth researching and seeing if there is a problem relating to this model and that a fix is already out there .
 
Upvote 0 Downvote


I do same if I see someone buying something I have seen problems with before :)
 
Upvote 1 Downvote


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 5/9/2017 9:24:59 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-16015-01.dmp
This was probably caused by the following module: ysdrv.sys (YSDrv+0x216E3)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF801CA7B16E3, 0x0, 0x54525049)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ysdrv.sys .
Google query: ysdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 5/9/2017 9:24:59 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ysdrv.sys (YSDrv!RTAssertMsg2+0xFA3)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF801CA7B16E3, 0x0, 0x54525049)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ysdrv.sys .
Google query: ysdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION
 
Upvote 0 Downvote


i turned off OC settings and turbo in BIOS and it didnt crash at all yesterday. now its up to its crap again.



On Thu 5/11/2017 1:28:13 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051117-12906-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3627F)
Bugcheck code: 0x124 (0x0, 0xFFFFD889E72F0028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 5/11/2017 1:28:13 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFD889E72F0028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 5/9/2017 9:24:59 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-16015-01.dmp
This was probably caused by the following module: ysdrv.sys (YSDrv+0x216E3)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF801CA7B16E3, 0x0, 0x54525049)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ysdrv.sys .
Google query: ysdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION


I am starting to think that its my MOBO. back when i first built this ASUS suite kept saying i have a Temp Error. With all settings normal. Now i uninstalled all ASUS programs when i clean booted my PC a while ago. now changing the BIOs seems to be working. But it cannot be on optimized defaults


File System Filter 'wcifs' (Version 10.0, ‎2016‎-‎09‎-‎15T12:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy1'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.

also have this now

So i contacted ASUS and AMD. ASUS advied to rotate my ram from The A slots to B slots and clear CMOS to see if the RAM or BIOs is causing the issue. AMD has not gotten back to me Yet. Also i am Running Windows Repair because i can.

So lets add that to the pile of things done so far
 
Upvote 0 Downvote
UPDATE:

One of your restore points are bad. What I did to fix this do the following

Open command prompt in administrator mode by type CMD in the search box, right click CMD program and open as administrator
2. Type this command vssadmin delete shadows /for=c: /all and hit enter
3. Choose Y on the confirmation and hit enter. A message will display showing how many VSS copies deleted.

After that go into system restore create a new restore point as your old ones will be deleted & no more problems.

Found this here

https://www.tenforums.com/general-support/78177-warning-about-file-system-filter-wcifs-what.html

may have fixed it


nope no fix
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom