BSOD everyday.

[Emilvooo]

Got again some BSOD's... I re-do the AMD driver thingy.. after that still BSOD. <

 

[usasma]

The first memory dump (analyzed by blueelvis) is a STOP 0xA

The next set of memory dumps:
3 STOP 0x1E
A STOP 0xA

From the previous memory dumps:
A STOP 0x3B
A STOP 0xC7

From the WER section of MSINFO32:
A STOP 0xF7 on 5/23
A STOP 0x139 on 5/25

From the latest 2 memory dumps:
A STOP 0x3B
A STOP 0x1E

The lack of a pattern is usually indicative of low level/hardware problems. Here's my canned speech about it:

Out of 11 memory dumps there were 6 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers) - and older systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Please start with these free hardware diagnostics: Hardware Diagnostics

Also, STOP 0x1E errors are more likely to be hardware/compatibility errors than most other BSOD errors.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

In summary:
- remove AMD Overdrive
- perform the hardware diagnostics: Hardware Diagnostics
- let us know the results and we'll move on from there.


B]Analysis:[/B]
The following is for informational purposes only.

[FONT=lucida console]**************************Wed May 28 16:32:46.070 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-19640-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 0:08:55.807[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]3B, {c0000005, fffff801de6d15fc, ffffd0015cdce570, 0}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801de6d15fc, Address of the instruction which caused the bugcheck
Arg3: ffffd0015cdce570, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_ONE_BIT[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 28 16:23:22.471 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-19703-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 0:40:03.207[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]1E, {ffffffffc000001d, fffff800c1731047, fffff800c19dca00, 3f}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
Arguments: 
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff800c1731047, The address that the exception occurred at
Arg3: fffff800c19dca00, Parameter 0 of the exception
Arg4: 000000000000003f, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c000001d
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_LARGE_32[/B]
  BIOS Version                  P1.50
  BIOS Release Date             10/02/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Wed May 28 16:32:46.070 2014 (UTC - 4:00)**************************
speedfan.sys         Sat Dec 29 15:59:35 2012 (50DF59B7)
SAlpham64.sys        Fri May 31 10:19:10 2013 (51A8B15E)
dump_storahci.sys    Thu Aug 22 07:40:39 2013 (5215F8B7)
[COLOR=RED][B]AODDriver2.sys       Wed Sep 11 23:36:40 2013 (523136C8)[/B][/COLOR]
RTKVHD64.sys         Tue Dec 10 07:16:11 2013 (52A7060B)
SteelBus64.sys       Wed Jan  8 12:00:12 2014 (52CD841C)
Rt630x64.sys         Tue Feb 18 06:44:16 2014 (53034790)
aswHwid.sys          Tue Apr  8 11:43:26 2014 (5344191E)
atikmpag.sys         Tue Apr 15 21:07:05 2014 (534DD7B9)
atikmdag.sys         Tue Apr 15 22:13:17 2014 (534DE73D)
aswRdr2.sys          Thu Apr 17 07:02:56 2014 (534FB4E0)
aswMonFlt.sys        Thu Apr 17 07:04:01 2014 (534FB521)
aswRvrt.sys          Thu Apr 17 07:04:41 2014 (534FB549)
aswVmm.sys           Thu Apr 17 07:04:55 2014 (534FB557)
aswSnx.sys           Mon May  5 04:04:42 2014 (5367461A)
aswSP.sys            Mon May  5 04:11:11 2014 (5367479F)
aswStm.sys           Mon May  5 04:11:48 2014 (536747C4)
[/FONT]

http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=SAlpham64.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=SteelBus64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
aswHwid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys

 

[lifetec]

Did you switched your memory modules to Kingston.

Asrock advice (see manual) to install 1866 modules in Slot A2 and B2, you installed your modules in A1 and B1.
Please put them in the adviced slots.

1. Please install the memory module into the slots DDR3_A2 and
DDR3_B2 for the first priority.

2. If you want to install two memory modules, for optimal compatibility and reliability, it is recommended to install them either in the set of slots DDR3_A1 and DDR3_B1, or in the set of slots DDR3_A2 and DDR3_B2.

3. If only one memory module or three memory modules are installed in the DDR3 DIMM slots on this motherboard, it is unable to activate the Dual Channel Memory Technology.

4. If a pair of memory modules is NOT installed in the same Dual Channel, for example, installing a pair of memory modules in DDR3_A1 and DDR3_A2, it is unable to activate the Dual Channel Memory Technology .

5. It is not allowed to install a DDR or DDR2 memory module into DDR3 slot; otherwise, this motherboard and DIMM may be damaged.


6. If you adopt DDR3 2100/1866/1800/1600 memory modules on this motherboard, it is recommended to install them on DDR3_A2 and DDR3_B2 slots.

It seems that Asrock 970 pro3 R2.0 mainboards are sensitive to low power PSU. What brand and wattage are you using.?

 

[Emilvooo]

Did you switched your memory modules to Kingston.

Asrock advice (see manual) to install 1866 modules in Slot A2 and B2, you installed your modules in A1 and B1.
Please put them in the adviced slots.

1. Please install the memory module into the slots DDR3_A2 and
DDR3_B2 for the first priority.

2. If you want to install two memory modules, for optimal compatibility and reliability, it is recommended to install them either in the set of slots DDR3_A1 and DDR3_B1, or in the set of slots DDR3_A2 and DDR3_B2.

3. If only one memory module or three memory modules are installed in the DDR3 DIMM slots on this motherboard, it is unable to activate the Dual Channel Memory Technology.

4. If a pair of memory modules is NOT installed in the same Dual Channel, for example, installing a pair of memory modules in DDR3_A1 and DDR3_A2, it is unable to activate the Dual Channel Memory Technology .

5. It is not allowed to install a DDR or DDR2 memory module into DDR3 slot; otherwise, this motherboard and DIMM may be damaged.


6. If you adopt DDR3 2100/1866/1800/1600 memory modules on this motherboard, it is recommended to install them on DDR3_A2 and DDR3_B2 slots.

It seems that Asrock 970 pro3 R2.0 mainboards are sensitive to low power PSU. What brand and wattage are you using.?

Got a Seasonic
S12II-520 Bronze.

And okay i will try that.

 

[Emilvooo]

The first memory dump (analyzed by blueelvis) is a STOP 0xA

The next set of memory dumps:
3 STOP 0x1E
A STOP 0xA

From the previous memory dumps:
A STOP 0x3B
A STOP 0xC7

From the WER section of MSINFO32:
A STOP 0xF7 on 5/23
A STOP 0x139 on 5/25

From the latest 2 memory dumps:
A STOP 0x3B
A STOP 0x1E

The lack of a pattern is usually indicative of low level/hardware problems. Here's my canned speech about it:

Out of 11 memory dumps there were 6 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers) - and older systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Please start with these free hardware diagnostics: Hardware Diagnostics

