Solved Multiple BSOD New custom Build ntfs.sys ntoskrnl.exe

[tunaktu86]

I'm sorry I did not respond sooner. We have had major system failures at work and I haven't had a chance to work on my home PC.

OK. I ran verifier /query an got

C:\Windows\system32>verifier /query
9/25/2013, 9:18:50 AM
No drivers are currently verified.

I checked on AMD's website and they released a new AMD Catalyst driver a few days ago and I installed it.

I was using my PC all day yesterday and had one restart, I did not see what caused it or what the message was. I played DOTA2 for maybe 5 minutes and the system had a BSOD

 

[YoYo155]

Both of the latest bugchecks display memory issues (memory corruption & access violation).

BugCheck 24, {1904fb, fffff8800bad72c8, fffff8800bad6b20, fffff880012e7c05}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [U][B]memory_corruption[/B][/U]


EXCEPTION_RECORD:  fffff8800bad72c8 -- (.exr 0xfffff8800bad72c8)
ExceptionAddress: fffff880012e7c05 ([B][COLOR=Blue]Ntfs!NtfsCommonCleanup+0x0000000000000425[/COLOR][/B])
   ExceptionCode: [COLOR=Teal][B]c0000005 (Access violation)[/B][/COLOR]
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
[COLOR=Red][U][B]Attempt to read from address ffffffffffffffff[/B][/U][/COLOR]

In Blue we can see where the error happaned, in red we can see that the memory that is being
read from (in Red) is invalid.

By checking the image (Ntfs) for errors, we can see that memory was corrupted
in this case three bits.

[COLOR=Green][B]!chkimg -d -db !Ntfs[/B][/COLOR]
    fffff880012e7c04 - Ntfs!NtfsCommonCleanup+424
    [ [COLOR=Red][B]00:04[/B][/COLOR] ]
    fffff880012e7c24 - Ntfs!NtfsCommonCleanup+444 (+0x20)
    [ [COLOR=Red][B]be:bc[/B][/COLOR] ]
    fffff880012e7c3c - Ntfs!NtfsCommonCleanup+45c (+0x18)
    [ [COLOR=Red][B]00:02[/B][/COLOR] ]
