BSOD and random freezes

[AxelBlade]

I keep getting BSOD and random freezes that make me unable to use the computer, so i have to restart it and hope that won't happen again. Happens randomly, there is not an specific trigger to this. It's driving me crazy!

Leaving the minidump file to make it easier!

Thx in advance!

==================================================
Dump File : 080415-8234-01.dmp
Crash Time : 8/4/2015 10:48:25 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff802`848d3d72
Parameter 3 : ffffd001`795f89f0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16393 (th1_st1.150717-1719)
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080415-8234-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 281,024
Dump File Time : 8/4/2015 10:49:20 PM
==================================================

 

[johnbl]

basically a driver tried to access a bad memory address.
error code = 0xc0000005

can not tell why with the info provided.

in general: run memtest86 to confirm your memory timings in BIOS are correct and your system memory is ok
also, remove any overclocking in BIOS or in software.

sometimes you can figure this out by looking at the driver table in the memory dump file with the windows debugger.
put the memory dump file C:\Windows\Minidump\080415-8234-01.dmp
most often for this error you have to turn on more debugging (verifier.exe and change the memory dump type to kernel memory dump)

 

[AxelBlade]

Just checked my memory timings and they were not correct :/, also removed the OC, back to default. Going to use the computer for a while and see if it solved the problem! I'll post something later or tomorrow!

Also, i tried opening the dmp file with the windows debugger, when i do it, a bunch or random characters appears

I'm attaching it here to see if it helps http://

 

[johnbl]

your memory dump works ok in my debugger.

looks like you have a overclocking driver installed at:
D:\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014

two old drivers ?
Ideazon ZBoard/Ideazon ZBoard Fang MM USB HID
\SystemRoot\System32\drivers\Alpham164.sys Mon Jul 23 00:57:03 2007
\SystemRoot\System32\drivers\Alpham264.sys Tue Mar 20 02:51:03 2007
http://steelseries.com/downloads

I would remove the software overclock also.

 

[AxelBlade]

Regarding to the overclocking driver, actually it's just only an option in the Catalyst control center (amd drivers).

I just disabled it http://prntscr.com/815q9c

I also uninstalled the keyboard drivers and downloaded the new ones from the webpage.

I've been using the computer for 2 hours straight without any BSOD so far. I'll try playing some random games and see what happens!

I'll keep in touch

EDIT: Been running prime95 to test the stability, looks fine. Should i try with something different to check how stable is my system?

 

[AxelBlade]

Okay, looks like the random BSOD's are gone, but now something new is happening. Now for some reason, all my usb's crash after using it for a while (been using it already for 5 hours without any problem). Any clue of what can be happening?

 

[johnbl]

my wife's machine is rebooting once a day. I just looked at it and there is a live kd dump that indicates it is a bug in the USB 3.0 support for the asmedia usb controller chip in her machine. It was kind of rude to reboot the machine without showing a bugcheck code or making a normal memory dump. I found the live kd dump by searching her drive for files with .dmp file names and took a look in the debugger.

I moved her USB devices to a USB 2.0 controller, went into BIOS and disable the asmedia usb 3.0 chip.
Will see if that helps.

also note: no error in the error log before the reboot, no indication of a bugcheck in the log.
but the details were saved in a file USBXHCI-20150804-1706.dmp

I figure BIOS bug or a chipset with bugs that microsoft has not worked around in there version of the driver.
(the machine is one BIOS patch old, with no indications of what was fixed in the new patch other than a CPU update)

Okay, looks like the random BSOD's are gone, but now something new is happening. Now for some reason, all my usb's crash after using it for a while (been using it already for 5 hours without any problem). Any clue of what can be happening?

 

[AxelBlade]

Okay, thank you anyway, i'm not geting any kind of error log as well...

Atleast the main problem is solved! Thank you again!