Also, STOP 0x1E errors are more likely to be hardware/compatibility errors than most other BSOD errors.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

In summary:
- remove AMD Overdrive
- perform the hardware diagnostics: Hardware Diagnostics
- let us know the results and we'll move on from there.


B]Analysis:[/B]
The following is for informational purposes only.

[FONT=lucida console]**************************Wed May 28 16:32:46.070 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-19640-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 0:08:55.807[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]3B, {c0000005, fffff801de6d15fc, ffffd0015cdce570, 0}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000003B"]SYSTEM_SERVICE_EXCEPTION (3b)[/URL]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801de6d15fc, Address of the instruction which caused the bugcheck
Arg3: ffffd0015cdce570, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_ONE_BIT[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 28 16:23:22.471 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-19703-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 0:40:03.207[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]1E, {ffffffffc000001d, fffff800c1731047, fffff800c19dca00, 3f}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
Arguments: 
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff800c1731047, The address that the exception occurred at
Arg3: fffff800c19dca00, Parameter 0 of the exception
Arg4: 000000000000003f, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c000001d
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_LARGE_32[/B]
  BIOS Version                  P1.50
  BIOS Release Date             10/02/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Wed May 28 16:32:46.070 2014 (UTC - 4:00)**************************
speedfan.sys         Sat Dec 29 15:59:35 2012 (50DF59B7)
SAlpham64.sys        Fri May 31 10:19:10 2013 (51A8B15E)
dump_storahci.sys    Thu Aug 22 07:40:39 2013 (5215F8B7)
[COLOR=RED][B]AODDriver2.sys       Wed Sep 11 23:36:40 2013 (523136C8)[/B][/COLOR]
RTKVHD64.sys         Tue Dec 10 07:16:11 2013 (52A7060B)
SteelBus64.sys       Wed Jan  8 12:00:12 2014 (52CD841C)
Rt630x64.sys         Tue Feb 18 06:44:16 2014 (53034790)
aswHwid.sys          Tue Apr  8 11:43:26 2014 (5344191E)
atikmpag.sys         Tue Apr 15 21:07:05 2014 (534DD7B9)
atikmdag.sys         Tue Apr 15 22:13:17 2014 (534DE73D)
aswRdr2.sys          Thu Apr 17 07:02:56 2014 (534FB4E0)
aswMonFlt.sys        Thu Apr 17 07:04:01 2014 (534FB521)
aswRvrt.sys          Thu Apr 17 07:04:41 2014 (534FB549)
aswVmm.sys           Thu Apr 17 07:04:55 2014 (534FB557)
aswSnx.sys           Mon May  5 04:04:42 2014 (5367461A)
aswSP.sys            Mon May  5 04:11:11 2014 (5367479F)
aswStm.sys           Mon May  5 04:11:48 2014 (536747C4)
[/FONT]

http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=SAlpham64.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=SteelBus64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
aswHwid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys

I cant find the AODdriver in device manager? :s

 

[usasma]

Try this:

1) Create a Restore Point using System Restore
2) Create a Repair disc (Recovery Drive in Win8.1):
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns for Windows) and use it to disable any instances of AODDriver2.sys that are starting (or any other AMD OverDrive entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of AODDriver2.sys (or any other AMD Overdrive entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of AODDriver2.sys or any other AMD OverDrive entries are disabled.
7) Go to c:\program files\ati technologies\ati.ace\fuel\amd64 and rename the AODDriver2.sys driver to AODDriver2.BAD.

In the event that the system doesn't boot:

1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename AODDriver2.BAD to AODDriver2.sys
2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

 

[Emilvooo]

Try this:

1) Create a Restore Point using System Restore
2) Create a Repair disc (Recovery Drive in Win8.1):
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns for Windows) and use it to disable any instances of AODDriver2.sys that are starting (or any other AMD OverDrive entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of AODDriver2.sys (or any other AMD Overdrive entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of AODDriver2.sys or any other AMD OverDrive entries are disabled.
7) Go to c:\program files\ati technologies\ati.ace\fuel\amd64 and rename the AODDriver2.sys driver to AODDriver2.BAD.

In the event that the system doesn't boot:

1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename AODDriver2.BAD to AODDriver2.sys
2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

Can you also use a disc instead of a usb ?

 

[usasma]

Not in 8.1 - sorry!

 

[Emilvooo]

Not in 8.1 - sorry!

Could it be the PSU then? I have no idea... still geting BSOD's...

I will add a rar again. I hope you guys can help me because im getting really sick of it.. And my english is not that good so maby i missed some thing what i needed to do..

 

[usasma]

Hardware diagnostics: Hardware Diagnostics
If they all pass, then:
Troubleshooting by hardware stripdown: Hardware Stripdown Troubleshooting

PSU and motherboard are usually the last things tested - as they're a pain to replace (and usually can't be reliably tested on their own).

 

