[elefantjunior]

so i just built a new desktop a few weeks ago and i've been battling blue screen errors since i turned it on. i've tried reinstalling/repairing windows 7 (64 bit) and made sure my drivers were up to date. my system specs are

OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 64 bit
Processor: Intel® Core™ i5-4570 CPU @ 3.20GHz, Intel64 Family 6 Model 60 Stepping 3
Processor Count: 4
RAM: 8148 Mb
Graphics Card: AMD Radeon HD 7900 Series, -1024 Mb
Hard Drives: C: Total - 953766 MB, Free - 792902 MB;
Motherboard: Gigabyte Technology Co., Ltd., Z87X-D3H-CF
Antivirus: Microsoft Security Essentials, Updated and Enabled

i attached a zip file with the most recent blue screens, since i've turned it on the 0x7e has been the most common which from what i gather is a graphics card issue but no matter what i do i cant seem to get it to stop. hopefully someone here can help me out
 091813-13150-01.zip   248.99KB   190 downloads

Edited by elefantjunior, 18 September 2013 - 07:55 PM.

[Advertisements]

elefantjunior

Download and run whocrashed and post the results for us please.

[phillpower2]

elefantjunior

Download and run whocrashed and post the results for us please.

[elefantjunior]

ok i ran it and these are the results that came out.


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 4.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: NABISCO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-4570 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8474615808 total
VM: 2147352576, free: 1934032896




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 9/19/2013 3:30:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-16473-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Thu 9/19/2013 3:30:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x625EB)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel® USB 3.0 eXtensible Host Controller Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED



On Thu 9/19/2013 3:07:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-13244-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880045406AA)
Bugcheck code: 0x50 (0xFFFFF8A019F0DC90, 0x0, 0xFFFFF880045406AA, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Thu 9/19/2013 2:30:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-13041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344EFF, 0xFFFFF88005491EF0, 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 Thu 9/19/2013 2:19:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-13026-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A009316AD0, 0x0, 0xED77)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
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 video memory manager has encountered a condition that it is unable to recover from.
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 Thu 9/19/2013 2:11:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-12994-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA820962A748, 0x2, 0x0, 0xFFFFF800032D2D31)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 9/19/2013 1:04:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-14820-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x85FDC)
Bugcheck code: 0xD1 (0x12002D, 0x2, 0x1, 0xFFFFF88001685FDC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 Thu 9/19/2013 12:34:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-13572-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Thu 9/19/2013 12:29:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-13150-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E26)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880053D3E26, 0xFFFFF88003EFA568, 0xFFFFF88003EF9DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Wed 9/18/2013 6:47:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4E (0x7, 0x1E44CF, 0xA3BDF, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 9/18/2013 6:41:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-12667-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003945E68, 0xFFFFF880039456C0, 0xFFFFF800032E6150)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 9/18/2013 12:51:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091713-26894-01.dmp
This was probably caused by the following module: afd.sys (afd+0x368A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800035BB861, 0xFFFFF880031E08D8, 0xFFFFF880031E0130)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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/17/2013 8:41:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091713-30310-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA8064CE7298, 0x2, 0x1, 0xFFFFF800033873AC)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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/17/2013 2:06:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091613-31215-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Sun 9/15/2013 3:32:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091413-22230-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x31FC0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880053C6FC0, 0xFFFFF88003C68378, 0xFFFFF88003C67BD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Only 15 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:

iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.

[phillpower2]

Thanks for the update elefantjunior which as you can see is pointing towards the Intel USB 3.0 driver;

Can you check the Device Manager for any yellow ! or red Xs please.

Next please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Thanks to rshaffer61 for the PCPitstop information

NB: An example of the url that we require and the information that it leads to http://www.pcpitstop.com/betapit/sec.asp?conid=25271813

[elefantjunior]

http://www.pcpitstop...?conid=25432444

I tried moving a RAM stick from one slot to another and for the last 2 days i have not had a problem with any blue screens or freezes so it may be that i just had the RAM in the wrong slot and the PC wasnt reading it properly. however this is what the scan came back with if there is something else that you might see i can do

[phillpower2]

Thanks for the update which sounds promising elefantjunior

The test results in the main look ok however can you please return to the PCPitstop results and address the items that have a red X against them, if you hover the cursor over the item you will be given a description of the issue and if you click on it you will be instructed how to correct the problem.

I noted the Pando Media Booster entry in your list of installed software, this type of program can do more harm than good so I suggest that you uninstall it asap, some information Here