3 errors : !Ntfs (fffff880012e7c04-fffff880012e7c3c)
fffff880012e7c00  80  d0  00  00 *04  f6  40  41  03  74  0e  49  8b  40  28  f6 [email protected].@(.
...
fffff880012e7c20  19  00  00  41 *bc  07  00  00  00  44  8a  64  24  70  4c  8b ...A.....D.d$pL.
fffff880012e7c30  94  24  90  00  00  00  83  bc  24  08  01  00 *02  04  0f  84 .$......$.......

BugCheck 3B, {[U][B]c0000005[/B][/U], fffff800030fc45f, fffff8800871bb40, 0}

Probably caused by : ntkrnlmp.exe ( nt!SeComputeAutoInheritByObjectType+13b )

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800030fc45f

STACK_TEXT:  
fffff880`0871c520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeComputeAutoInheritByObjectType+0x13b

Please remove:

lmimirr.sys Wed Apr 11 01:32:45 2007
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=lmimirr.sys

LMIRfsDriver.sys Mon Jul 14 19:26:56 2008
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys

AODDriver2.sys Wed Nov 21 09:44:04 2012
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys

atpdrvr.sys Wed Sep 23 14:01:27 2009
Product: Array SSL VPNCompany: Array Networks, Inc. - See more at: atpdrvr.sys | System Explore

ElbyCDIO.sys Mon Mar 4 11:21:51 2013
CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys

VClone.sys Mon Mar 11 02:49:12 2013
VirtualCloneCD Driver by Elaborate Bytes AG
http://www.carrona.org/drivers/driver.php?id=VClone.sys

truecrypt.sys Tue Feb 7 11:09:36 2012
TrueCrypt driver
http://www.carrona.org/drivers/driver.php?id=truecrypt.sys
​

Please Update:

Rt64win7.sys Tue Sep 27 17:50:33 2011
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys

Description: Win7 and WinServer 2008 R2 Auto Installation Program
Version: 7.075
Update Time: 2013/9/24

• Download

amdiox64.sys Thu Feb 18 17:17:53 2010
AMD IO Driver
http://www.carrona.org/drivers/driver.php?id=amdiox64.sys

• Download

OK. I ran verifier /query an got

C:\Windows\system32>verifier /query
9/25/2013, 9:18:50 AM
No drivers are currently verified.

As I though DV wasn't enabled, please follow :: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html ::

 

[tunaktu86]

Removed log me in

Removed Virtual Clone

removed Truecrypt

couldn't dins EBLYCDIO or AODDriver2.sys or amd overdrive

updated RT64win7.sys

updated the amd IO drivers to 13

as I was in the GUI to turn on Driver verifier it BSOD

 

[YoYo155]

Thanks for the update, please upload a new instance of the SFDT.

To remove AOD;
Uninstall Catalyst Control Center using | AMD Catalyst Un-install Utility
Then follow through with a pass of Driver Sweeper.

Download version 13.1
​

   Note

Install the display driver only! | Do not install the Catalyst Control Center software.

 

[tunaktu86]

Here is the requested SF.

I uninstalled all AMD drivers and re-installed sans Catalyst Control Center software

Also, this is the image I get when verifier is running and Windows logs on. If I can change the resolution fast enough or boot into Low res mode it will load into windows and allow me to use the system.

I believe there should be a crash or two in the SF I am uploading where verifier was running.

Below is the verifier /query results.
______________________

C:\Windows\system32>verifier /query
9/27/2013, 7:03:58 AM
Level: 00000DBB
RaiseIrqls: 0
AcquireSpinLocks: 844447
SynchronizeExecutions: 157107
AllocationsAttempted: 1477071
AllocationsSucceeded: 1477071
AllocationsSucceededSpecialPool: 1477071
AllocationsWithNoTag: 0
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 287134
UnTrackedPool: 1383621

Verified drivers:

Name: amd_sata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: amd_xata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 6
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 68
PeakNonPagedPoolUsageInBytes: 1600

Name: amdxata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: etronxhci.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 3
CurrentNonPagedPoolAllocations: 20
PeakPagedPoolAllocations: 7
PeakNonPagedPoolAllocations: 25
PagedPoolUsageInBytes: 628
NonPagedPoolUsageInBytes: 1459224
PeakPagedPoolUsageInBytes: 1076
PeakNonPagedPoolUsageInBytes: 1459768

Name: usbfilter.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 140
PeakNonPagedPoolUsageInBytes: 24

Name: rt64win7.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 4105
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 4105
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 613812
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 613812

Name: ndis.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 6
CurrentNonPagedPoolAllocations: 8836
PeakPagedPoolAllocations: 8
PeakNonPagedPoolAllocations: 8875
PagedPoolUsageInBytes: 984
NonPagedPoolUsageInBytes: 2661752
PeakPagedPoolUsageInBytes: 1296
PeakNonPagedPoolUsageInBytes: 2678280

Name: amdiox64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 116
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 360
PeakNonPagedPoolUsageInBytes: 132

Name: etronhub3.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 4
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 12
PagedPoolUsageInBytes: 116
NonPagedPoolUsageInBytes: 1344
PeakPagedPoolUsageInBytes: 132
PeakNonPagedPoolUsageInBytes: 1984

Name: dump_diskdump.sys, loads: 0, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_amd_sata.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_dumpfve.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 16400

 

[YoYo155]

Ok thanks, you can disable DV now as it's pretty apparent we are dealing with faulty hardware.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Test the GPU using OCCT:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html
• Use Speccy to monitor the temperatures :: Speccy - System Information - Free Download ::
  

BugCheck 3B, {c0000005, fffff8000332dc39, fffff8800999dfe0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption



!chkimg -lo 50 -db !nt
3 errors : !nt (fffff8000332dc0c-fffff8000332dc3c)
fffff8000332dc00  40  8a  d7  49  8b  4e  30  e8  64  f0  d4  ff *f4  09  1c  24 @..I.N0.d......$
fffff8000332dc10  0f  ae  e8  48  8d  84  24  b8  00  00  00  48 *8d  44  24  40 ...H..$....H.D$@
...
fffff8000332dc30  89  44  24  30  48  89  74  24  28  48  8b  44 *26  68  48  89 .D$0H.t$(H.D&hH.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff8800999dfe0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption

Post back with the results, and good luck.

 

[tunaktu86]

EDIT: Also i've started getting errors in DOTA 2 when I choose my character. Its a checkerboard for backgrounds and some animations instead of actual scenes.

ok. I ran OCCT for 15 minutes and it got up to 81 degrees C.

I tried to run the OCCT Memtest, and it says "User Aborted" after only a second or two.

 

[YoYo155]

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.

 

[tunaktu86]

Well this morning u went to starlet up PC and it was unresponsive. I've tried removing components and unplugging and reseating all psu cords and the power supply still only flashes on for a second then won't respond again. I can turn the switch off on the back of the psu and back on and again the fans start to spin up and I see some led's and then everything goes black again.

I'm going to get my psu tested. I believe I may have a bad PSU. Do you think that May have been causing some of the problems all along?

 

[YoYo155]

Very much so yes, keep us in the loop .

 

[tunaktu86]

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.

 

[YoYo155]

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?

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.

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 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[tunaktu86]

I did purchase a new PSU and it is a 550W

Seasonic G Series 550 Watt

eXtreme PSU Calculator

System Type: 1 physical CPU
Motherboard: Regular - Desktop
CPU Socket: Socket AM3+
CPU: AMD FX-6300 3500 MHz Vishera
CPU Utilization (TDP): 90% TDP
RAM: 2 Sticks DDR3 SDRAM
Video Card 1: AMD Radeon HD 7950

ATTENTION: FOR PERSONAL, NON-COMMERCIAL USE ONLY
Regular SATA: 3 HDDs
Flash SSD: 1 Drive
CD-ROM Drive: 1 Drive
PCI-e x16 Card: 1 Card
USB: 2 Devices
Fans
Regular: 3 Fans 80mm; 1 Fan 250mm;
LED: 3 Fans 80mm;
Keyboard and mouse: Yes
System Load: 90 %

Minimum PSU Wattage: 386 Watts
Recommended Wattage: 436 Watts


I will test the ATi card again with Furmark and switch PCIE slots and see if I get any more BSOD's.

I'll also use the Nvidia Card and see as well.

 

[tunaktu86]

I changed PCIE slots and tested the ATI Card first. I ran Furmark first thing and it ran for 5 minutes and then had a BSOD. temperature of the GPU was only 74.

I shut down the machine and installed the Nvidia Card. I had uninstalled the Nvidia Drivers previously so while trying to install the new drivers had 2 more BSOD. one was so quick that i couldn't see anything but blue then it restarted. The second showed BSOD then restarted and ran checkdisk upon boot. I was able to then install the most recent nvidia Driver (released 9-19-2013) and ran furmark for 26 minutes with no issue. temp held at 72 for 22 minutes of the 26.

I also played one game of DOTA 2 to try to trigger a BSOD with the nvidia card and it didn't happen.

Is this sufficient or did I miss something in your post?


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.

 

[tunaktu86]

I wanted to test again this morning if I could get a Blue Screen on the Nvidia. I ended up getting a BSOD after using DOTA for about 15 minutes.

Are you thinking this is a GPU issue, or a RAM issue that memtest didn't pick up or could it be the SSD causing the drivers to access bad memory?

 

[YoYo155]

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;

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::[U][COLOR=Blue][B]BeginCPUAccess[/B][/COLOR][/U]+0x4e
fffff880`09da6930 fffff880`04b39ffb dxgmms1![COLOR=Blue][B]VidMmBeginCPUAccess[/B][/COLOR]+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

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![U][COLOR=DarkOrchid][B]PpmPerfChooseCoresToUnpark[/B][/COLOR][/U]+0x4fd
fffff880`030d4da0 fffff800`0373c4ac nt![COLOR=DarkOrchid][B]PpmPerfCalculateCoreParkingMask[/B][/COLOR]+0x6c2
fffff880`030d4ed0 fffff800`0368f30c nt![COLOR=DarkOrchid][B]PpmCheckRun[/B][/COLOR]+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.

• Don't forget to tick the 'Round off checking' option under Advanced:
  View 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;

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]

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?

After installing the newest Nvidia driver, yes I have only gotten the BSOD while in DOTA. I have not been playing on it in the past few days due to personal issues.

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;

• 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.

• Don't forget to tick the 'Round off checking' option under Advanced:
  View 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.

OK. I am at work currently, I will run a prime 95 test on the CPU as requested when I get home.

Side note;

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.

If you think a fresh set of eyes may help locate the issue I am up for anything. I'm kind of worried at this point because I am now out of my newegg RMA window. I've never run into an issue this squirrely in any of my previous builds.

 

[tunaktu86]

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.

 

[YoYo155]

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:

[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                          [COLOR=Blue][U][B]4096MB[/B][/U][/COLOR]
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                Node0_[COLOR=Blue][U][B]Dimm1[/B][/U][/COLOR]
  Bank Locator                  Node0_Bank0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         800MHz
  Manufacturer                  Undefined         
  Serial Number                             
  Asset Tag Number                            
  Part Number                   [B]F3-14900CL9-4[/B]

[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                          [COLOR=Blue][U][B]4096MB[/B][/U][/COLOR]
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                Node0_[COLOR=Blue][U][B]Dimm3[/B][/U][/COLOR]
  Bank Locator                  Node0_Bank0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         800MHz
  Manufacturer                  Undefined         
  Serial Number                             
  Asset Tag Number                            
  Part Number                   [B]F3-14900CL9-4[/B]

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 .

 

[tunaktu86]

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?