Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 3, 2017 18:47:35 GMT -5
At times I am seeing a blue screen with this error - THREAD STUCK IN DEVICE DRIVER. I have peeked in the device manager, but I don't see anything flagged. Any help would be appreciated.  |
|
|
|
Post by jholland1964 on Aug 3, 2017 19:13:55 GMT -5
Pretty much device on the computer can experience this error but solutions for each are different so we need a lot more information. Exactly what are you doing when this blue screen happens? We need to know the full wording of the error, including the error number
|
|
billm65
Member
Posts: 30 
World Start Name: billm65
|
Post by billm65 on Aug 3, 2017 19:48:42 GMT -5
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 3, 2017 19:54:11 GMT -5
Thank you both! I'll have to wait to post a screen shot of the error message as it's on someone else's phone. Hopefully they will return shortly.
|
|
|
|
Post by jholland1964 on Aug 3, 2017 21:26:53 GMT -5
Thank you both! I'll have to wait to post a screen shot of the error message as it's on someone else's phone. Hopefully they will return shortly. This screen shot must be 100% visible, very clear and fully readable. It is preferred that instead of screen shot that you transcribe the full error if possible and post it here. Also, the link given by bill65 is similar to yours but please remember, in that particular thread the poster's problem was caused by the video driver but don't assume that is what is causing yours. This error can occur with a problem with ANY piece of hardware, not only the video driver. I have found other posts at Microsoft and other forums where the problem has been caused by sound cards, overheating, power supply and other items. So in order to help determine which one is causing yours then you absolutely must tell us exactly what you are doing, programs being used, etc. when these blue screens occur and the complete text in the errors shown on the blue screen. |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 0:29:30 GMT -5
Looks like it won't be tonight. I'll try again tomorrow.
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 0:35:20 GMT -5
Judy, it never has happened with me - but, rather with my daughter who plays "Star Stable". I mentioned to her that it probably had something to do with the game, but she said that it had happened another time - but, I just don't know for sure. You mentioned about overheating which this computer just came back from being repaired and the problem was the fans. It is now moved to a cooler room and is turned off a lot, so hopefully that will help. I can't make the error message come up on its own, so I'll have to wait to see how good the screen shot is.
|
|
|
|
Post by jholland1964 on Aug 4, 2017 8:23:22 GMT -5
Judy, it never has happened with me - but, rather with my daughter who plays "Star Stable". I mentioned to her that it probably had something to do with the game, but she said that it had happened another time - but, I just don't know for sure. You mentioned about overheating which this computer just came back from being repaired and the problem was the fans. It is now moved to a cooler room and is turned off a lot, so hopefully that will help. I can't make the error message come up on its own, so I'll have to wait to see how good the screen shot is. Since this happens while playing a game then it may very well be the video card, but we definitely cannot know for sure until we can read the ALL of the error message. You said you cannot make the error come up yourself, are you attempting to get it the same way....playing the game? In order to try to duplicate an error like this then the only way to do this is you have to do exactly what was being done at the time of the error, not another game either, you must be playing the exact same game. If needed sit with her while your daughter plays the game to be sure it is also being played the same way. If the blue screen happens then do not take another picture, write down the error in full, top to bottom including the error number, that also is vital. Again I say, do not post a screen shot especially ones taken on a phone of a blue screen error on a computer screen, are very, very difficult to read when posted on a forum like this one. I would ask that you read the screen shot yourself and transcribe it in full here as a post. IMPORTANT - Did these blue screens happen BEFORE the repairs or after? |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 13:01:53 GMT -5
Judy, she's not here now but, I believe she said it had also happened one time before the repairs. I'll ask her again tonight. Also, I'll have her play the game tonight and see if we can duplicate the error message.
|
|
|
|
Post by jholland1964 on Aug 4, 2017 13:29:46 GMT -5
Judy, she's not here now but, I believe she said it had also happened one time before the repairs. I'll ask her again tonight. Also, I'll have her play the game tonight and see if we can duplicate the error message. If it also happened before the fans were repaired then that rules out that one thing, overheating, meaning at that time there was another problem besides overheating. So put that thought aside as it is not the cause of the blue screen. Yes, do have her try to duplicate the blue screen and please do not take a picture, please write down everything shown on the blue screen. Until then you can try looking in the Event Viewer. Go to the Control Panel, Administrative Tools, Event Viewer. Open it, open the Windows Logs section, Open the System logs and an error event in the System log section might be able to tell you which hardware driver crashed, which can help you a bad or out of date driver or a faulty hardware component. You may see items with a yellow triangle that says Warning. That is Not what you need to investigate. The ones you need to look at, that happened around or on the date that you know for sure when the Blue Screen occurred and these would be a Red Circle with an Exclamation point in the middle of it. Double click on one of them and you can see the properties of this Error. There is a copy button on the left side of these boxes when they open. Copy it and then paste it here. If there are numerous ones, read through them but don't copy paste them all. If they are all for the same thing then copy/paste ONE of them here. If there are multiple errors noted for different things pick the exact date of the last Blue Screen and copy/paste one of them but give us a list of the others. |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:16:51 GMT -5
Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 8/4/2017 9:24:55 PM Event ID: 10010 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Asus Description: The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10010</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-08-05T01:24:55.151013900Z" /> <EventRecordID>7516</EventRecordID> <Correlation /> <Execution ProcessID="532" ThreadID="1380" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">{784E29F4-5EBE-4279-9948-1E8FE941646D}</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:19:19 GMT -5
Log Name: System Source: Service Control Manager Date: 8/4/2017 9:21:50 PM Event ID: 7000 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Asus Description: The CldFlt service failed to start due to the following error: The request is not supported. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7000</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-08-05T01:21:50.046538400Z" /> <EventRecordID>7491</EventRecordID> <Correlation /> <Execution ProcessID="808" ThreadID="964" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security /> </System> <EventData> <Data Name="param1">CldFlt</Data> <Data Name="param2">%%50</Data> <Binary>43006C00640046006C0074000000</Binary> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:22:02 GMT -5
I noticed on this one - no one was playing the Star Stable game. Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 8/4/2017 7:16:08 PM Event ID: 10016 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Asus Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10016</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-08-04T23:16:08.687542900Z" /> <EventRecordID>7436</EventRecordID> <Correlation /> <Execution ProcessID="532" ThreadID="8640" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">application-specific</Data> <Data Name="param2">Local</Data> <Data Name="param3">Activation</Data> <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data> <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data> <Data Name="param6">NT AUTHORITY</Data> <Data Name="param7">SYSTEM</Data> <Data Name="param8">S-1-5-18</Data> <Data Name="param9">LocalHost (Using LRPC)</Data> <Data Name="param10">Unavailable</Data> <Data Name="param11">Unavailable</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:22:56 GMT -5
Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 8/4/2017 12:10:21 PM Event ID: 10010 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Asus Description: The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10010</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-08-04T16:10:21.920388400Z" /> <EventRecordID>7425</EventRecordID> <Correlation /> <Execution ProcessID="532" ThreadID="104" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">{784E29F4-5EBE-4279-9948-1E8FE941646D}</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:23:44 GMT -5
Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 8/4/2017 12:07:21 PM Event ID: 10016 Task Category: None Level: Error Keywords: Classic User: LOCAL SERVICE Computer: Asus Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10016</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-08-04T16:07:21.755424500Z" /> <EventRecordID>7422</EventRecordID> <Correlation /> <Execution ProcessID="532" ThreadID="104" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="param1">application-specific</Data> <Data Name="param2">Local</Data> <Data Name="param3">Activation</Data> <Data Name="param4">{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}</Data> <Data Name="param5">{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}</Data> <Data Name="param6">NT AUTHORITY</Data> <Data Name="param7">LOCAL SERVICE</Data> <Data Name="param8">S-1-5-19</Data> <Data Name="param9">LocalHost (Using LRPC)</Data> <Data Name="param10">Unavailable</Data> <Data Name="param11">Unavailable</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:29:16 GMT -5
Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 8/1/2017 11:57:13 PM Event ID: 1001 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Asus Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ea (0xffffe785e7c9d080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 95a7ce55-e49d-4495-88f2-cc5163a139f9. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-08-02T03:57:13.486040500Z" /> <EventRecordID>7043</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security /> </System> <EventData> <Data Name="param1">0x000000ea (0xffffe785e7c9d080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)</Data> <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data> <Data Name="param3">95a7ce55-e49d-4495-88f2-cc5163a139f9</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:33:19 GMT -5
Log Name: System Source: Service Control Manager Date: 7/30/2017 11:56:46 PM Event ID: 7011 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Asus Description: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SCardSvr service. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7011</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-07-31T03:56:46.175012300Z" /> <EventRecordID>6853</EventRecordID> <Correlation /> <Execution ProcessID="808" ThreadID="3612" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security /> </System> <EventData> <Data Name="param1">30000</Data> <Data Name="param2">SCardSvr</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:34:21 GMT -5
Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 7/30/2017 11:56:43 PM Event ID: 10005 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Asus Description: DCOM got error "1070" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {784E29F4-5EBE-4279-9948-1E8FE941646D} Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10005</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-07-31T03:56:43.583766500Z" /> <EventRecordID>6851</EventRecordID> <Correlation /> <Execution ProcessID="364" ThreadID="12176" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">1070</Data> <Data Name="param2">wuauserv</Data> <Data Name="param3">Unavailable</Data> <Data Name="param4">{784E29F4-5EBE-4279-9948-1E8FE941646D}</Data> </EventData> </Event> |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:34:43 GMT -5
Log Name: System Source: Service Control Manager Date: 7/30/2017 11:56:41 PM Event ID: 7022 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Asus Description: The Windows Update service hung on starting. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7022</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-07-31T03:56:41.525087400Z" /> <EventRecordID>6850</EventRecordID> <Correlation /> <Execution ProcessID="808" ThreadID="960" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security /> </System> <EventData> <Data Name="param1">Windows Update</Data> <Binary>770075006100750073006500720076000000</Binary> </EventData> </Event> |
|
|
|
Post by jholland1964 on Aug 4, 2017 21:37:35 GMT -5
Linda I asked for ONE log, why have you posted 9 of them? Please, please, please stop.
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:39:32 GMT -5
Judy, there are a ton of the ones I posted above. I also saw some regarding unexpected shutdowns. That is when we had some power outages.
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:40:18 GMT -5
Sorry, Judy - the ones above were all different and I didn't know which one might be important.
|
|
|
|
Post by jholland1964 on Aug 4, 2017 21:46:50 GMT -5
When you saw so many different errors in such a short time instead of posting any logs you should instead have reported there were "tons" of them. I would have told you instead to take the computer back to the repair shop. There should not be so many errors on a newly repaired computer. There shouldn't really be any errors at all.
Power outages would not be considered because those were not computer caused. If the power goes out then the computer will shut down, that would not be unexpected.
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:47:27 GMT -5
Here is what was on the blue screen from July 27th. Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you. 100% complete For more information about this issue and possible fixes visit www.windows.com/stopcode If you call a support person give them this info: Thread stuck in device driver |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:51:56 GMT -5
When you saw so many different errors in such a short time instead of posting any logs you should instead have reported there were "tons" of them. I would have told you instead to take the computer back to the repair shop. There should not be so many errors on a newly repaired computer. There shouldn't really be any errors at all. Power outages would not be considered because those were not computer caused. If the power goes out then the computer will shut down, that would not be unexpected. It seems the errors have been going on before there was a fan problem. |
|
|
|
Post by jholland1964 on Aug 4, 2017 21:54:15 GMT -5
Here is what was on the blue screen from July 27th. Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you. 100% complete For more information about this issue and possible fixes visit www.windows.com/stopcode If you call a support person give them this info: Thread stuck in device driver Then why didn't you post the log from July 27th? It is not one of the nine that you have posted. 5 of them were from tonight, one of them was from the 1st and 3 of them were from the 30th. Multiple causes for them also. |
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 21:59:56 GMT -5
Here is what was on the blue screen from July 27th. Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you. 100% complete For more information about this issue and possible fixes visit www.windows.com/stopcode If you call a support person give them this info: Thread stuck in device driver Then why didn't you post the log from July 27th? It is not one of the nine that you have posted. 5 of them were from tonight, one of them was from the 1st and 3 of them were from the 30th. Multiple causes for them also. Because you told me to stop. There are more than one for July 27th - but, here is one: Log Name: System Source: Service Control Manager Date: 7/27/2017 10:56:44 PM Event ID: 7000 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Asus Description: The CldFlt service failed to start due to the following error: The request is not supported. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7000</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-07-28T02:56:44.839884400Z" /> <EventRecordID>6438</EventRecordID> <Correlation /> <Execution ProcessID="804" ThreadID="1340" /> <Channel>System</Channel> <Computer>Asus</Computer> <Security /> </System> <EventData> <Data Name="param1">CldFlt</Data> <Data Name="param2">%%50</Data> <Binary>43006C00640046006C0074000000</Binary> </EventData> </Event> |
|
|
|
Post by jholland1964 on Aug 4, 2017 22:06:32 GMT -5
Linda, it is time to take this computer back to the shop. There are just too many errors with too many things to be able to narrow all of them down and fix them all yourself or through this forum. I am sorry. You need to point out all of these errors to the tech and tell him about all of the blue screens and errors that happened before you had it in there for the fan problem and show them the errors have continued since the fan repair. There is more wrong with the computer than a fan problem.
|
|
Linda
Member
"Possum's friend"
Posts: 39
Former World Start Member: Yes
|
Post by Linda on Aug 4, 2017 22:10:16 GMT -5
Thanks, Judy!
|
|
|
|
Post by jholland1964 on Aug 4, 2017 22:17:52 GMT -5
You're welcome Linda. Sorry we couldn't get it done here but there are so many errors with so many different services, 8 at least, it would be best to take it back to the repair shop and let them do it fully in one or two days rather than try to go through each individual error yourself and try to fix them. It honestly may take a repair install to get it all running as it should, I don't really know for sure. That was the recommendation I found for some of those errors.
|
|
