Multiple BSOD New custom Build ntfs.sys ntoskrnl.exe

I am back after installing the power supply....still having BSOD's attached is the logs. 2 While playing DOTA. One while running the SF Diag tool.

Care to elaborate?
You said you are going to have your PSU tested, the results?
Did it need replacing? Are you using a new PSU?

YoYo155 said:

tunaktu86, we are dealing with a hardware error. I went back and reviewed the files you uploaded in the order
they were uploaded and I noticed you went back to your Radeon GPU and installing the latest drivers
which in both of the times you were presented with a distorted display as seen in posts 9&25.

Now while you had the nVidia GPU you had a BSOD once while in DOTA2, lately we are seeing
rise in cases that are related to DOTA2 and other Steam based games so that BSOD is not necessarily
related to the GPU which made you switch back.

Now we need to determine whether the PSU is sufficient, whether the PCI-e slot is in good shape
and determine whether the GPU is not at fault.


What is the make an model of you PSU?
Fill out this form and post back the result:

• Power Supply Calculator

• Test both GPUs using Furmark.

whether the PCI-e slot is in good shape -switch slots and try it out.
If it still bugchecks;
whether the GPU is not at fault -Test both GPUs (nVidia as well as ATi) using Furmark.

If you don't feel like I should continue in assisting to try and diagnose the issue just say so I won't mind :) .


The last bugchecks are more of the same.

Code:

Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Wed Oct  2 01:52:48.504 2013 (UTC + 3:00) 
System Uptime: 0 days 0:00:56.628 
BugCheck A, {4e8b47fe, 2, 1, fffff800030b1c29} 
*** WARNING: Unable to verify timestamp for win32k.sys 
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys 
Probably caused by : memory_corruption 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Wed Oct  2 01:51:23.741 2013 (UTC + 3:00) 
System Uptime: 0 days 0:02:38.850 
BugCheck 3B, {c000001d, fffff8000332de1c, fffff88008e68c60, 0} 
Probably caused by : memory_corruption 
BUGCHECK_STR:  0x3B 
PROCESS_NAME:  dota.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Wed Oct  2 01:22:48.644 2013 (UTC + 3:00) 
System Uptime: 0 days 0:09:01.218 
BugCheck 1E, {ffffffffc0000005, fffff800030b1c39, 1, 88} 
Probably caused by : memory_corruption 
BUGCHECK_STR:  0x1E_c0000005_R 
PROCESS_NAME:  steamerrorrepo 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Sat Sep 28 03:50:17.602 2013 (UTC + 3:00) 
System Uptime: 0 days 0:01:49.366 
BugCheck 50, {ffffe9801aec7287, 1, fffff8000332dc02, 7} 
Probably caused by : memory_corruption 
BUGCHECK_STR:  0x50 
PROCESS_NAME:  chrome.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Sat Sep 28 03:47:59.307 2013 (UTC + 3:00) 
System Uptime: 0 days 0:09:23.415 
BugCheck 1E, {ffffffffc0000005, fffffa8007abe475, 1, 16d8911} 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed ) 
BUGCHECK_STR:  0x1E_c0000005_R 
PROCESS_NAME:  svchost.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Fri Sep 27 20:14:03.103 2013 (UTC + 3:00) 
System Uptime: 0 days 0:01:03.227 
BugCheck 50, {fffff8800b46eaf8, 0, fffff800033bdc2d, 2} 
Probably caused by : memory_corruption 
BUGCHECK_STR:  0x50 
PROCESS_NAME:  chrome.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533 
Debug session time: Fri Sep 27 20:12:32.285 2013 (UTC + 3:00) 
System Uptime: 0 days 3:15:14.409 
BugCheck 4E, {99, 213a89, 0, da89} 
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) 
BUGCHECK_STR:  0x4E_99 
PROCESS_NAME:  chrome.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Hi so sorry for the slow replies lately as things are popping up unexpectedly.

A question, using the nVidia card what slot did you test it in? and did you get a BSOD
only while in DOTA?
As for the bugchecks I've noticed that they pertain a problem with the CPU, of all things.
By looking at these stacks we can see the CPU being accessed, unparking a core;

Code:

00 fffff880`09da6568 fffff800`03703be0 nt!KeBugCheckEx
fffff880`09da6570 fffff800`03683cae nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`09da66d0 fffff880`04a1c006 nt!KiPageFault+0x16e
fffff880`09da6860 fffff880`04a02260 dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x4e
fffff880`09da6930 fffff880`04b39ffb dxgmms1!VidMmBeginCPUAccess+0x28
fffff880`09da6980 fffff880`04b3a6c2 dxgkrnl!DXGDEVICE::Lock+0x287
fffff880`09da69e0 fffff960`001f1482 dxgkrnl!DxgkLock+0x22a
fffff880`09da6ab0 fffff800`03684e13 win32k!NtGdiDdDDILock+0x12
fffff880`09da6ae0 00000000`7558156a nt!KiSystemServiceCopyEnd+0x13
00000000`1a86e598 00000000`00000000 0x7558156a

