Issue While Playing Wow

I was wondering if anyone could help me. I have been having this issue for a few days but its getting worst. While playing wow the game sound crashes makes a beeping crazy sound. Then the game crashes/pc. and the screen goes blank. Then I get a message saying "No Signal"

It doesn't always happen that way. This current crash, the screen went blank and then got the no signal. I looked at event view and had to errors:

Source : Application:
Faulting application name: IAStorDataMgrSvc.exe, version: 11.6.0.1030, time stamp: 0x5042b0f0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x05574bf5
Faulting process id: 0x1cdc
Faulting application start time: 0x01d30768542726d0
Faulting application path: C:\Program Files (x86)\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
Faulting module path: unknown
Report Id: ffca3dff-0c81-4a58-a12b-253d0cfd3cf5
Faulting package full name:
Faulting package-relative application ID:

Source: JNET Runtime :
Application: IAStorDataMgrSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at IAStorUtil.SystemDataModelListener.ProcessSystemDataModelChanges()
at IAStorUtil.SystemDataModelListener.LoadSavedSystemState()
at IAStorDataMgr.EventRelay.<Start>b__0(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Not sure if this helps, hope it does. Any help would be appreciated.

Thank you.

 

Best guess from the IAStorDataMgrSvc, you are looking at a failure quite soon. Look to replace your drives.

 

1.What OS are you using?
2.What is the brand name of the system drive?
3.Are the crashes only happening, when running WOW?
"No Signal" makes me think unexpected power shutdown.
4.Does Event Id 41 show up in the viewer?

Do a physical cleanup of the machine; i.e. eliminate "dust bunnies" and clear the vents, etc. Make things cool.

Check system file integrity. Boot into safe mode with networking, download and run Tweaking.com - Windows Repair
http://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html
Familiarize yourself with its "Help" items. Do steps 1 thru 4. Don't do repairs at this time. Reboot into normal windows after step 4.
Are there any new IAStor errors in the viewer now?

Download and run Speccy to check and monitor system operating temperatures, especially cpu and gpu. http://www.majorgeeks.com/files/details/speccy.html
Post a screenshot here of the summary page.

Make sure your system is malware free. Start a thread in the Malware Help (specialist) forum, by carefully following the "Read & Run Me First" guide. http://forums.majorgeeks.com/index.php?forums/malware-help-mg-a-specialist-will-reply.35/
Tell them you need a check before doing system repairs.

After the specialists give you a clean bill of health for malware, go back to safe mode and rerun the Tweaking Repair all steps,
including "Repairs."

The idea here is to provide us more information, eliminate over heating as an issue, eliminate malware as an issue, and to correct system file issues. If you can do that, then the focus can move on to a specific devices, such as graphics card or drives, and power supply. Let us know how things are progressing.

 

1.What OS are you using?
- Windows 10
- OS Build 15063.483

2.What is the brand name of the system drive?
Not sure what that means?

- But this is a Lenovo erazer x700

3.Are the crashes only happening, when running WOW?
- Yes they are only happening on wow
"No Signal" makes me think unexpected power shutdown.
- it happened again, it said no signal and then a few seconds later it was on again but no sound.

4.Does Event Id 41 show up in the viewer?
Where do I look for this, sorry I'm not to tech savvy with it comes to terms and where to look.

The stuff I posted i got from applications, when i click on systems I see this:

The Intel(R) Rapid Storage Technology service terminated unexpectedly. It has done this 1 time(s).

In applicatiosn this is there:
Faulting application name: IAStorDataMgrSvc.exe, version: 11.6.0.1030, time stamp: 0x5042b0f0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x05864bf5
Faulting process id: 0x35d0
Faulting application start time: 0x01d30bc8e21f3882
Faulting application path: C:\Program Files (x86)\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
Faulting module path: unknown
Report Id: 4e504d39-87f7-415e-b65b-665ccd0dcfde
Faulting package full name:
Faulting package-relative application ID:

Also I updated my drivers using Drive booster which I got on here. Since every time I tried to manually do it it says my drivers are current but the Drive Booster found a lot of out ones. The only thing I didnt undate was the intel processor one. Cause its giving a different name and wasnt sure if its the right one. My current processor says Intel(R) Core(TM) i& - 3930k and the one that driver booster is saying is Intel(R) Xeno(R) Processor E5 product family/Core i7 since Im not sure I just didnt update it cause its like 48 updates with the same name..

 

So after I do steps 1 to 4 I run wow and see if it crashes again?

 

Did the step 2 the scan results said this:
┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair 2018 (v4.0.1) - Pre-Scan
│ Computer: NITROMUSPRIME (Windows 10 Home 10.0.15063.483 ) (64-bit)
│ [Started Scan - 8/3/2017 1:54:10 AM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (8/3/2017 1:54:10 AM)
│
│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)
C:\WINDOWS\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
│
1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
│ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
│
│ THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.
│
│ Files Checked & Verified: 4,302
│
│ Done Scanning Windows Packages Files.(8/3/2017 1:58:27 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (8/3/2017 1:58:27 AM)
│
│ Reparse Points are OK!.
│
│ Files & Folders Searched: 340,354
│ Reparse Points Found: 113
│
│ Done Scanning Reparse Points.(8/3/2017 1:58:54 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (8/3/2017 1:58:54 AM)
│
│ This folder in the 'Path' variable doesn't exist: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static
│
│ This folder in the 'Path' variable doesn't exist: C:\Program Files (x86)\AMD\ATI.ACE\Core-Static
│
│ Problems were found with the Environment Variables.
│ You can use the Repair Environment Variables Tool at the bottom of this Window to try and fix these problems.
│
│ Done Checking Environment Variables. (8/3/2017 1:58:54 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 8/3/2017 1:58:54 AM]
│
│ [x] Scan Complete - Problems Found!
│ [x]
│ [x] You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.
│ [x]
│ [x] While problems have been found, you can still run the repairs in the program.
│ [x] But for the best results it is recommended to fix the problems reported in this scan if possible.
└────────────────────────────────────────────────────────────────────────────────┘


Do I do the repairs point and environment var it is saying to do?

 

I did the environment var repair thing. When to step 3 and this is the report:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\John\Desktop>CD /D C:\

C:\>set path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SystemRoot%\System32\WindowsPowerShell\v1.0

C:\>chkdsk C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is Windows8_OS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
Progress: 505856 of 505856 done; Stage: 100%; Total: 35%; ETA: 0:00:14 .


505856 file records processed.

File verification completed.
Progress: 13827 of 13827 done; Stage: 100%; Total: 28%; ETA: 0:00:19 ..


13827 large file records processed.

Progress: 0 of 0 done; Stage: 99%; Total: 28%; ETA: 0:00:19 ...


0 bad file records processed.


Stage 2: Examining file name linkage ...
Progress: 599704 of 599704 done; Stage: 100%; Total: 81%; ETA: 0:00:06


599704 index entries processed.

Index verification completed.
Progress: 1 of 0 done; Stage: 99%; Total: 81%; ETA: 0:00:06 .
Progress: 0 of 0 done; Stage: 99%; Total: 81%; ETA: 0:00:06 ..


0 unindexed files scanned.

Progress: 0 of 0 done; Stage: 99%; Total: 81%; ETA: 0:00:06 ...


0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Progress: 5 of 5 done; Stage: 100%; Total: 99%; ETA: 0:00:00


46925 data files processed.

CHKDSK is verifying Usn Journal...
Progress: 4372 of 4372 done; Stage: 100%; Total: 95%; ETA: 0:00:00 ..


35817296 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

122280959 KB total disk space.
99811636 KB in 256053 files.
156420 KB in 46926 indexes.
0 KB in bad sectors.
622827 KB in use by the system.
65536 KB occupied by the log file.
21690076 KB available on disk.

4096 bytes in each allocation unit.
30570239 total allocation units on disk.
5422519 allocation units available on disk.

C:\>

So on the main UI is says no error found on this drive. I also have a D drive I'll check that one as well and then move on to the next step

Edit: Doesnt seem to have a way to check D. but from reading help seems I dont need to

 

did steps 1 thru 4, did see some errors not the one you asked about but these are there: ( side note: I ran wow and it didn't crash)

1.
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

2.
Activation context generation failed for "C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Microsoft Office\root\Office16\UccApi.DLL" on line 1. Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="16.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="16.0.0.0". Please use sxstrace.exe for detailed diagnosis.

3.

Activation context generation failed for "d:\composite2014\python\lib\distutils\command\wininst-8_d.exe". Dependent Assembly Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

4.

Product: Akamai NetSession Interface -- Error 1310. Error writing to file: C:\Users\John\AppData\Local\Akamai\admintool.exe. System error 0. Verify that you have access to that directory.

#4 appeared twice.


Gonna do the malware steps next.

 

Tried running WoW this morning and it crashed again. The game flickered to a black screen, it came back then the whole screen turned black after a few seconds. Had to restart the whole pc again.

Got these errors in event viewer:

1.The ScRegSetValueExW call failed for FailureActions with the following error:
Access is denied.

2.The Intel(R) Rapid Storage Technology service terminated unexpectedly. It has done this 1 time(s).

 

Hi John, thank you for reporting your process. I will try to catch up here with your questions.

Post #4 Your system drive, usually C:, is where Windows files reside to enable the Windows system to operate. When you did Tweaking step 4, it had no test for D: because no system files reside on it.

Regarding Event viewer, here is a handy tutorial by Woody
http://www.dummies.com/computers/operating-systems/windows-10/how-to-use-event-viewer-in-windows-10/

Caution, don't get too excited about anything that shows up here. Many things shown, will come and go after reboots. Some things are acceptable or not worth troubleshooting. Usually you want to watch for Critical items, repeating every start.

Event 41 is a Critical and indicates an abnormal system shutdown and a good time to run Tweaking steps 3 and 4 to check and repair system drive/file integrity.

Rather than give a long description in these threads, unless asked to, please just report the ID number and name for the event as shown in Woody's example: Event Id, CAPI2.

Drivers: for now, don't do any more driver updating. I'll say more next post.

 

Drivers cont: Here is a quote from plodr, an esteemed MG helper ... "if it ain't broke, don't fix it.
Very rarely do I EVER update a driver!"
This is in another thread on this site and when plodr speaks, most of us pay attention.

Many of us here won't even allow Windows to update drivers.
3rd party driver programs aren't always accurate and can cause problems with their updates. Their fixing can break your system.
If you use one of these programs, make sure you have a complete rollback/backup capability. Likely, you will need to pay for these features.

Many of us start looking for driver updates from the machine source, in your case, Lenovo. Otherwise check the device manufacture's site for specific devices.

Please don't do any more fixing on your own until we get through the whole process I outlined in post #3.

When you first run the programs needed for the Malware (specialist) forum, make sure you don't clean or delete anything, but just obtain and post the required logs. The specialists will tell you when and what to delete after they analyze the logs.

 

Post #6 Correcting reparse and environmental errors was good.

Post #7 System drive integrity, step 3, looks good at this point.
You didn't post what result you got from step 4, System file check.
Please provide it the next time its run. Rerunning these two steps is a good thing to do after each time your system crashes.

Post #8 Temps look normal, but keep on eye on gpu temp when doing heavy graphics activity.

Post #9 You can keep testing WOW if you want, but I don't expect the crashes to go away. We really haven't repaired anything, yet.