Windows 8.1 Irregular BSODs
Tags:
- Blue Screen
-
Windows 8
- Windows 8.1
Last response: in Windows 8
FluffyWaffles
September 28, 2014 1:15:55 AM
For roughly the past month, I have been getting irregular crashes. The crashes result in BSODs, most of the time which are resulting with different error messages, though they most commonly relate to some type of memory error. These crashes have only ever happened when I am playing video games (most currently blade and soul RU with english patch). Most often I am also running firefox along with my game on my second screen on twitch watching streams, youtube for videos, reading emails on gmail or on a game forum.
Personal troubleshooting attempts:
The driver programs for my keyboard and mouse (razer black widow 2013 ultimate's razer synapse and logitech g700s' gaming software, respectively) are defaulted not to run on startup and are only used when I need to make configurations to settings (never running when I crash) to eliminate their drivers as any possible problem.
I have run memtest, and it has come up clean after one full pass.
None of my system parts are overclocked. I have run a prime95 test for roughly 15minutes and it came up clean.
I have run HWMonitor while I am gaming, and temperatures come out to be fine, so overheating was ruled out, as well.
I have done "/sfc Scannow" in an elevated command prompt and it has come up clean.
I have updated my drivers (checked using SlimDrivers) just recently, and will mention if this fixed any problems (was AMD SMB bus and SATA driver, i believe but cant remember for sure).
Dxdiag comes out clean as well from what I can tell.
In my bios, the only thing I have changed so far was change my ram voltage from auto to 1.5V in case my ram wasn't getting enough juice.
I have done a completey fresh install of my NVidia drivers as well. Afterwards, in my device manager, I have disabled NVidia Virtual audio device under "sound, video and game controllers" and the High Definition Audio controllers for my graphics cards (PCI bus 1 and 3, not 0) under "system devices."
These steps were taken separately over the course of this month as I came across the solutions online. While they helped a bit with the frequency and a few type of problems, the bsods in general still haven't gone away.
I have done full system scans on avast!(free version) and Malwarebytes Anti-Malware (Premium), both of which come clean.
I plan to run furmark as well later, once I have the time. If needed, I can put my minidump files into a zip and post a link (let me know preferred site to upload to). I will also attach a fresh dxdiag analysis if it can help pinpoint a problem. I very much hope that I won't have to resort to reinstalling windows 8.1 and thank anyone willing to help me figure this out.
Computer Specs
CPU: AMD FX 8350 (w/ Cooler Master Hyper 212 Evo+ for cooler)
Graphics: 2 GTX 660Ti in SLI (ASUS Direct CU II coolers)
RAM: 2 kits of 4x2gb Corsair Vengeance 1337mhz (total 16gb ram)
MB: ASUS M5A99FX PRO R2.0
PSU: Corsair RM750
Personal troubleshooting attempts:
The driver programs for my keyboard and mouse (razer black widow 2013 ultimate's razer synapse and logitech g700s' gaming software, respectively) are defaulted not to run on startup and are only used when I need to make configurations to settings (never running when I crash) to eliminate their drivers as any possible problem.
I have run memtest, and it has come up clean after one full pass.
None of my system parts are overclocked. I have run a prime95 test for roughly 15minutes and it came up clean.
I have run HWMonitor while I am gaming, and temperatures come out to be fine, so overheating was ruled out, as well.
I have done "/sfc Scannow" in an elevated command prompt and it has come up clean.
I have updated my drivers (checked using SlimDrivers) just recently, and will mention if this fixed any problems (was AMD SMB bus and SATA driver, i believe but cant remember for sure).
Dxdiag comes out clean as well from what I can tell.
In my bios, the only thing I have changed so far was change my ram voltage from auto to 1.5V in case my ram wasn't getting enough juice.
I have done a completey fresh install of my NVidia drivers as well. Afterwards, in my device manager, I have disabled NVidia Virtual audio device under "sound, video and game controllers" and the High Definition Audio controllers for my graphics cards (PCI bus 1 and 3, not 0) under "system devices."
These steps were taken separately over the course of this month as I came across the solutions online. While they helped a bit with the frequency and a few type of problems, the bsods in general still haven't gone away.
I have done full system scans on avast!(free version) and Malwarebytes Anti-Malware (Premium), both of which come clean.
I plan to run furmark as well later, once I have the time. If needed, I can put my minidump files into a zip and post a link (let me know preferred site to upload to). I will also attach a fresh dxdiag analysis if it can help pinpoint a problem. I very much hope that I won't have to resort to reinstalling windows 8.1 and thank anyone willing to help me figure this out.
Computer Specs
CPU: AMD FX 8350 (w/ Cooler Master Hyper 212 Evo+ for cooler)
Graphics: 2 GTX 660Ti in SLI (ASUS Direct CU II coolers)
RAM: 2 kits of 4x2gb Corsair Vengeance 1337mhz (total 16gb ram)
MB: ASUS M5A99FX PRO R2.0
PSU: Corsair RM750
More about : windows irregular bsods
-
Reply to FluffyWaffles
make sure you update your razer drivers, they should have this years date. the ones from last year tended to corrupt other drivers memory and caused various bugchecks.
you can also put your memory .dmp file on a server to be looked at. There are lots of OEM drivers that are common causes of crashes. Sometimes, just looking at the driver dates and the name of the driver they can be spotted.
you can do the following look at all the driver dates
start cmd.exe as a admin
driverquery.exe /v > myfile.txt
notepad myfile.txt
then look at the dates of the drivers in the list
you can also just type
driverquery.exe
and it will show the name and date and no verbose info
you can also put your memory .dmp file on a server to be looked at. There are lots of OEM drivers that are common causes of crashes. Sometimes, just looking at the driver dates and the name of the driver they can be spotted.
you can do the following look at all the driver dates
start cmd.exe as a admin
driverquery.exe /v > myfile.txt
notepad myfile.txt
then look at the dates of the drivers in the list
you can also just type
driverquery.exe
and it will show the name and date and no verbose info
-
Reply to johnbl
m
0
l
FluffyWaffles
September 28, 2014 1:43:20 PM
My razer driver for my keyboard is up to date and has been updated within the past few months, so I do not think that may have been the problem. I have updated again just now in case however and will let you know if that made a progress.
I can upload my memory .dmp file if that would help (and the driverquery file if that may help as well), but what server should I upload to? I'll post a link afterwards.
I can upload my memory .dmp file if that would help (and the driverquery file if that may help as well), but what server should I upload to? I'll post a link afterwards.
-
Reply to FluffyWaffles
m
0
l
Related resources
- Multiple BSODs Windows 8.1 - Forum
- Frequent Bsods on a fresh Windows 8.1 Install - Forum
- bsod windows 8.1 after a "fire" issue - Forum
- BSOD 0x00000116 windows 8.1 64 bit - Forum
- Windows 8.1 BSOD- KMODE_EXCEPTION_NOT_HANDLED - Forum
anywhere where you can get space with public access to it. google docs, microsoft one drive, mediafire,...
what bugcheck code are you getting? some codes require kernel or full memory dumps rather than a minidump in order to figure them out.
I can upload my memory .dmp file if that would help (and the driverquery file if that may help as well), but what server should I upload to? I'll post a link afterwards.
what bugcheck code are you getting? some codes require kernel or full memory dumps rather than a minidump in order to figure them out.
FluffyWaffles said:
My razer driver for my keyboard is up to date and has been updated within the past few months, so I do not think that may have been the problem. I have updated again just now in case however and will let you know if that made a progress.I can upload my memory .dmp file if that would help (and the driverquery file if that may help as well), but what server should I upload to? I'll post a link afterwards.
-
Reply to johnbl
m
0
l
FluffyWaffles
October 2, 2014 12:22:43 PM
Sorry it took so long. Here's the link to my memory dmp:
http://www.mediafire.com/download/j7dmun66vucajdg/MEMOR...
upload took a while since its 1gb.
As for bugcheck code, from what I can gather from my mindumps, it was most recently a kernel security check failure and system service exception the day before.
http://www.mediafire.com/download/j7dmun66vucajdg/MEMOR...
upload took a while since its 1gb.
As for bugcheck code, from what I can gather from my mindumps, it was most recently a kernel security check failure and system service exception the day before.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 2, 2014 12:28:09 PM
bugcheck was in the directx but I figure it was caused by the GPU overclocking driver
AODDriver2.sys Tue Feb 11 03:06:52 2014
I would remove any gpu overclock and see if that was the cause.
you also have various other suspect drivers to remove or update.
lmimirr.sys Tue Apr 10 15:32:45 2007 ( RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver)
LGBusEnum.sys Mon Nov 23 17:36:48 2009 ( Logitech Keyboard driver)
BUSB2902.sys Thu Oct 29 19:02:34 2009 (USB audio driver? )
busbwdm.sys Thu Oct 29 18:01:20 2009
LMIRfsDriver.sys Mon Jul 14 09:26:56 2008 ( RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver)
AsUpIO.sys Mon Aug 02 19:47:59 2010
AsIO.sys Wed Aug 22 02:54:47 2012
AiChargerPlus.sys Wed Apr 18 18:17:35 2012 (tends to cause problems)
AODDriver2.sys Tue Feb 11 03:06:52 2014
I would remove any gpu overclock and see if that was the cause.
you also have various other suspect drivers to remove or update.
lmimirr.sys Tue Apr 10 15:32:45 2007 ( RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver)
LGBusEnum.sys Mon Nov 23 17:36:48 2009 ( Logitech Keyboard driver)
BUSB2902.sys Thu Oct 29 19:02:34 2009 (USB audio driver? )
busbwdm.sys Thu Oct 29 18:01:20 2009
LMIRfsDriver.sys Mon Jul 14 09:26:56 2008 ( RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver)
AsUpIO.sys Mon Aug 02 19:47:59 2010
AsIO.sys Wed Aug 22 02:54:47 2012
AiChargerPlus.sys Wed Apr 18 18:17:35 2012 (tends to cause problems)
-
Reply to johnbl
m
0
l
FluffyWaffles
October 2, 2014 5:18:19 PM
For Paul, I gave the larger dump since I was specifically asked for it. I can supply the minidumps later if they're needed.
As for john:
I did overclock my gpu before however have since undid the overclock. I will reset it to factory again to see if that may be the problem.
As for the other drivers, how would I update/remove them? I am unfamiliar with how to update or remove them specifically, so I could use some help there.
Also to note, the BUSB2902.sys is the usb driver for my audio mixer (behringer xenyx q802usb).
As for john:
I did overclock my gpu before however have since undid the overclock. I will reset it to factory again to see if that may be the problem.
As for the other drivers, how would I update/remove them? I am unfamiliar with how to update or remove them specifically, so I could use some help there.
Also to note, the BUSB2902.sys is the usb driver for my audio mixer (behringer xenyx q802usb).
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 2, 2014 5:22:18 PM
FluffyWaffles
October 3, 2014 9:03:58 PM
I checked my GPU clock speeds, and is very much on default settings with no changes currently made by me.
As for my CPU overclocking, I have only attempted overclocking using ASUS AI Suite II and have undone those changes a long time ago. Should I fully remove it to see if that solves my problems?
Any future cpu overclocking I don't mind doing through the bios so removing it fully is no biggie to me.
As for my CPU overclocking, I have only attempted overclocking using ASUS AI Suite II and have undone those changes a long time ago. Should I fully remove it to see if that solves my problems?
Any future cpu overclocking I don't mind doing through the bios so removing it fully is no biggie to me.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 3, 2014 9:12:15 PM
FluffyWaffles
October 3, 2014 10:16:21 PM
I understand that OC in bios can also cause crashes: I don't plan to do it until after all my current problems are resolved.
Got another crash, this time was a new bugcheck: "attempted_execute_of_noexecute_memory"
Here is the minidump: http://www.mediafire.com/download/3jiavtbmkj0jpiy/10031...
I'll uninstall asus suite and see how it goes for a while. I will let you know if anything happens.
Got another crash, this time was a new bugcheck: "attempted_execute_of_noexecute_memory"
Here is the minidump: http://www.mediafire.com/download/3jiavtbmkj0jpiy/10031...
I'll uninstall asus suite and see how it goes for a while. I will let you know if anything happens.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 3, 2014 10:28:24 PM
FluffyWaffles
October 4, 2014 12:30:06 AM
Tried updating drivers through device manager from Microsoft and they came back as updated. I have tried getting the drivers from the manufacturer's website in the past, but stopped once avast gave me a warning (and stopped the DL with said warning) so I haven't tried again since. The hardware itself is rather old, so I just assumed the support for the hardware has stopped.
The logmein drivers I don't need, as I've uninstalled the program a long time ago. Not sure how to remove the drivers specifically either, so would appreciate an assist there.
The logmein drivers I don't need, as I've uninstalled the program a long time ago. Not sure how to remove the drivers specifically either, so would appreciate an assist there.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 4, 2014 12:37:28 AM
Windowsupdate wont find drivers for everything. Altho if the system keeps crashing you may have to remove that USB audio device to see if it fixes it.
lmimirr.sys and LMIRfsDriver.sys belong to logmein. These maybe in C:\windows\system32\drivers folder. If theyre there, delete them
Or go to device manager, / view show hidden devices. Go thru the entries see if there's any reference to these 2 drivers. If there is, delete them
lmimirr.sys and LMIRfsDriver.sys belong to logmein. These maybe in C:\windows\system32\drivers folder. If theyre there, delete them
Or go to device manager, / view show hidden devices. Go thru the entries see if there's any reference to these 2 drivers. If there is, delete them
-
Reply to Paul NZ
m
0
l
FluffyWaffles
October 5, 2014 1:42:16 AM
I've deleted the logmein drivers and checked my USB audio driver files to see if they were updated via cross check driver versions on my system versus on manufacturer's website. Numbers were the same, so I assume they are updated.
ASUS AI suite II has also been fully uninstalled from my system. So far I have not had any BSODs, however I have had several display driver crashes (they were able to recover without a bsod).
The only thing I could notice from these would be that I am playing games while running something in my browser that uses flash. I've checked this with both firefox and google chrome and it has crashed at least once with each case when I had a twitch stream or youtube video playing.
To check if its any of my hardware, I'll disconnect my hardware one by one from my computer for 24 hour cycles and see if it changes anything.
ASUS AI suite II has also been fully uninstalled from my system. So far I have not had any BSODs, however I have had several display driver crashes (they were able to recover without a bsod).
The only thing I could notice from these would be that I am playing games while running something in my browser that uses flash. I've checked this with both firefox and google chrome and it has crashed at least once with each case when I had a twitch stream or youtube video playing.
To check if its any of my hardware, I'll disconnect my hardware one by one from my computer for 24 hour cycles and see if it changes anything.
-
Reply to FluffyWaffles
m
0
l
FluffyWaffles
October 5, 2014 3:26:45 AM
Just had another crash. http://www.mediafire.com/download/al3zft9if0qc05a/10051...
This time I didn't have any game open, however did have a twitch stream open. Crash was "Unexpected Kernel Mode Trap" and pointed to win32k.sys.
At this rate, would it be simpler to just cut my pains and reinstall my OS? The constant crashes are discouraging and are starting to annoy me more than the thought of having to reinstall everything on my C drive.
This time I didn't have any game open, however did have a twitch stream open. Crash was "Unexpected Kernel Mode Trap" and pointed to win32k.sys.
At this rate, would it be simpler to just cut my pains and reinstall my OS? The constant crashes are discouraging and are starting to annoy me more than the thought of having to reinstall everything on my C drive.
-
Reply to FluffyWaffles
m
0
l
Desktop Window Manager dwm.exe
I think the windows display manager uses a buffer allocated in the graphic driver to make a buffer to hold the graphics data for the desktop background.
I think it got a fault when it tried to release the buffer and then the program that was to service the fault got a fault and the system bugchecked.
I would either use the overclocking driver to underclock your GPU memory by a 100 MHz or remove it if your are overclocking.
It will always be the suspect if it is loaded and you have a GPU failure.
- it could also be caused by a stack overflow in the kernel caused by the two virus scanners running at the same time.
(can not tell with a mini memory dump, normally you use a kernel memory dump and verifier.exe flags to catch this problem)
you are running two virus scanners avast and malwarebytes this is bad news only run one or remove both and run the malwarebytes free version that does not install drivers.
GPU graphic card overclock software installed
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys (remove because I can not tell if you are overclocking the GPU)
you have asus hardware monitoring software installed
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010 (remove)
Asus PCProbe Utility
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012 (remove)
iTunes software
\SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Thu May 03 12:56:17 2012 (not sure, but it is old)
CyberLink WebCam Virtual Driver
\SystemRoot\system32\DRIVERS\clwvd.sys Wed Apr 13 20:47:49 2011 (remove or update)
usbfilter.sys Tue Aug 28 18:27:12 2012
AMD USB Filter Driver I would go to amd website and find a chipset driver update for my CPU
your BIOS version is 3 versions out of date. current version is 2501 on 5/14/2014 looks like they did fixes for the USB, new CPUs, and various "system stability" fixes (most often fixes in default memory timings and voltages for various memory modules) I would pick up the update.
on the asus website they have amd chipset drivers dated 10/18/2013 under the windows 8 driver listings. Install these if you can not find a newer version from the AMD website. These drivers will fix various bugs in the CPU and in the Chipset on your actual motherboard.
http://www.asus.com/Motherboards/M5A99FX_PRO_R20/HelpDe...
system info:
Manufacturer ASUSTeK COMPUTER INC.
Product M5A99FX PRO R2.0
Version Rev 1.xx
BIOS Version 2005
BIOS Release Date 09/16/2013
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Max Speed 4000MHz
Current Speed 4000MHz
I think the windows display manager uses a buffer allocated in the graphic driver to make a buffer to hold the graphics data for the desktop background.
I think it got a fault when it tried to release the buffer and then the program that was to service the fault got a fault and the system bugchecked.
I would either use the overclocking driver to underclock your GPU memory by a 100 MHz or remove it if your are overclocking.
It will always be the suspect if it is loaded and you have a GPU failure.
- it could also be caused by a stack overflow in the kernel caused by the two virus scanners running at the same time.
(can not tell with a mini memory dump, normally you use a kernel memory dump and verifier.exe flags to catch this problem)
you are running two virus scanners avast and malwarebytes this is bad news only run one or remove both and run the malwarebytes free version that does not install drivers.
GPU graphic card overclock software installed
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys (remove because I can not tell if you are overclocking the GPU)
you have asus hardware monitoring software installed
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010 (remove)
Asus PCProbe Utility
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012 (remove)
iTunes software
\SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Thu May 03 12:56:17 2012 (not sure, but it is old)
CyberLink WebCam Virtual Driver
\SystemRoot\system32\DRIVERS\clwvd.sys Wed Apr 13 20:47:49 2011 (remove or update)
usbfilter.sys Tue Aug 28 18:27:12 2012
AMD USB Filter Driver I would go to amd website and find a chipset driver update for my CPU
your BIOS version is 3 versions out of date. current version is 2501 on 5/14/2014 looks like they did fixes for the USB, new CPUs, and various "system stability" fixes (most often fixes in default memory timings and voltages for various memory modules) I would pick up the update.
on the asus website they have amd chipset drivers dated 10/18/2013 under the windows 8 driver listings. Install these if you can not find a newer version from the AMD website. These drivers will fix various bugs in the CPU and in the Chipset on your actual motherboard.
http://www.asus.com/Motherboards/M5A99FX_PRO_R20/HelpDe...
system info:
Manufacturer ASUSTeK COMPUTER INC.
Product M5A99FX PRO R2.0
Version Rev 1.xx
BIOS Version 2005
BIOS Release Date 09/16/2013
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Max Speed 4000MHz
Current Speed 4000MHz
-
Reply to johnbl
m
0
l
FluffyWaffles
October 5, 2014 6:52:42 PM
For my virus scanners, I've kept avast as is and disabled malware protection and malware website protection on malwarebytes and disabled them on startup. I now only have malwarebytes do a threat scan once every three days for its automated schedule, but I'll remove it if you think it is still a problem. I have also removed the mentioned drivers except for GEARAspiWDM.sys (don't really think it can cause a problem).
As for the AMD chipset, I was able to update via the website to version 14.9 and dated 9/28/2014. I have also updated the bios to version 2501.
If I still have another crash, I'll make sure to give the full memory dump for john and the minidump for paul.
As for the AMD chipset, I was able to update via the website to version 14.9 and dated 9/28/2014. I have also updated the bios to version 2501.
If I still have another crash, I'll make sure to give the full memory dump for john and the minidump for paul.
-
Reply to FluffyWaffles
m
0
l
FluffyWaffles
October 11, 2014 8:03:59 PM
Another crash, sadly. Was a system service exception.
Full Memory Dump: http://www.mediafire.com/download/tfgnb4mpn9oo59x/MEMOR...
Minidump: http://www.mediafire.com/download/2cfyefc54euvew8/10111...
I'll attempt seeing if lowering my gpu memory by 100MHz helps this time around. All other gpu settings are on default.
Full Memory Dump: http://www.mediafire.com/download/tfgnb4mpn9oo59x/MEMOR...
Minidump: http://www.mediafire.com/download/2cfyefc54euvew8/10111...
I'll attempt seeing if lowering my gpu memory by 100MHz helps this time around. All other gpu settings are on default.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 11, 2014 8:15:33 PM
FluffyWaffles
October 11, 2014 8:48:21 PM
The behringer usb audio driver i've checked already on the manufacturer's website and have verified that this driver is as updated as it gets. The mixer is a very old model, and this lines up with that fact.
(To make sure it isn't the mixer's driver causing the crash, I'll be running for a week with the mixer physically disconnected from the system.)
As for avast causing the stop error, how would I go about checking if it is? Would swapping my active protection from avast to malwarebytes premium do?
Here's some extra info on my system for the case of my gpu from furmark and gpu-z (didnt know if there was a preferred img site, so I used tinpic):
Furmark: http://tinypic.com/r/wieed/8
GPU-Z : http://tinypic.com/r/30xjy86/8
Both my gpus are on the same setting.
(To make sure it isn't the mixer's driver causing the crash, I'll be running for a week with the mixer physically disconnected from the system.)
As for avast causing the stop error, how would I go about checking if it is? Would swapping my active protection from avast to malwarebytes premium do?
Here's some extra info on my system for the case of my gpu from furmark and gpu-z (didnt know if there was a preferred img site, so I used tinpic):
Furmark: http://tinypic.com/r/wieed/8
GPU-Z : http://tinypic.com/r/30xjy86/8
Both my gpus are on the same setting.
-
Reply to FluffyWaffles
m
0
l
Paul NZ
October 11, 2014 9:17:23 PM
FluffyWaffles
October 11, 2014 9:48:03 PM
Yeah I am aware that malwarebytes isn't an antivirus program, hence why I am reluctant to eliminate avast right off the bat. I don't know if fully removing avast would solve my problem, but I will try it if disconnecting my mixer and DAC fail to show improvement over time. The idea of switching to defender just doesn't sit well with me, either.
Sorry if i'm being difficult; the crashes are just irritating me now. A lot.
Sorry if i'm being difficult; the crashes are just irritating me now. A lot.
-
Reply to FluffyWaffles
m
0
l
well my guess is Rzudd.sys driver corrupted the memory based on looking at the internal trace logs. then windows later bugcheck when part of its internal data structures were corrupted by the RSudd.sys driver over writing them.
The driver is very current but I would look for a update/roll back the driver or remove this device. (i would hope they have a update)
------------------
Rzudd.sys is making some bad USB requests right before the memory corruption bugcheck.
Image path: \SystemRoot\System32\drivers\rzudd.sys
Timestamp: Wed Aug 20 19:58:48 2014
80: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFF8D31DA68, WDFREQUEST 0x00001FFF8EB4B658, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
81: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
in the current full memory dump: bugcheck related to memory corruption:
-remove asgt.exe or the entire garysoft software. (overclocking software)
- turn on verifier.exe debug flags
------------------------------
Use verifier.exe to configure your system to do some special error checking.
You have some very old (2009) usb drivers, these old drivers tend to not work with any other USB device plugged in.
The driver has to process its data and not process data belonging to other devices Like Razer usb keyboard/mice
Usb thumb drives,...
Verifier.exe will catch the errors in these driver and bugcheck and name the driver and the error it is doing.
use this to set up verifier:
http://www.sevenforums.com/crash-lockup-debug-how/65331...
to turn off verifier you run the command (cmd.exe as a admin)
verifier.exe /reset
------------
Looks like you are running Glarysoft utilities. you should uninstall them for now.
one of the glarysoft utilities running on your system is ASGT.exe it is a overclocking utility.
I see various issues in your hardware setup, I think most of them are due to you making changes to try to figure out your problems.
You have 2 audio sources disabled, and a webcam driver remove but software still trying to access it.
(not a big deal, but you will want to fix it after you get your other problems resolved)
The driver is very current but I would look for a update/roll back the driver or remove this device. (i would hope they have a update)
------------------
Rzudd.sys is making some bad USB requests right before the memory corruption bugcheck.
Image path: \SystemRoot\System32\drivers\rzudd.sys
Timestamp: Wed Aug 20 19:58:48 2014
80: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFF8D31DA68, WDFREQUEST 0x00001FFF8EB4B658, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
81: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
in the current full memory dump: bugcheck related to memory corruption:
-remove asgt.exe or the entire garysoft software. (overclocking software)
- turn on verifier.exe debug flags
------------------------------
Use verifier.exe to configure your system to do some special error checking.
You have some very old (2009) usb drivers, these old drivers tend to not work with any other USB device plugged in.
The driver has to process its data and not process data belonging to other devices Like Razer usb keyboard/mice
Usb thumb drives,...
Verifier.exe will catch the errors in these driver and bugcheck and name the driver and the error it is doing.
use this to set up verifier:
http://www.sevenforums.com/crash-lockup-debug-how/65331...
to turn off verifier you run the command (cmd.exe as a admin)
verifier.exe /reset
------------
Looks like you are running Glarysoft utilities. you should uninstall them for now.
one of the glarysoft utilities running on your system is ASGT.exe it is a overclocking utility.
I see various issues in your hardware setup, I think most of them are due to you making changes to try to figure out your problems.
You have 2 audio sources disabled, and a webcam driver remove but software still trying to access it.
(not a big deal, but you will want to fix it after you get your other problems resolved)
-
Reply to johnbl
m
0
l
FluffyWaffles
October 12, 2014 9:56:18 PM
Rzudd.sys is the driver for my keyboard. There is no further update, so I'll try seeing if there is a possible older driver on their forums that is recommended to revert to.
ASGT.exe is a reference to my overclocking utility, ASUS GPU Tweak. I can uninstall it once I reset my gpu memory speed to factory default.
This is the first time that I have heard of Glarysoft utilities, so anything outside of asgt.exe that may be it I wouldn't know of unless you specifically point out the program name.
The hardware setup is from me figuring out my problems. The 2 audio sources are my gpu's, which I disabled after some forum rummaging on nvidia that states nvidia audio may cause crashes. As for the webcam driver, it isn't removed but disabled on startup. I don't use it however so I'll just uninstall it.
I attempted to use verifier, however on the very last step for setup where you choose which drivers to test from a list, the list was empty. There were no instructions for which parameters to use via command line either so I am in a bit of a slump as for what to do. The instructions make it rather clear that mistakes can cause problems, however, so I haven't done it yet.
ASGT.exe is a reference to my overclocking utility, ASUS GPU Tweak. I can uninstall it once I reset my gpu memory speed to factory default.
This is the first time that I have heard of Glarysoft utilities, so anything outside of asgt.exe that may be it I wouldn't know of unless you specifically point out the program name.
The hardware setup is from me figuring out my problems. The 2 audio sources are my gpu's, which I disabled after some forum rummaging on nvidia that states nvidia audio may cause crashes. As for the webcam driver, it isn't removed but disabled on startup. I don't use it however so I'll just uninstall it.
I attempted to use verifier, however on the very last step for setup where you choose which drivers to test from a list, the list was empty. There were no instructions for which parameters to use via command line either so I am in a bit of a slump as for what to do. The instructions make it rather clear that mistakes can cause problems, however, so I haven't done it yet.
-
Reply to FluffyWaffles
m
0
l
verifier should not hurt anything, but it can slow down a machine with all the checking it is doing. Also if it finds a bug it will cause a bugcheck much earlier.
if the bug is found quickly in the first few seconds of booting, you would be blocked from a normal boot. You would have to use safe mode.
most of the time it takes a while before verifier find a problem and bugchecks. then you reboot and run verifier.exe /reset to turn it off after you have your memory dump.
most people just select to check all the drivers for all the error conditions, Sometime they get bugchecks in old drivers that are unrelated to their problem
but most of the time with problems like this it catches the correct driver as it attempts to write over another drivers data.
if the bug is found quickly in the first few seconds of booting, you would be blocked from a normal boot. You would have to use safe mode.
most of the time it takes a while before verifier find a problem and bugchecks. then you reboot and run verifier.exe /reset to turn it off after you have your memory dump.
most people just select to check all the drivers for all the error conditions, Sometime they get bugchecks in old drivers that are unrelated to their problem
but most of the time with problems like this it catches the correct driver as it attempts to write over another drivers data.
-
Reply to johnbl
m
0
l
FluffyWaffles
October 14, 2014 2:58:55 AM
Took several hours, but finally got a crash. Here's the memory dump file:
https://www.mediafire.com/?v4m2f66g01m92uw
Also, a side note: the BSODs have had some warnings in several different forms which include screen flicker, game crash or display driver crash (they never happened all at once, only one of the three happens followed by a few minutes of working properly then one of the symptoms happen again. This reoccurs several times before the crash happens).
https://www.mediafire.com/?v4m2f66g01m92uw
Also, a side note: the BSODs have had some warnings in several different forms which include screen flicker, game crash or display driver crash (they never happened all at once, only one of the three happens followed by a few minutes of working properly then one of the symptoms happen again. This reoccurs several times before the crash happens).
-
Reply to FluffyWaffles
m
0
l
windows changed the boot order of devices on each boot, if one driver is corrupting memory it may be a different driver on each boot. Most of the 3rd party drivers don't call bugchecks in there code. Windows calls bugcheck in the windows code when it check a drivers calls. SO if you have a 3 rd party driver messing up another 3rd party driver you don't get a bugcheck until the second driver calls a windows driver with bad parameters.
ie, razer keyboard driver corrupts memory belonging to the graphics driver, your graphics may get messed up but no bugcheck until the graphics driver uses the messed up date structures to call a windows function. The windows function may then bugcheck.
I am downloading the memory dump now
https://www.mediafire.com/?v4m2f66g01m92uw
Also, a side note: the BSODs have had some warnings in several different forms which include screen flicker, game crash or display driver crash (they never happened all at once, only one of the three happens followed by a few minutes of working properly then one of the symptoms happen again. This reoccurs several times before the crash happens).
ie, razer keyboard driver corrupts memory belonging to the graphics driver, your graphics may get messed up but no bugcheck until the graphics driver uses the messed up date structures to call a windows function. The windows function may then bugcheck.
I am downloading the memory dump now
FluffyWaffles said:
Took several hours, but finally got a crash. Here's the memory dump file:https://www.mediafire.com/?v4m2f66g01m92uw
Also, a side note: the BSODs have had some warnings in several different forms which include screen flicker, game crash or display driver crash (they never happened all at once, only one of the three happens followed by a few minutes of working properly then one of the symptoms happen again. This reoccurs several times before the crash happens).
-
Reply to johnbl
m
0
l
ok looking at the memory dump on dated 10/14/2014
BugCheck 50, {ffffe001bab7fa90, 0, fffff802a48fde2c, 2}
Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeInTree+bc )
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe001bab7fa90, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff802a48fde2c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
# Call Site
00 nt!MiFindEmptyAddressRangeInTree
01 nt!MiFindEmptyAddressRange
02 nt!NtAllocateVirtualMemory
03 nt!KiSystemServiceCopyEnd
not too useful but if you look at the what the ruddz.sys driver
SystemRoot\System32\drivers\rzudd.sys Wed Aug 20 19:58:48 2014 (same driver as last bugcheck)
it made two invalid device requests right before the crash.
here are the internal log entries:
127: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFE53AD93B8, WDFREQUEST 0x00001FFE53AD0BE8, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
128: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
129: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFE53ACDF78, WDFREQUEST 0x00001FFE53AC9B08, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
130: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
---- end of log
The log also indicated that the device made some power state transitions before it made the bad calls.
you might go to the windows control panel power management and see if you can force the device not to power down.
in a attempt to see if you can prevent the condition that caused the driver to make the bad calls. (driver bug)
I would still see if I could get a updated driver or remove the driver and replace the keyboard and see if you still have a problem
I will look at the memory and see if I can see any of the Rzudd.sys drivers data written over the top of the windows data structures
I will send a message with the full rzudd.sys internal log if you want to look at it or send it to get help from the driver maker.
BugCheck 50, {ffffe001bab7fa90, 0, fffff802a48fde2c, 2}
Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeInTree+bc )
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe001bab7fa90, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff802a48fde2c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
# Call Site
00 nt!MiFindEmptyAddressRangeInTree
01 nt!MiFindEmptyAddressRange
02 nt!NtAllocateVirtualMemory
03 nt!KiSystemServiceCopyEnd
not too useful but if you look at the what the ruddz.sys driver
SystemRoot\System32\drivers\rzudd.sys Wed Aug 20 19:58:48 2014 (same driver as last bugcheck)
it made two invalid device requests right before the crash.
here are the internal log entries:
127: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFE53AD93B8, WDFREQUEST 0x00001FFE53AD0BE8, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
128: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
129: FxRequest::GetDeviceControlOutputMemoryObject - Attempt to get UserMode Buffer Pointer for METHOD_NEITHER DeviceControl 0xb0193, WDFDEVICE 0x00001FFE53ACDF78, WDFREQUEST 0x00001FFE53AC9B08, 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)
130: FxRequest::GetDeviceControlOutputMemoryObject - Driver must use METHOD_BUFFERED or METHOD_xx_DIRECT I/O for this call, or use WdfDeviceInitSetIoInCallerContextCallback to probe and lock user mode memory
---- end of log
The log also indicated that the device made some power state transitions before it made the bad calls.
you might go to the windows control panel power management and see if you can force the device not to power down.
in a attempt to see if you can prevent the condition that caused the driver to make the bad calls. (driver bug)
I would still see if I could get a updated driver or remove the driver and replace the keyboard and see if you still have a problem
I will look at the memory and see if I can see any of the Rzudd.sys drivers data written over the top of the windows data structures
I will send a message with the full rzudd.sys internal log if you want to look at it or send it to get help from the driver maker.
-
Reply to johnbl
m
0
l
Oh, i guess if the keyboard driver has any usermode interface to it, it would be what is making the call to the driver. If you turn off the user mode interface, it would not make the call and your driver would then not make the call that corrupted the memory.
it would let you keep the driver and prevent the memory corruption cause by the bad usermode pointers used.
it would let you keep the driver and prevent the memory corruption cause by the bad usermode pointers used.
-
Reply to johnbl
m
0
l
Looking at your bugcheck again>
kind of interesting
all of your 8 cores had the same stack on them:
ffffd000`2ecf67f0 fffff800`52b96896 dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x259
01 ffffd000`2ecf6bc0 fffff800`52a66d75 dxgmms1!VidMmReferenceDmaBuffer+0x56
02 ffffd000`2ecf6c20 fffff800`52a66755 dxgkrnl!DXGCONTEXT::Render+0x225
03 ffffd000`2ecf7770 fffff802`a45e44b3 dxgkrnl!DxgkRender+0x325
04 ffffd000`2ecf7a80 00000000`779c77fa nt!KiSystemServiceCopyEnd+0x13
05 00000000`0de3e6b8 00000000`00000000 0x779c77fa
all of them are doing a direct memory access to the graphics card.
your directx binaries look up to date: Thu Mar 06 01:22:14 2014
the running process was client.bin, I think that is the silerlight subsystem. You might look for a update of that if there is one.
- you have two antivirus programs running on your system. (i would turn one or both off)
-you system is loading a huge number of games into memory as standby memory in case you want to run them.
You might want to go to http://technet.microsoft.com/en-us/sysinternals/ff70022...
and download rammap.exe and run it, go to the menu item called "empty" and you can clear your standby list and working set.
and it will build a more current version rather than pre load old games that you have not used for months.
you had another glarysoft utility installed called mytrashcan.exe maybe a OEM has installed them using their name rather than the vendors name.
looks like razer had some other files running
RzOvlMon.exe <------ you may find that killing this will prevent the error reported in the razer keyboard driver log.
razerrrg_.ttf
razerrl_0.ttf
razer-regu.ttf
I think the other 3 files were just true type fonts files
your nvidia driver was using lots of nonpage pool (expected because of the running game)
nvvad64v.sys Thu Sep 04 10:10:48 2014 (looks current)
NvStreamKms.sys Thu Oct 02 18:39:09 2014
nvlddmkm.sys Sat Sep 13 12:59:50 2014
nvvad64v.sys Thu Sep 04 10:10:48 2014 (NVIDIA Virtual Audio Driver)
At this point I would remove the nvidia streaming service, and disable the nvidia high definition audio in control panel if you dont' get your sound to your speakers via the video cable. I mention this to take the load off of the nvidia driver and hardware.
I would also go into BIOS, disable and reenable a device to get the BIOS to rebuild and reconfigure the various IO ports in the database it hands off to windows. Also make sure you have installed the cpu chipset drivers directly from the chipset manufacture.
AMD FX(tm)-8350 Eight-Core Processor so go to AMD or your motherboard vendor Manufacturer ASUSTeK COMPUTER INC.
Product M5A99FX PRO R2.0
Version Rev 1.xx
I only make these changes because to the DMA call (direct memory access) will go through a DMA controller that would be configured by the BIOS.
(or that is how it used to work, its been a long time)
kind of interesting
all of your 8 cores had the same stack on them:
ffffd000`2ecf67f0 fffff800`52b96896 dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x259
01 ffffd000`2ecf6bc0 fffff800`52a66d75 dxgmms1!VidMmReferenceDmaBuffer+0x56
02 ffffd000`2ecf6c20 fffff800`52a66755 dxgkrnl!DXGCONTEXT::Render+0x225
03 ffffd000`2ecf7770 fffff802`a45e44b3 dxgkrnl!DxgkRender+0x325
04 ffffd000`2ecf7a80 00000000`779c77fa nt!KiSystemServiceCopyEnd+0x13
05 00000000`0de3e6b8 00000000`00000000 0x779c77fa
all of them are doing a direct memory access to the graphics card.
your directx binaries look up to date: Thu Mar 06 01:22:14 2014
the running process was client.bin, I think that is the silerlight subsystem. You might look for a update of that if there is one.
- you have two antivirus programs running on your system. (i would turn one or both off)
-you system is loading a huge number of games into memory as standby memory in case you want to run them.
You might want to go to http://technet.microsoft.com/en-us/sysinternals/ff70022...
and download rammap.exe and run it, go to the menu item called "empty" and you can clear your standby list and working set.
and it will build a more current version rather than pre load old games that you have not used for months.
you had another glarysoft utility installed called mytrashcan.exe maybe a OEM has installed them using their name rather than the vendors name.
looks like razer had some other files running
RzOvlMon.exe <------ you may find that killing this will prevent the error reported in the razer keyboard driver log.
razerrrg_.ttf
razerrl_0.ttf
razer-regu.ttf
I think the other 3 files were just true type fonts files
your nvidia driver was using lots of nonpage pool (expected because of the running game)
nvvad64v.sys Thu Sep 04 10:10:48 2014 (looks current)
NvStreamKms.sys Thu Oct 02 18:39:09 2014
nvlddmkm.sys Sat Sep 13 12:59:50 2014
nvvad64v.sys Thu Sep 04 10:10:48 2014 (NVIDIA Virtual Audio Driver)
At this point I would remove the nvidia streaming service, and disable the nvidia high definition audio in control panel if you dont' get your sound to your speakers via the video cable. I mention this to take the load off of the nvidia driver and hardware.
I would also go into BIOS, disable and reenable a device to get the BIOS to rebuild and reconfigure the various IO ports in the database it hands off to windows. Also make sure you have installed the cpu chipset drivers directly from the chipset manufacture.
AMD FX(tm)-8350 Eight-Core Processor so go to AMD or your motherboard vendor Manufacturer ASUSTeK COMPUTER INC.
Product M5A99FX PRO R2.0
Version Rev 1.xx
I only make these changes because to the DMA call (direct memory access) will go through a DMA controller that would be configured by the BIOS.
(or that is how it used to work, its been a long time)
-
Reply to johnbl
m
0
l
FluffyWaffles
October 15, 2014 10:35:11 PM
I don't think silverlight would be the problem here, but still worth looking into an update. I'll get back to you on that.
The antivirus programs are avast and malwarebytes, and the latter is configured only for routine scans every three days; the active protection on malwarebytes is completely disabled, so there should be little or no conflicts with both of them running. Plus, I've had them both running before with no problems for several months. This is also verified by the malwarebytes forums, where the only problem I've found mentioned is when trying to install either or after the other is already installed on the system. After that, most other posts on the malwarebytes forums were inconveniences or incompatabilities with programs that need antivirus/antimalware exceptions, such as the Private Internet Access VPN program for generating its ruby.exe file. (For full transparency, this was only for 3-4 hours of rummaging their forum a while back when configuring their vpn for myself)
mytrashcan.exe was something I got of my own volition; it just allows me to modify my desktop recycle bin to whatever image i please and resize the bin on my desktop. Outside of adding a second or two on login time, I don't think it can affect anything.
The cpu chipset drivers are already updated directly from AMD's website. I've never thought of reenabling my device through the bios though, so I'll try that.
I do believe that my crashes are solely due to razer's keyboard driver, though: the reason I believe this is because I've had the screen flicker again recently (which normally after several a BSOD appears). I tried shutting down the razer synapse process and rebooting it, and the system worked fine for the rest of that session (5 hours, after which I stopped for the day).
The antivirus programs are avast and malwarebytes, and the latter is configured only for routine scans every three days; the active protection on malwarebytes is completely disabled, so there should be little or no conflicts with both of them running. Plus, I've had them both running before with no problems for several months. This is also verified by the malwarebytes forums, where the only problem I've found mentioned is when trying to install either or after the other is already installed on the system. After that, most other posts on the malwarebytes forums were inconveniences or incompatabilities with programs that need antivirus/antimalware exceptions, such as the Private Internet Access VPN program for generating its ruby.exe file. (For full transparency, this was only for 3-4 hours of rummaging their forum a while back when configuring their vpn for myself)
mytrashcan.exe was something I got of my own volition; it just allows me to modify my desktop recycle bin to whatever image i please and resize the bin on my desktop. Outside of adding a second or two on login time, I don't think it can affect anything.
The cpu chipset drivers are already updated directly from AMD's website. I've never thought of reenabling my device through the bios though, so I'll try that.
I do believe that my crashes are solely due to razer's keyboard driver, though: the reason I believe this is because I've had the screen flicker again recently (which normally after several a BSOD appears). I tried shutting down the razer synapse process and rebooting it, and the system worked fine for the rest of that session (5 hours, after which I stopped for the day).
-
Reply to FluffyWaffles
m
0
l
I think the crashes were also because of the razer usermode interface program to the razer keyboard driver.
I just listed all the other things I could see that might be problems with your machine.
The antivirus programs are avast and malwarebytes, and the latter is configured only for routine scans every three days; the active protection on malwarebytes is completely disabled, so there should be little or no conflicts with both of them running. Plus, I've had them both running before with no problems for several months. This is also verified by the malwarebytes forums, where the only problem I've found mentioned is when trying to install either or after the other is already installed on the system. After that, most other posts on the malwarebytes forums were inconveniences or incompatabilities with programs that need antivirus/antimalware exceptions, such as the Private Internet Access VPN program for generating its ruby.exe file. (For full transparency, this was only for 3-4 hours of rummaging their forum a while back when configuring their vpn for myself)
mytrashcan.exe was something I got of my own volition; it just allows me to modify my desktop recycle bin to whatever image i please and resize the bin on my desktop. Outside of adding a second or two on login time, I don't think it can affect anything.
The cpu chipset drivers are already updated directly from AMD's website. I've never thought of reenabling my device through the bios though, so I'll try that.
I do believe that my crashes are solely due to razer's keyboard driver, though: the reason I believe this is because I've had the screen flicker again recently (which normally after several a BSOD appears). I tried shutting down the razer synapse process and rebooting it, and the system worked fine for the rest of that session (5 hours, after which I stopped for the day).
I just listed all the other things I could see that might be problems with your machine.
FluffyWaffles said:
I don't think silverlight would be the problem here, but still worth looking into an update. I'll get back to you on that.The antivirus programs are avast and malwarebytes, and the latter is configured only for routine scans every three days; the active protection on malwarebytes is completely disabled, so there should be little or no conflicts with both of them running. Plus, I've had them both running before with no problems for several months. This is also verified by the malwarebytes forums, where the only problem I've found mentioned is when trying to install either or after the other is already installed on the system. After that, most other posts on the malwarebytes forums were inconveniences or incompatabilities with programs that need antivirus/antimalware exceptions, such as the Private Internet Access VPN program for generating its ruby.exe file. (For full transparency, this was only for 3-4 hours of rummaging their forum a while back when configuring their vpn for myself)
mytrashcan.exe was something I got of my own volition; it just allows me to modify my desktop recycle bin to whatever image i please and resize the bin on my desktop. Outside of adding a second or two on login time, I don't think it can affect anything.
The cpu chipset drivers are already updated directly from AMD's website. I've never thought of reenabling my device through the bios though, so I'll try that.
I do believe that my crashes are solely due to razer's keyboard driver, though: the reason I believe this is because I've had the screen flicker again recently (which normally after several a BSOD appears). I tried shutting down the razer synapse process and rebooting it, and the system worked fine for the rest of that session (5 hours, after which I stopped for the day).
-
Reply to johnbl
m
0
l
Related resources
- SolvedIrregular freezes on Windows 7... PSU or Motherboard ? Forum
- SolvedBSOD 0xa00001 windows 8.1 Forum
- SolvedWindows 8.1 random Crashes (no BSOD) & USB 3.0 stopped working on front panel only Forum
- SolvedWindows 8.1: BSOD on Wake: ntoskrnl.exe SYSTEM_SERVICE_EXCEPTION Forum
- SolvedWindows 8.1 Login Flickering, then BSOD. However Perfectly fine after restart every time? [Video] Forum
- SolvedExternal USB Drive Causes Bsod on Windows 8.1 (Page Fault In Non Paged Area) Forum
- Solvedbsod atikmdag.sys windows 8.1 Forum
- SolvedWindows 8.1 Software installation BSoD loop Forum
- SolvedBSOD KMODE_EXCEPTION_NOT_HANDLED Windows 8.1 Forum
- SolvedBSoD,Freezes,0xa000001,Display driver stopped responding Windows 8.1 Forum
- SolvedWindows 8.1 worked fine then crashed and now continuously reboots to BSOD. Forum
- SolvedBSOD windows 8.1 Forum
- SolvedWindows 8.1 atikmdag.sys BSOD. Forum
- SolvedWindows 8.1 BSOD- IRQL NOT LESS OR EQUAL Forum
- Solvedbrand new install of windows 8.1 and BSOD comes up saying SYSTEM_SERVICE_EXCEPTION Forum
- More resources
Read discussions in other Windows 8 categories
!