Frequent BSOD, new computer

[Eternaltheft]

Hey guys, I've just built a new computer and I've been getting quite a few BSODs lately. It would be awesome if you guys could help me out

Computer Specs:
Windows 7 Ultimate x 64
Intel i5-4670
Gigabyte Z87X-D3H-CF
16GB DDR3
GeForce GTX 770

 

[Arc]

Hello Eternaltheft.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html .

_____________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8801c670000, 0, fffff80003095bbb, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!GreGetDIBitsInternal+d6 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8801c670000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003095bbb, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c7100
GetUlongFromAddress: unable to read from fffff800032c71c0
 fffff8801c670000 Nonpaged pool

FAULTING_IP: 
nt!ExAcquireResourceSharedLite+110
fffff800`03095bbb 498b03          mov     rax,qword ptr [r11]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8801e16c670 -- (.trap 0xfffff8801e16c670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=02121c0c06129093 rbx=0000000000000000 rcx=fffff880121f8790
rdx=fffff880121f87a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003095bbb rsp=fffff8801e16c800 rbp=0000000000000000
 r8=fffff880121f8790  r9=0000000000000000 r10=0000000000000001
r11=fffff8801c670000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!ExAcquireResourceSharedLite+0x110:
fffff800`03095bbb 498b03          mov     rax,qword ptr [r11] ds:fffff880`1c670000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000310dbe0 to fffff8000308fb80

STACK_TEXT:  
fffff880`1e16c508 fffff800`0310dbe0 : 00000000`00000050 fffff880`1c670000 00000000`00000000 fffff880`1e16c670 : nt!KeBugCheckEx
fffff880`1e16c510 fffff800`0308dcae : 00000000`00000000 fffff880`1c670000 fffff880`1e16c800 fffffa80`10c64f90 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`1e16c670 fffff800`03095bbb : 00000000`00000a7c 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x16e
fffff880`1e16c800 fffff800`03098b13 : 00000000`00000000 fffffa80`129c98c0 00000000`00000000 fffff880`1e16c938 : nt!ExAcquireResourceSharedLite+0x110
fffff880`1e16c870 fffff960`0014c536 : fffff880`1e16c938 00000000`00000004 fffffa80`112d3b70 fffff800`03333244 : nt!ExEnterPriorityRegionAndAcquireResourceShared+0x23
fffff880`1e16c8a0 fffff960`001628ed : 00000000`00000100 00000000`78051748 00000000`00000000 fffffa80`00000040 : win32k!GreGetDIBitsInternal+0xd6
fffff880`1e16c990 fffff800`0308ee13 : 00000000`6f0114ed 00000000`78051748 00000000`00000000 00000000`00000040 : win32k!NtGdiGetDIBitsInternal+0x3cd
fffff880`1e16ca70 00000000`7560062a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011de38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7560062a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!GreGetDIBitsInternal+d6
fffff960`0014c536 488b1523602500  mov     rdx,qword ptr [win32k!ghsemDynamicModeChange (fffff960`003a2560)]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!GreGetDIBitsInternal+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51aeb1a7

FAILURE_BUCKET_ID:  X64_0x50_win32k!GreGetDIBitsInternal+d6

BUCKET_ID:  X64_0x50_win32k!GreGetDIBitsInternal+d6

Followup: MachineOwner
---------

 

[Eternaltheft]

Hi Arc, I've ran memtest before and received no errors.

Ok i followed the verifier instructions and it caused me to have some BSODs, here's the updated version of the SF folder:

View attachment 284546

The snapshot of speccy:View attachment 284550

Thanks for helping so far

 

[Arc]

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Let us know the results.
__________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800457b360, fffff98003f1ce10, 0}

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
Unable to load image dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1360 )

Followup: MachineOwner
---------

 

[Eternaltheft]

I've uninstalled daemon tools and uninstalled intel rapid storage from control panel and device manager. Thanks for all the help, hopefully there are no more blue screens, if there are, I'll be sure to come back here

 

[Arc]

Let us know how the computer is running, after a couple of days or at the occurence of the next BSOD, whichever is earlier.