[azasadny]

Any updates? I'm having similar BSOD issues with a system I built for my son's girlfriend. I'll start the troubleshooting process later this week...

 

[Emilvooo]

Run prime for a few hours no errors. Wil run some other hardware diagonoticts later. Also run Furmark dindt get any errors or something like that. It's also not the HDD....

What could id be, it have to be the mainboard or psu..

 

[Emilvooo]

Saw this on the ASROCK site and then my motherboard.

For cooling the CPU and its surrounding components, please install a CPU cooler with a top-down blowing design.

Im using the stock heatsink, could this than be the problem?

 

[usasma]

Finish hardware diagnostics: Hardware Diagnostics
Then start Troubleshooting by Stripdown: Hardware Stripdown Troubleshooting

That will leave you with few parts that haven't been tested.
Then try replacements for each one (doing PSU and mobo last).

A bad cooler will cause the CPU to overheat - the temp monitor I suggested will tell you if you're overheating.
HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

 

[Emilvooo]

I dont know what i did, but i have now for 6 days no BSOD..

 

[azasadny]

My BSOD's were caused by setting the SATA drive as "AHCI" instead of "IDE". Sonce changing it, I haven't had any BSOD's and I've run Prime95 and Furmark for 24 hours...

 

[Emilvooo]

My BSOD's were caused by setting the SATA drive as "AHCI" instead of "IDE". Sonce changing it, I haven't had any BSOD's and I've run Prime95 and Furmark for 24 hours...

I did cleaned my pc up from outside/inside and redid the cables etc. Maby its bcs i did that but yehg..