Code:

fffff880`030d49f8 fffff800`03684129 nt!KeBugCheckEx
fffff880`030d4a00 fffff800`03682da0 nt!KiBugCheckDispatch+0x69
fffff880`030d4b40 fffff800`0373dc1d nt!KiPageFault+0x260
fffff880`030d4cd0 fffff800`0373e382 nt!PpmPerfChooseCoresToUnpark+0x4fd
fffff880`030d4da0 fffff800`0373c4ac nt!PpmPerfCalculateCoreParkingMask+0x6c2
fffff880`030d4ed0 fffff800`0368f30c nt!PpmCheckRun+0x8c
fffff880`030d4f00 fffff800`03687d15 nt!KiRetireDpcList+0x1bc
fffff880`030d4fb0 fffff800`03687b2c nt!KxRetireDpcList+0x5
fffff880`031fd810 00000000`00000000 nt!KiDispatchInterruptContinue

• Use Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU.
• smarteyeball said:

  Don't forget to tick the 'Round off checking' option under Advanced:
  Attachment 87940
  
  Otherwise you won't know if one of your cores has failed etc
• Throw in some scans for good measure and for the sake of covering all angles;
• Download TDSS-Killer and scan for rootkits.
• Download Windows Defender Offline and scan for other types of infections.
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

Side note;

tunaktu86 said:

Also from your statement: If you don't feel like I should continue in assisting to try and diagnose the issue just say so I won't mind.

Are you suggesting I find someone else to assist or is a hardware replacement your suggestion? Either way...I don't mind.

I didn't suggest anything just wanted to hear your opinion on the state of things, and to let you know
that I will not take it personally if you wish that another will pop and give his opinion.

tunaktu86 said:

I think we may have hit the Jackpot. the machine will now BSOD at will.

When I run prime95 in anything but small FFT it causes BSOD's. I ran it as a small FFT and it seemed to run fine for over 15 minutes.

When I ran it as In-Place FFT's it BSOD as soon as the workers start. When I ran it as blend it crashed after only a minute.

Prime95 v 27.9

I will update the post after I run TDSS killer and scan the system with windows defender.

Hi thanks for the update :) , I see a couple of things that are odd to me.

First of all I find it hard to believe that the idle temperature is 14°C.
Also we see that the CPU is a little bit overclocked.
I don't think the overclock is from within the BIOS but reset it to be safe.

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

Now again all the bugchecks show memory corruption, that is in line with the fact that when you stress
test using options that include the RAM the machine bugchecks.

I see that you have F3-14900CL9-4, which is not in the motherboards QVL (Qualified Vendor's List)
what may mean something or not as those lists are often not complete but it's something to keep in mind.

I can also see you have two DIMM's 4GB each in slots 1&3:

Code:

[Memory Device (Type 17) - Length 34 - Handle 0030h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                Node0_Dimm1
  Bank Locator                  Node0_Bank0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         800MHz
  Manufacturer                  Undefined         
  Serial Number                             
  Asset Tag Number                            
  Part Number                   F3-14900CL9-4

[Memory Device (Type 17) - Length 34 - Handle 0034h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                Node0_Dimm3
  Bank Locator                  Node0_Bank0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         800MHz
  Manufacturer                  Undefined         
  Serial Number                             
  Asset Tag Number                            
  Part Number                   F3-14900CL9-4

Now start the process of elimination. Check each module (stick) in each slot individually
then try to bugcheck the machine as you did earlier using Prime95 if both modules pass all of the slots
on their own try both of them in all of the configurations possible with two modules over four slots.
It's time consuming but it's the only way to determine where the fault lays, the Motherboard, the CPU
or the RAM itself.

Take your time and post back with the results :) .

I tried testing each stick separately and the stick in slot one as well as in slot 3 kept getting BSOD's but stick two never would BSOD. I have tried it in slot 1 for about 10 minutes, and in slot three for 10 minutes on prime 95 then for a couple of hours between web browsing and playing DOTA2, no BSOD's with stick two.

I tested ram stick 1 in slots 1 and three and got bsod
I tested stick two in slots one and three and got no bsod even after 2 hours of web browsing and playing dota2.

Would you like me to keep testing in the rest of the slots with stick two or just RMA the bad stick/pair of sticks?