Feedback is necessary, you know

 

[Eternaltheft]

Unfortunately I got a few more BSOD

View attachment 284647

 

[Arc]

Have a look at this thread: http://www.sevenforums.com/bsod-hel...mory-management-error-0x1a-2.html#post2522354

I hope you get something useful there.

 

[Eternaltheft]

I don't really understand what it means by "switched the graphic card option back to 'switchable'" :S

 

[Arc]

He first switched it to integrated only, to make it sure that if there is no trouble with the integrated graphics. When it is sure, he switched back to switchable.

 

[Eternaltheft]

Ok i followed Asif's steps, of re seating the ram, custom installing the NVIDIA driver and changing the graphics clock to 650. Thanks for the tips ^^. Guess I'll just wait on the next BSOD haha

Still getting BSOD .

View attachment 284700

 

[Eternaltheft]

Still get a few BSOD. If anyone can help me, it will glady be appreciated ^^

View attachment 284955

 

[Arc]

Do a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html . Use either of the GPU.

 

[Eternaltheft]

Ok thanks . So I don't install intel rapid storage and install custom settings for NVIDIA after the clean reinstall?

 

[Arc]

Yes, keep it simple.

 

[essenbe]

Eternaltheft, I came here at the request of Arc, so if I ask about something thay has neen done already please excuse me. Unless Arc has some evidence or indications otherwise, I'm not convinced it is the Optimus Technology. Optimus just allows the computer to decide on which applications to use the on chip (CPU) graphics or the dedicated GPU. I have a laptop with Optimus and realy dislike it. I have, through the Nvidia control panel, changed it to use the dedicated graphics only. It has never caused me a problem except the battery life is shorter, which does not bother me personally, but is the whole idea of optimus, to give longer battery life. It is difficult to advise you on exactly what to do since your system specs say your laptop is self built. Most pre manufactured laptops, the manufacturer alters the drivers to work with the way they built the laptop to run. In some cases installing drivers from Nvidia, can cause problems. Personally, I think Arc is taking the right approach. A clean install of Windows is best. But, look at the windows updates as they come in. Don't install hardware updates that you already have the drivers for. Download the drivers from your motherboard's web site. But, do not install any programs for a few days. Let it run as as a clean install as long as you can. If you get along OK. Install 1 program at a time, and use the laptop for a while to make sure that program you installed is not the problem. Keep doing that untill you have your laptop set up the way you like it. If you do that, then if you have BSODs again, it will be the last program you installed. I am subscribed to this thread now, and will be here to assist you and Arc any way I can. I hope you don't mind.

 

[Eternaltheft]

Hi Essenbe, thanks for the suggestions . But I'm using a custom built desktop, not laptop so I don't really care about the battery . Do you think I should just run the dedicated video graphics only? Of course I don't mind, I really appreciate you taking the time to help me out, these BSOD are driving me insanse and I'm not much of a tech savvy person haha

 

[essenbe]

Well, I have no idea how I got the impression that you had a self built laptop. I must be brain dead. Then, are you using LucidLogix? If you are, it can help some things but can also cause a lot of problems. If you have it on, I would disable it and just use the GTX 770.

I also hate to tell you this, but new technology takes time for the manufacturers to catch up with. I know I went through that with the Ivy Bridge and the Maximus V. I even RMA'd the board when the problem was that Asus had a bad bios that caused problems with the board. When they finally figured out what was wrong, they issued a new bios and problems solved. The same goes with other software manufacturers. You are not the only person who has problems with thay board. http://www.overclock.net/t/1409617/massive-problems-with-gtx-770. I don't know if it is a defect in the board or software. It would still be easier to try running it on a complete clean install to see if you have problems and slowly install 1 piece of software at a time and use it long enough to see if it is still stable. Then install another program and do the same.

Also, what version of the Nvidia driver are you using. Sometimes it can help to change to an older or newer driver.

 

[Eternaltheft]

Nope, I have no idea what LucidLogix is. But I have the Intel graphics.

I don't think I have as bad of a problem as the other person who was a GTX 770, my main problems are the BSOD.

I have NVIDIA Graphics Driver 320.49