3D mark

My system is new and have made no mods to hardware as in oc but every time I try to run fire strike extreme stress test it always give in a error. All temps are around 30 c. Any ideas?
Thanks

As for window errors all I get is a little window pops up and say window has a error. But you can not cancel the program or close it. It does not show in task master to close and it will not restart as it says it is already running. The only way to start it is to reboot the system to restart then of course it crashes again. I am at work right now and will post what the srror from the log says later.
Thanks






Chassis Model: Special Deal Hot Seller - Digital Storm Velox
Exterior Finish: - Standard Factory Finish
Trim Accents: - Standard Factory Finish
Processor: Intel Core i7 6850K 3.6GHz (6-Core) (Unlocked CPU)
Motherboard: ASUS X99 RAMPAGE V EDITION 10 (Intel X99 Chipset) (Up to 4x PCI-E Devices) (RGB Lighting)
System Memory: 32GB DDR4 3200MHz Corsair Dominator Platinum DHX (Extreme-Performance)
Power Supply: 1000W Corsair HX1000i (Digitally Controlled Power)
Expansion Bay: Option Not Available
Optical Drive: DVD-R/RW/CD-R/RW (DVD Writer 8x / CD-Writer 8x) (Internal)
Storage Set 1: 1x SSD (1TB Samsung 850 EVO)
Storage Set 2: 1x Storage (2TB Western Digital - Black Edition)
Storage Set 3: - No Thanks
RAID Config: - No Thanks
RAID Card: - No Thanks
Internet Access: High Speed Network Port (Supports High-Speed Cable / DSL / Network Connections)
Graphics Card(s): 2x SLI Dual (GeForce GTX 1080 8GB (NVIDIA Founders Edition) (VR Ready)
Sound Card: Integrated Motherboard Audio
HPC Processor: - No Thanks
Extreme Cooling: H20: HydroLux LITE: Integrated Cooling System (2x Graphics Cards + CPU)
HydroLux Tubing Style: Flexible Tubing (Requires HydroLux Liquid Cooling System)
HydroLux Fluid Color: Red Fluid (Requires HydroLux Liquid Cooling System)
Cable Management: Exotic Cable Management - Red - (Cable Combs with Custom Color Sleeved Extension Cables)
Chassis Fans: Corsair LED Airflow Performance Edition (Red) (Up to 6 Fans)
Internal Lighting: Digital Storm RGB LED Lighting System (Requires Thermal Management Control Board & Software)
Airflow Control: Digital Storm Thermal Management Control Board & Software
Chassis Mods: - No Thanks
Noise Reduction: - No Thanks
LaserMark: - No Thanks
CPU Boost: Stage 1: Overclock CPU - Up to 4.4GHz (Depends on Cooling and Motherboard)
Graphics Boost: Yes, Overclock the video card(s) as much as possible with complete stability
OS Boost: - No Thanks, Please do not tweak the services on the operating system
Windows OS: Microsoft Windows 10 Home (64-Bit Edition)
Recovery Tools: Windows Recovery Toolkit (Bundled with Windows CD)
Virus Protection: FREE: McAfee AntiVirus Plus (1 Year Service Activation Card) (Not Pre-installed) ($35 Value)
Office: - No Thanks
Game: - No Thanks
Display: - No Thanks
Surge Shield: - No Thanks
Speakers: - No Thanks
Keyboard: - No Thanks
Mouse: - No Thanks
Branded Gear: - No Thanks
Priority Build: - No Thanks, Ship Within 10-15 Business Days After Order Is Successfully Processed
Warranty: Life-time Expert Care with 3 Year Limited Warranty (   
1343494 -- FREE NVIDIA Bundle - Paragon Game Ready Pack ($115 Worth of In-Game Currency) 1 $0.00
MISC HB SLI Bridge By: John 8/19/2016 1 $50.00

Below are the error codes that showed up. Also when I bought the system I did buy a new usb hub listed below. I have ran the stress test before with out errors once. Also last night I installed Acronis and made a clone to a usb drive. It is connected and I did disable the software as I will only use it to make another clone in the future if needed. Not sure if I did something wrong there either? it does recommend updating it drivers any one hear of this?
Thanks










Upgraded Version] Anker USB 3.0 SuperSpeed 10-Port Hub Including a BC 1.2 Charging Port with 60W (12V / 5A) Power Adapter [VIA VL812-B2 Chipset and updated Firmware 9081] AH231   



by Anker

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 9/20/2016 6:58:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092016-12125-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF961EBB9F3DF)
Bugcheck code: 0x50 (0xFFFFF90197994508, 0x2, 0xFFFFF961EBB9F3DF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/20/2016 6:58:46 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!DestroyCacheDC+0xF)
Bugcheck code: 0x50 (0xFFFFF90197994508, 0x2, 0xFFFFF961EBB9F3DF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/20/2016 6:50:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092016-12484-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF801DB8E53B9)
Bugcheck code: 0xD1 (0x3E800000000, 0x2, 0x0, 0xFFFFF801DB8E53B9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/20/2016 3:28:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091916-12640-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF96018DCB8FE)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF89, 0x2, 0xFFFFF96018DCB8FE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/20/2016 2:41:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091916-12656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8010FEFE47F, 0xFFFFD00024C3ECF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/20/2016 1:55:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091916-12671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0x50 (0xFFFFF8016D35331C, 0x10, 0xFFFFF8016D35331C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/13/2016 11:23:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-12234-01.dmp
This was probably caused by the following module: ftdibus.sys (0xFFFFF801BA130520)
Bugcheck code: 0x50 (0xFFFFE00060000000, 0x2, 0xFFFFF801BA130520, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ftdibus.sys
product: FTDIChip CDM Drivers
company: FTDI Ltd.
description: FTDIBUS USB Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ftdibus.sys (FTDIBUS USB Driver, FTDI Ltd.).
Google query: FTDI Ltd. PAGE_FAULT_IN_NONPAGED_AREA



On Sat 9/10/2016 1:20:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090916-12578-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3E1D)
Bugcheck code: 0x113 (0x4, 0xFFFFD000215BCA98, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 9/9/2016 11:46:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090916-12140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802ADAAD497, 0xFFFFD00022912B50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/31/2016 8:20:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083116-10625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x141F80)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





________________________________________
Conclusion
________________________________________

14 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ftdibus.sys (FTDIBUS USB Driver, FTDI Ltd.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Who crashed is there a better one?
Thanks

Sorry the last dump file is the one on top

Ok sorry but how and where do I pull this or these?

Go here in your pc:

C:\Windows\Minidump

and copy the latest dump file and paste it onto your desktop, now close teh minidump folder and comeback to the dump file we just copied to the desktop. right click the dump file and choose rename, now the only part we want to change here is the extension (.dmp) we want to change it from .dmp to .zip and then save it. once saved upload it here.

you have to change the name since the uploader here on the forum does not allow .dmp files, but it will take .zip files.

I will change it back to .dmp when I get it.

if you need help uploading here let me know.

Also what is the problem with your second card? its not showing up?

Edited by DST4ME - 20 Sep 2016 at 6:19pm

uploads/13888/082816-10828-01.zip
Hope this works
Also what do you see that shows the second card is not operating?
Thanks

never mind I figured out what you did wrong with the link.

Ok this dump file is telling us:

it was Probably caused by : nvlddmkm.sys ( nvlddmkm+1bc285 )

Not sure, you have many errors and this is just one dump file.

If you like try DDU version 17.0.2.0 and uninstall your nvidia drivers with it in safe mode and install a new set of drivers from nvidia. When you install the new drivers install only the drivers and physx drivers.

Click on the link in sig that says nvidia drivers and download a new set of drivers first then use ddu to uninstall and etc.

Edited by DST4ME - 20 Sep 2016 at 7:14pm

I had gotten your thread totally messedup with somebody else, they had stated their temps where fine and for some reason I kept mixing up their info with yours.

Must have software

Edited by DST4ME - 20 Sep 2016 at 10:45pm

Our pleasure