Various BSOD's (hardware or software?)

Toggle sidebar Toggle sidebar
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Hi all...I bought this PC in January :

AMD FX 6300 3.5 GHz
RAM DD3 CORSAIR VENGEANCE 2x2 GB 1600 MHz
EVGA 430W 80+
ASRock 970 PRO 3 R2.0
XFX R7 260X 2GB

Since January my PC has a lot of BSODs but i can't find the cause...recently I found some errors with memtest over 1 block of ram, but using the other 1 (which is safe) the PC crashes anyway with BSODs...I have some minidump which I will upload here:

https://www.mediafire.com/folder/hn5nb78fw9ovu//minidump

Help me please! I will give you every things/info you'll need.

PS:I had w8.1, after I had reinstalled it,after that I had installed W7 with all drivers updated.

Prime 95 says that:

[Mon Jul 14 18:02:22 2014]
FATAL ERROR: Resulting sum was 8.643921016522246e+018, expected: 8.643921016522646e+018
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Mon Jul 14 18:08:07 2014]
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Sat Jul 19 18:08:47 2014]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Sat Jul 19 18:15:02 2014]
Self-test 8K passed!
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
 
Solution
M
i have same mobo, same processor, and same issue as well. i found a solution that work for me, and maybe work for you too. reset your bios settings, go to oc tweaker tab, set 2000mhz for nb frequency multiplier, set dram voltage manually. (my ram need 1.5v and automatic settings give me 1.68v)
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the graphics driver called its own bugcheck, most likely because of lack of proper power from the power supply.


Unknown bugcheck code (a0000001)
called by atikmdag+0x28ece

2: kd> lmvm atikmdag
start end module name
fffff880`110a2000 fffff880`11fb2000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Thu Apr 17 19:13:16 2014 (53508A3C)
CheckSum: 00EAEEE6
ImageSize: 00F10000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


I think this is a power issue with the graphics card not getting proper power
You should confirm the power is good make sure any power supply to graphics card power connections are well connected.
- also blow out any dust in the fans of the GPU
- swap out power supply if you have one to test with.

note: it the power supply is under rated, the GPU will pull too much power and it can cause the voltage to the CPU to drop too low and make your system reset for various reasons.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I would:
- remove any overclocks
- remove any overclocking drivers (AODDriver2.sys)
- run malwarebytes to confirm that you don't have malware
update: C:\Program Files (x86)\UltraISO\drivers\ISODrv64.sys Wed Nov 20 17:22:28 2013
update BIOS if you have one (yours looked like it was 2 months newer than the one listed on the website)

you might even just reset the bios to defaults and reconfigure.
I suggest this because the debugger indicates that you have Corsair CMZ4GX3M2A1600C9
memory running at 667Mhz rather than at 1600Mhz. You might want to check in to that
the other banks indicate that they are running at 0MHZ so I am not sure what is going on. (BIOS bugs, incorrect info???)

the second bugcheck I looked at was a corruption in TCPIP stack. unrelated to the first problem.

