Windows 8 refreshed,"SYSTEM_SERVICE_EXCEPTION" BSOD

detection

Distinguished
Jul 20, 2014
10
0
18,510
Hi all,

I'm running a fairly new build I put together. It's been pretty much nothing but a headache from the beginning, but I thought I finally had something stable just before I got yet another BSOD. I just recently RMA'd my APU. I put the new one in a saw promising changes, but still had issues, so I "refreshed" my Windows 8 install and started again with drivers, programs, etc.

I seemed to be running smoothly until I had two issues (so far):

First: Was just browsing the web when I completely locked up. Cursor froze, CTRL+ALT+DEL didn't work, sleep didn't work. I had to hard reset.

Second: BSOD as named in title of thread.

There were two minidump files, you can see them here: https://www.dropbox.com/s/ucsa5ecgwh03ksf/minidumps.zip?dl=0

Would appreciate any insight as I'm not familiar with minidumps. Thanks.

ETA: Another lockup followed by another BSOD since posting thread. This BSOD was "DPC_WATCHDOG_VIOLATION... the another, "MEMORY_MANAGEMENT" - minidumps added to zip already linked.
 
Solution
if you windows was installed while the system had faulty ram, then your windows install would be corrupted.
Windows checks for some corrupted files because of the various malware/virus attacks, when it finds it, it calls a bugcheck to stop the system.

you will at least want to verify that your core windows files are ok and not corrupted. To do this you would run the system file checker.
start cmd.exe as an admin
sfc.exe /scannow (this will scan an repair your system files using a local backup copy)

if the utility indicates that it can not do the repair, that means that the backup copy is also corrupted. Happens, when a virus or pirate version of windows modified the hidden copy.

on windows 8.x you can fix this...
ok, two other bugchecks, one more in networking code and another
where I could not tell the cause,

i would still remove the USB webcam, and update my chipset drivers and BIOS if there is a update.


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

last time I looked at this type of problem, it was caused because one core was trying to install a usb driver for a network card, while the second core was attempting to use the network card. Problem was the first core got a failure while trying to install the USB network driver. Caused the usb port to stop working until a timeout occurred and the system bugchecked.

I would uninstall your webcam and usb network driver, and look for updated software and install them again. One at a time, reboot, test to make sure they work and install the second and reboot and make sure the second one works.

I would start with the network USB driver but make sure you have applied any updates listed below. Also, google on how to set windows device manager to show hidden devices, usb devices are hidden when removed but the driver is still there. If you show the hidden devices you can remove the driver.

there is also a tool that can help you. It is called usbview.exe and it comes with the windows standalone debugger, google "windows standalone debuggger" and you can download the debugger and the tool will be in the same directory. run it to see how winodows thinks your usb ports are configured.


==============
BugCheck 133, {0, 501, 500, 0}
DPC_WATCHDOG_VIOLATION (133)



for this bugcheck I would remove or update the webcam driver, then look at the motherboard vendors site and see if there are any chipset updates for your motherboard. to get updated usb 2.0 and usb 3.0 drivers. I would also look to see if there is a BIOS update in the last few months that corrects any USB problems.




first bugcheck was in network code
driver \SystemRoot\system32\DRIVERS\netr28x.sys Thu Jul 11 02:27:41 2013
(Ralink RT2860 series Wireless LAN Card)
but the stack looks messed up, so it may be a victim of corruption.
most of the time this will be cause because of underlying bugs in the USB drivers.

could be caused by a \SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
a Logitech USB Video Class Driver (WebCam)




machine info:
Manufacturer ASRock
Product FM2A75M Pro4+
BIOS Release Date 04/22/2014
BIOS Version P2.20

Processor ID 010f6300fffb8b17
Processor Version AMD A10-7850K APU with Radeon(TM) R7 Graphics
Processor Voltage 8fh - 1.5V
External Clock 100MHz
Max Speed 3700MHz
Current Speed 3700MHz

 

detection

Distinguished
Jul 20, 2014
10
0
18,510



Thanks so much for your reply! Sorry for my delay in responding; after creating this thread, I ran MemTest and found I DID have some bad RAM. I went through with an RMA and now have two new sticks in. Unfortunately that isn't the end of my saga and I am still having lockups often, and have had one "DPC_WATCHDOG_VIOLATION" BSOD so far.

I did update the Logitech driver. I also made sure there were no yellow exclamations in Device Manager. I didn't see any USB specific drivers in the chipset.

I downloaded the debugging tools but I'm not too sure what to do with them. You can see what USB Viewer shows here. You can also see my latest minidump here.

Thanks again!
 
if you windows was installed while the system had faulty ram, then your windows install would be corrupted.
Windows checks for some corrupted files because of the various malware/virus attacks, when it finds it, it calls a bugcheck to stop the system.

you will at least want to verify that your core windows files are ok and not corrupted. To do this you would run the system file checker.
start cmd.exe as an admin
sfc.exe /scannow (this will scan an repair your system files using a local backup copy)

if the utility indicates that it can not do the repair, that means that the backup copy is also corrupted. Happens, when a virus or pirate version of windows modified the hidden copy.

on windows 8.x you can fix this using the dism.exe command
dism.exe /online /cleanup-image /restorehealth

this command will restore the corrupted files from a trusted online source.

please note: this will only fix key windows files, everything you have installed while you had bad RAM may be corrupted
and show unexpected failures when you run the program. you often have to reinstall the Apps. if you did the build, i would wipe and re-install everything. And be sure to do a full format of your drive rather than a quick format.




 
Solution