S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 16, 2017 #41 Hmmm... a nice find... try removing razer software from your machine and see if there's any improvement.
Hmmm... a nice find... try removing razer software from your machine and see if there's any improvement.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 17, 2017 #42 Will do, I actually updated the Razer Drivers on the day I was sending you the Memtest results, if I get another crash I will go right after the Razer software, excellent find!
Will do, I actually updated the Razer Drivers on the day I was sending you the Memtest results, if I get another crash I will go right after the Razer software, excellent find!
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 20, 2017 #43 I removed the system file that commonly causes the Razer releated blue-screens ( rzpmgrk.sys ), worked fine for a few days. Then I got this error today, once again system_service_exception, blaming tcpip.sys, minidump attatched. View attachment 122017-22375-01.zip
I removed the system file that commonly causes the Razer releated blue-screens ( rzpmgrk.sys ), worked fine for a few days. Then I got this error today, once again system_service_exception, blaming tcpip.sys, minidump attatched. View attachment 122017-22375-01.zip
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 20, 2017 #44 I'm suspecting a software that is network related may be causing this, please do the following: Step#1 - FRST Scan 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Right click to run as administrator. When the tool opens click Yes to disclaimer. 3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already). 4. Press Scan button. 5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop) 6. Please attach the log back here. 7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
I'm suspecting a software that is network related may be causing this, please do the following: Step#1 - FRST Scan 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Right click to run as administrator. When the tool opens click Yes to disclaimer. 3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already). 4. Press Scan button. 5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop) 6. Please attach the log back here. 7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 20, 2017 #45 Scan done, here is the logs. Attachments Addition.txt 55.7 KB · Views: 1 FRST.txt 19.2 KB · Views: 0
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 20, 2017 #46 Please uninstall all Razer software from your system and then monitor for crashes.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 20, 2017 #47 Done, uninstalled Synapse and the Chroma SDK. I'll report back if anything happens!
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 20, 2017 #49 Uninstalled Synapse and Chroma SDK, yet when I restarted the PC the Razer folder is still present (as well as the GameScanner process in task manager) Yet windows says I uninstalled it? shortcut was still there too (but did not work)
Uninstalled Synapse and Chroma SDK, yet when I restarted the PC the Razer folder is still present (as well as the GameScanner process in task manager) Yet windows says I uninstalled it? shortcut was still there too (but did not work)
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 20, 2017 #50 Kill the process and delete the Razer folder afterwards.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 20, 2017 #51 Ah! That worked, good lord I could kiss you. :hug: I'll do another quick restart, and I'll report back if anything happens!
Ah! That worked, good lord I could kiss you. :hug: I'll do another quick restart, and I'll report back if anything happens!
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 27, 2017 #52 Well then, the PC had no issues for seven days....then I got another blue screen, about five-six minutes ago. I'm about to scream in all honesty. EDIT: I looked in my System32 driver folder and found three razer files still hanging around for some reason, deleted them just incase. Attachments 122717-27234-01.zip 28.4 KB · Views: 4
Well then, the PC had no issues for seven days....then I got another blue screen, about five-six minutes ago. I'm about to scream in all honesty. EDIT: I looked in my System32 driver folder and found three razer files still hanging around for some reason, deleted them just incase.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 30, 2017 #53 So I had two more bluescreens today, as well as my mouse not working (for some reason, managed to figure that out though) What else could it be??? Attachments 2 Minidump.zip 52.5 KB · Views: 2
So I had two more bluescreens today, as well as my mouse not working (for some reason, managed to figure that out though) What else could it be???
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 30, 2017 #54 Use Prime95 Blend test for a few hours and see if you get anything: https://www.sysnative.com/forums/ha...rocessor-diagnostic-tool-ipdt.html#post202168
Use Prime95 Blend test for a few hours and see if you get anything: https://www.sysnative.com/forums/ha...rocessor-diagnostic-tool-ipdt.html#post202168
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 30, 2017 #55 Okay, I'll load it up later tonight and let it run.
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 30, 2017 #56 Got another blue-screen, didn't run the program yet. Including the dump file if you want to see it. Attachments 123017-23078-01.zip 24.6 KB · Views: 1
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 30, 2017 #57 Aaandd another one... Attachments 123017-20953-01.zip 24.8 KB · Views: 2
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 31, 2017 #58 I ran the program for a few hours, no crashes occured during the time. Are the dump files able to point to anything at all? I'm really not sure as to what is causing this problem.
I ran the program for a few hours, no crashes occured during the time. Are the dump files able to point to anything at all? I'm really not sure as to what is causing this problem.
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Dec 31, 2017 #59 Could you post a new logs collection (and perhaps a speccy snapshot)?
DissyEX Well-known member Joined Oct 27, 2017 Posts 80 Dec 31, 2017 #60 xilolee said: Could you post a new logs collection (and perhaps a speccy snapshot)? Click to expand... If it wouldn't bluescreen almost instantly, then yes. http://speccy.piriform.com/results/2VgYKAmCVPsgODOidGYwVEW Attachments Addition.txt 59.6 KB · Views: 1 FRST.txt 20.2 KB · Views: 2
xilolee said: Could you post a new logs collection (and perhaps a speccy snapshot)? Click to expand... If it wouldn't bluescreen almost instantly, then yes. http://speccy.piriform.com/results/2VgYKAmCVPsgODOidGYwVEW