normally, i consider a powersupply under rated if it fails when not overclocking. I would stop all overclocking and retest to see if you get bugchecks. And you need to find out why the BIOS has strange settings for your memory.
(replace powersupply if you have one handy but I am not sure it caused your problem, it coould be a corrupted BIOS)










 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Well I haven't overclocks, I used malwarebytes some days ago and it didn't find anything..I have got the latest bios (1.50) (http://www.asrock.com/mb/AMD/970%20Pro3%20R2.0/?cat=Download&os=BIOS )Have I to reflesh it? For the 0mhz can the damaged ram block be the cause? (memtest found some errors in one block) I have another powersupply but it's old (500W) and I think there aren't 500w effective. For tcpip what can I do?
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
looks like you have a overclocking driver installed
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014
you might want to remove it, in case it is corrupting memory.

for the tcpip issue i would update
\SystemRoot\system32\DRIVERS\Rt64win7.sys Thu Apr 21 11:15:33 2011
your network driver from realtek

I will look at another memory dump.
How many memory sticks to you have installed? the debugger indicates 4 but only 1 working at 667Mhz
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the third bugcheck file is also network related and would require a updated network driver to resolve

the memory dumps have a list of internal drivers that also indicate the path. One of your bugcheck looked like the list of drivers were edited. Kind of strange, you might want to check for some kind of rootkit.
just not sure what would modify the path to the drivers in memory. (path to files removed, incorrect case on letters)
almost like something was attempting to fake the list of drivers.
 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
2 x 2 gb 1600 mhz, (dual channel).
AODDriver deleted.
To update my network driver where I will download it?Because the ASRock site says that the latest version is the same that I have.
For the bios have I to reflesh it?

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-for the netcard, look up the spec for your chip on your mother board, then you have to google the chip number to get to the realtek web site and find the current driver.
http://www.realtek.com.tw/downloads/ kind of hard to find the right section without the chip number

-I would not reflash the BIOS but just try and reset it to defaults and reconfigure it.

maybe the info reported in the memory dump is just incorrect. You might want to run a third party tool to see what it thinks your memory is set to.

at this point I would remove as many 3rd party drivers as I could, make sure you windows is updated
and run a system file check and chkdsk on your OS drive
start cmd.exe as a admin
sfc.exe /scannow (checks for corruption in core windows files)

you should remove all of your memory .dmp files (and just put up any new ones if you get another bugcheck)






 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Sorry for my ignorance but what do you mean for third party tools?

PS:TDS Killer didn't find anything
ps2: Driver update, now I have the 7.86 ( before 7.04)
 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510


new BSOD https://www.mediafire.com/?u6d7ichldx3d66w
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
thinking about it my bet is on the USB driver corrupting memory. I would look for a update to the two etron drivers listed below. You may even want to disable the hardware in bios and remove the drivers if you have other usb ports to use. (just to help isolate the problem, if you can not find driver updates)

check this driver for your usb http://www.etron.com/en/products/u3hc.php
at least the file date is 8/28/2013 maybe it is a update to the one you have (july 16 2013).

------------------
device driver bug or a corruption in the memory area of one device driver.
here is a list of suspect drivers:
AtihdW76 \SystemRoot\system32\drivers\AtihdW76.sys Tue Sep 24 17:23:49 2013
atikmdag \SystemRoot\system32\DRIVERS\atikmdag.sys Fri Dec 06 13:19:43 2013
atikmpag \SystemRoot\system32\DRIVERS\atikmpag.sys Fri Dec 06 12:21:45 2013
EtronHub3 \SystemRoot\System32\Drivers\EtronHub3.sys Tue Jul 16 23:23:48 2013
EtronXHCI \SystemRoot\System32\Drivers\EtronXHCI.sys Tue Jul 16 23:23:45 2013
ISODrv64 \??\C:\Program Files (x86)\UltraISO\drivers\ISODrv64.sys Wed Nov 20 17:22:28 2013

- also confirm you have done all of the windows updates and rebooted

I would update or remove any of these I could. (there are updated to the graphics driver)
I would also go to device manager and disable the AMD high definition sound driver unless I was using sound via a monitor directly from the video card.

then really confirm your BIOS settings for your memory chip are correct


now retest and see if you get another bugcheck, and post it if you do.
(next you will have to use verifier.exe to set some flags and increase the memory dump to a full memory dump to get proper debug info to see what driver is messing up (if it is a driver and not hardware issues))

----------------
BIOS reports 2 sticks of Corsair
Speed 667MHz
Part Number CMZ4GX3M2A1600C9
in banks A1_BANK1 and A1_BANK 3

(should check that the speed setting and memory timings are correct in BIOS)
9-9-9-24 at 1.5 Volts DDR3 1600MHz
-------------







 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Well...Unistalled ultraiso.
Unistalled video drivers and reinstalled bu XFX CD
Unistalled usb drivers and reinstalled by the site.
Disabled AMD High definition sound driver.
Loaded XMP 1.2 Profile(CPU-Z said DRAM Frequency 798.2 MHz)
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
looks like one of your processors in your CPU hung. Unable to tell why from a minidump, need a kernel dump
You might want to check your voltages and clock settings to your CPU.

confirm memtest86 booted from a disk works ok?

remove supperantispyware from 2011:
fffff880`02c56000 fffff880`02c60000 SASDIFSV64 \??\C:\Program Files\SUPERAntiSpyware\SASDIFSV64.SYS Thu Jul 21 16:03:00 2011 (4E28B024)
fffff880`02c4c000 fffff880`02c56000 SASKUTIL64 \??\C:\Program Files\SUPERAntiSpyware\SASKUTIL64.SYS Tue Jul 12 14:00:01 2011 (4E1CB5D1)

you might also remove
C:\Windows\system32\drivers\MBAMSwissArmy.sys Thu Mar 20 15:12:35 2014
and
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Thu Jun 06 01:56:26 2013
is still installed (overlclocking software)



 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Well I'm here again...I had find some errors with memtest86+ on 1 block of RAM, I sent them on warranty and they are back some days ago but the BSODs continue to appears...These are some screens:
rvoJQ7p.jpg

ooT3HGs.jpg

QbvRSKM.jpg
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
one of the drivers was the graphics driver, one was the ethernet driver that bugchecked. I can not tell the cause of the others. Generally bugchecks in different systems indicated memory corruption that can be caused by hardware or a bad device driver.

you have to run various hardware tests and have them pass. Memtest86, prime95, seatools are good examples. if these pass you have to look at the software that can cause the corruption. Most of the time you start with low level software update the BIOS, update the CPU chipset drivers. update any suspect non microsoft drivers, remove software that you don't require. After that you have to run verifier.exe with debug flags to have windows bugcheck when a driver attempts to corrupt another drivers memory. It will bugcheck and name the driver that caused the corruption.
here is info on running verifier
http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

please note: some issues require a kernel mode memory dump rather than a minidump to figure out which driver caused them.
 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
[Mon Sep 08 17:38:49 2014]
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
[Mon Sep 08 17:45:00 2014]
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 560K passed!
[Mon Sep 08 17:51:14 2014]
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 160K passed!
[Mon Sep 08 17:57:41 2014]
Self-test 160K passed!
Self-test 160K passed!
Self-test 160K passed!
Self-test 160K passed!
Self-test 640K passed!
FATAL ERROR: Resulting sum was 1.582000179908949e+019, expected: 1.582000179908957e+019
Hardware failure detected, consult stress.txt file.
[Mon Sep 08 18:04:12 2014]
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Mon Sep 08 18:09:43 2014]
Self-test 224K passed!
Self-test 224K passed!
Self-test 224K passed!
Self-test 224K passed!
[Mon Sep 08 18:15:25 2014]
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
[Mon Sep 08 18:21:05 2014]
Self-test 256K passed!
Self-test 256K passed!
Self-test 256K passed!
Self-test 256K passed!
[Mon Sep 08 18:26:14 2014]
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
[Mon Sep 08 18:31:56 2014]
Self-test 320K passed!
Self-test 320K passed!
Self-test 320K passed!
Self-test 320K passed!
[Mon Sep 08 18:37:51 2014]
Self-test 896K passed!
Self-test 896K passed!
Self-test 896K passed!
Self-test 896K passed!
[Mon Sep 08 18:43:50 2014]
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
[Mon Sep 08 18:49:33 2014]
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
[Mon Sep 08 18:55:10 2014]
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
[Mon Sep 08 19:00:24 2014]
Self-test 144K passed!
Self-test 144K passed!
Self-test 144K passed!
Self-test 144K passed!
[Mon Sep 08 19:05:57 2014]
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
[Mon Sep 08 19:11:20 2014]
Self-test 192K passed!
Self-test 192K passed!
Self-test 192K passed!
Self-test 192K passed!
[Mon Sep 08 19:16:53 2014]
Self-test 672K passed!
Self-test 672K passed!
Self-test 672K passed!
Self-test 672K passed!
[Mon Sep 08 19:22:15 2014]
Self-test 240K passed!
Self-test 240K passed!
Self-test 240K passed!
Self-test 240K passed!
[Mon Sep 08 19:28:15 2014]
Self-test 768K passed!
Self-test 768K passed!
Self-test 768K passed!
Self-test 768K passed!
[Mon Sep 08 19:33:27 2014]
Self-test 288K passed!
Self-test 288K passed!
Self-test 288K passed!
Self-test 288K passed!
[Mon Sep 08 19:39:31 2014]
Self-test 864K passed!
Self-test 864K passed!
Self-test 864K passed!
Self-test 864K passed!
[Mon Sep 08 19:44:45 2014]
Self-test 336K passed!
Self-test 336K passed!
Self-test 336K passed!
Self-test 336K passed!
[Mon Sep 08 19:50:25 2014]
Self-test 960K passed!
Self-test 960K passed!
Self-test 960K passed!
Self-test 960K passed!
[Mon Sep 08 19:55:34 2014]
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
Self-test 400K passed!
[Mon Sep 08 20:01:29 2014]
Self-test 1024K passed!
Self-test 1024K passed!
Self-test 1024K passed!
Self-test 1024K passed!
[Mon Sep 08 20:06:58 2014]
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
[Mon Sep 08 20:12:29 2014]
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
Self-test 128K passed!
[Mon Sep 08 20:17:47 2014]
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
Self-test 560K passed!
[Mon Sep 08 20:23:22 2014]
Self-test 160K passed!
Self-test 160K passed!
Self-test 160K passed!
Self-test 160K passed!
[Mon Sep 08 20:29:10 2014]
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
Self-test 640K passed!
[Mon Sep 08 20:34:37 2014]
Self-test 224K passed!
Self-test 224K passed!
Self-test 224K passed!
Self-test 224K passed!
[Mon Sep 08 20:40:19 2014]
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
Self-test 720K passed!
[Mon Sep 08 20:45:58 2014]
Self-test 256K passed!
Self-test 256K passed!
Self-test 256K passed!
Self-test 256K passed!
[Mon Sep 08 20:51:07 2014]
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
[Mon Sep 08 20:56:49 2014]
Self-test 320K passed!
Self-test 320K passed!
Self-test 320K passed!
Self-test 320K passed!
[Mon Sep 08 21:02:50 2014]
Self-test 896K passed!
Self-test 896K passed!
Self-test 896K passed!
Self-test 896K passed!
[Mon Sep 08 21:08:51 2014]
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
Self-test 384K passed!
[Mon Sep 08 21:14:18 2014]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 512K passed!
[Mon Sep 08 21:20:59 2014]
Self-test 512K passed!
Self-test 512K passed!
Self-test 144K passed!
Self-test 576K passed!
[Mon Sep 08 21:26:12 2014]
Self-test 144K passed!
Self-test 144K passed!
Self-test 192K passed!
[Mon Sep 08 21:31:43 2014]
Self-test 576K passed!
Self-test 576K passed!
Self-test 672K passed!
Self-test 240K passed!
 
Upvote 0 Downvote
M

mishima1992

Reputable
Sep 15, 2014
7
0
4,520
i have same mobo, same processor, and same issue as well. i found a solution that work for me, and maybe work for you too. reset your bios settings, go to oc tweaker tab, set 2000mhz for nb frequency multiplier, set dram voltage manually. (my ram need 1.5v and automatic settings give me 1.68v)
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom