SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

#21
Re: windwos7 newupdeta

Yes, we'll need Driver Verifier running again to verify changes after the Symantec uninstall.
 


#22
Re: windwos7 newupdeta

Hi

I removed WINCPAP i don't even know why its on there!

I removed APP charger, because that was the most recent version...
 


#23
Re: windwos7 newupdeta

Don't bother with App Charger at all. It's a gimmick item that comes with some motherboards that actually serves no purpose. You can still charge up devices through USB ports without it. All I've seen it do is cause problems.

Again, turn on Driver Verifier and we'll see what we can do from there.
 


#24
Re: windwos7 newupdeta

Hi

I've attached another dump. I've also turned on driver verifier as per instructions - but i'll obviously need to wait for the system to crash before I can post that result.

I really appreciate all your help with this.
 


Attachments

#25
Re: windwos7 newupdeta

Make sure to verify (punny) that Driver Verifier is active by opening it back up and selecting "Display existing settings". If no drivers are listed, then DV is disabled.

I almost had something analyzing one of your crashdumps, but alas, it was only a minidump, so it stopped me in my tracks right before I getting the dirt on the suspect item.

I do find a bit of a pattern with your crashdumps, and that's your graphics drivers, and in your latest crash it's actually flooding its resource area (the thread stack) with junk, causing the BSOD. It looks like the graphics driver is pretty up-to-date (update again if available), There is a good possibility there's a bug in either the motherboard BIOS/chipset drivers, or the graphics drivers, or moreso likely that the graphics card itself is bad. If you want to really test it out, remove the card and enable the Intel onboard graphics and test system stability there. If the system somehow seems to be stable again for an extended period of time, install the card again and check once more. If system destabilizes, it's time to get a new card. There is the offchance that the motherboard just doesn't work well with that specific card, or that it has a problem with your SLI setup (or there's an Nvidia driver bug for SLI). Again, try altering your graphics configuration and test inbetween each change to verify stability.
 


#26
Re: windwos7 newupdeta

Hi Thanks for the extra info, i've verified the settings, but it hasn't BSOD'd yet....

Could it be something to do with the GPU's overheating do you think?

The funny thing is though, its usually quite stable under load with the GPU's it seems to only have issues when the comp is idling - i 've yet to have a BSOD under load - Playing a Game, watching a Blu Ray....

To eliminate SLI as the issue i've had it turned off for the last few days, its not made any difference to the BSOD's...
 


#28
Re: windwos7 newupdeta

I got so sick of trying to work out what it was I reloaded everything (except the items you said to leave off)

Here's a new dump, of a reformatted system.... View attachment W7F_11-05-2013 Mark 2.zip
 


#29
Re: windwos7 newupdeta

any other ideas on what it could be? bad / inadequate psu??? ssd failure?
 


#30
Re: windwos7 newupdeta

Anyone? Please??

I have no idea what to do!!!!!!!!!!!
 


usasma

Fantastic Member
Microsoft Community Contributor
#31
Re: windwos7 newupdeta

Only 45 Windows Updates installed. Most systems have 66 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
Out of 7 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 - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

I would first update the wired network driver listed below (Broadcom NetLink Gigabit Ethernet). If the BSOD's continue after that, then I'd start with hardware diagnostics (here's a list of the one's that I suggest: Hardware Diagnostics )

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

k57nd60a.sys Wed Oct 19 16:17:36 2011 (4E9F3060)
Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys



Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sat May 11 08:38:55.323 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-16093-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 3:23:13.959[/B]
Probably caused by :[B]cdd.dll ( cdd!CDDPDEV::ProcessGDIDirtyList+48 )[/B]
BugCheck [B]50, {fffffaff12ac9170, 1, fffff800c552d4c6, 2}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arguments: 
Arg1: fffffaff12ac9170, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800c552d4c6, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]AV_cdd!CDDPDEV::ProcessGDIDirtyList[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 05:15:21.726 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-13375-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:11:36.362[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsOpenAttribute+30b )[/B]
BugCheck [B]24, {b50019060b, fffff8801f35d518, fffff8801f35cd50, fffff880017871ab}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000024]NTFS_FILE_SYSTEM (24)[/url]
Arguments: 
Arg1: 000000b50019060b
Arg2: fffff8801f35d518
Arg3: fffff8801f35cd50
Arg4: fffff880017871ab
PROCESS_NAME:  TiWorker.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]0x24_Ntfs!NtfsOpenAttribute[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 05:03:25.837 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-12671-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:00:53.474[/B]
Probably caused by :[B]fileinfo.sys ( fileinfo!FIStreamLogForNL+1fe )[/B]
BugCheck [B]C2, {7, 11c1, 5150107, fffff8a00a230ec0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C2]BAD_POOL_CALLER (c2)[/url]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 00000000000011c1, (reserved)
Arg3: 0000000005150107, Memory contents of the pool block
Arg4: fffff8a00a230ec0, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_FMfn
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]0xc2_7_FMfn_fileinfo!FIStreamLogForNL[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 05:02:09.391 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-12546-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:03:42.032[/B]
Probably caused by :[B]win32k.sys ( win32k!EngUnmapFontFileFD+7e8 )[/B]
BugCheck [B]50, {fffffa000d499c70, 0, fffff80371307c56, 2}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arguments: 
Arg1: fffffa000d499c70, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80371307c56, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID: [B]AV_win32k!EngUnmapFontFileFD[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 04:57:26.906 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-14078-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:05:16.542[/B]
*** ERROR: Module load completed but symbols could not be loaded for WdFilter.sys
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+8f6 )[/B]
BugCheck [B]19, {3, fffff8a0154da6f0, fffff8a0114da6f0, fffff8a0154da6f0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000019]BAD_POOL_HEADER (19)[/url]
Arguments: 
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a0154da6f0, the pool entry being checked.
Arg3: fffff8a0114da6f0, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a0154da6f0, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID: [B]0x19_3_nt!ExDeferredFreePool[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 04:40:48.029 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-12531-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:02:23.665[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+148b9 )[/B]
BugCheck [B]1E, {ffffffffc0000005, 1000000, 8, 1000000}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000001000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000001000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_X
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000005_X_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/2013
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 04:01:02.447 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051113-13281-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16551.amd64fre.win8_gdr.130306-1502
System Uptime:[B]0 days 0:17:17.085[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+371e2 )[/B]
BugCheck [B]1A, {41793, fffff683fbd59fd0, 1fb, 1fa}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Arguments: 
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff683fbd59fd0
Arg3: 00000000000001fb
Arg4: 00000000000001fa
BUGCHECK_STR:  0x1a_41793
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID: [B]0x1a_41793_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  P2.70
  BIOS Release Date             04/18/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.
Code:
[font=lucida console]**************************Sat May 11 08:38:55.323 2013 (UTC - 4:00)**************************
[COLOR=RED][B]k57nd60a.sys                Wed Oct 19 16:17:36 2011 (4E9F3060)[/B][/COLOR]
athrx.sys                   Wed Mar 21 23:26:22 2012 (4F6A9BDE)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
EtronXHCI.sys               Tue Jul  3 07:00:15 2012 (4FF2D0BF)
EtronHub3.sys               Tue Jul  3 07:00:21 2012 (4FF2D0C5)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
igdkmd64.sys                Wed Dec 12 19:42:26 2012 (50C92472)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
nvlddmkm.sys                Thu Mar 14 21:37:00 2013 (51427B3C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 05:02:09.391 2013 (UTC - 4:00)**************************
bxvbda.sys                  Mon Jul 23 19:30:50 2012 (500DDEAA)
evbda.sys                   Tue Jul 24 08:22:19 2012 (500E937B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 04:40:48.029 2013 (UTC - 4:00)**************************
nvlddmkm.sys                Fri Jan 18 08:22:15 2013 (50F94C87)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 11 04:01:02.447 2013 (UTC - 4:00)**************************
intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
intelide.sys                Wed Jul 25 22:29:52 2012 (5010ABA0)
[/font]
http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys
http://www.carrona.org/drivers/driver.php?id=athrx.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=EtronXHCI.sys
http://www.carrona.org/drivers/driver.php?id=EtronHub3.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=bxvbda.sys
http://www.carrona.org/drivers/driver.php?id=evbda.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
 


#32
Re: windwos7 newupdeta

There's problems with your hardware, it's just a matter of determining what hardware is bugging out. Unfortunately software diagnostic tests can only go so far. I noticed you said you tested with them but I don't think I ever asked you how long per test. Here's what I usually recommend to start off with:

RAM: Memtest86+ - 7+ passes (1 pass = all tests 1x)
CPU: Prime95 - Torture Test; Blend; overnight (9+ hours)
Drives: Seatools - All basic tests aside from the Fix all, Long generic or the advanced ones. Also provide us a screenshot of CrystalDiskInfo output.

All of these are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better. Last, make sure that when running Prime95 that you check temps during first 30minutes or so to see if temps are stable. Prime95 runs very hot so be sure your cooling can handle it before letting it run extensively.

Oh, btw, what PSU do you have anyways?

If hardware testing is done correctly and not coming up with anything, the problem is usually the PSU or motherboard. Replace both, starting with the PSU.
 


Last edited:
#33
Re: windwos7 newupdeta

I left Memtest86+ running and it did 10 passes with no errors
Prime95 ran for 12 hours
Seatools report no problems with the Driver, and I've tried all the test with it.

I have a Silverstone Strider Plus 750w PSU
 


#34
Re: windwos7 newupdeta

I have personally never heard of the Silverstone brand. Though I looked up the PSU and it appears discontinued. I hope it's not because of a defect in design. At least you have enough wattage output for the system.

We can't really go any further from here. You're going to have to pick either the motherboard or the PSU and buy a replacement and hope it's the correct choice. There's no diagnostic procedure for these items besides buying a good multimeter or high dollar PSU tester (the ones that adds load) and testing the PSU with it, or a motherboard diagnostic kit (also expensive). At least we can narrow it down to these two items.
 


#35
Re: windwos7 newupdeta

Really?? Still widely available here in Australia and came with many recommendations from lots of people.

I bought a new Mobo Asus Mavimus V Extreme....
 


#36
Re: windwos7 newupdeta

Well the new Mobo is in, and it seems much better so far *touch wood* but I guess only time will tell. The software and performance seem much better than my AsRock
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.