New Parts BSOD

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Kamil Cziba

Honorable
May 6, 2013
29
0
10,530
Hi,
I've recently change some parts of my PC:

Asrock Z77 Extreme4
i5 3570K
2x4GB Adata 1600 MHz cl9

My gpu is MSI GTX 660, PSU is BeQuiet 450W

Since then i'm having bsod's.
I've checked with 3 different version sets of drivers,
checked my memory with memtest - 8 passes no erros,
switched slots of my ddr3 and gpu
ran driver verifier - showed blue screen with my mouse drivers - I removed it but still didn't help.

What could be the reason ? I'm helpless.

Here is zip with all the minidumps sicne last windows reinstall:
https://docs.google.com/file/d/0BzZzjdmJquKYSmJ1NnIzdnd0Slk/edit?usp=sharing
 
Solution
I placed this on another post. Thought it might help. I chased Direct X and software problems for 2 months. Today I found the issue. Considering you moved stuff around I think you had the same problem as me. Hope the following helps:
-------------------------------------

The very same problem has plagued me since March 29th and it has been driving me nuts. I have gone through a TON of troubleshooting too and had replaced a hard drive and a sound card. At times I even felt it was fixed then sadly found out an hour later that it was not. My PC is only 3 years old and I felt it was not old enough to be experiencing problems.

Well today I am confident I found the solution.

Below was the exact error I was receiving...
There was no driver flagged in that dump, that usually means a hardware error.

Run MemTest86+ on each stick individually in Slot #1 for 7+ passes, if they both pass, test one of the sticks in each of the remaing slots individually for a further 7+ passes.

Check your RAM settings for compatibility.

Run hard drive diags: http://www.carrona.org/hddiag.html
 
Honestly, I'm not going to read through all of that, could you please verify what model is your MSI GTX 660, there are 5 different models.
http://www.msi.com/product/vga/#?fp=GeForce 600 Series&sk=Geforce GTX 660

Assuming general Nvidia references, the Nvidia GTX 660 requires a 450 watt PSU and 1 x 6-pin power connector.
What model type is your PSU, there are 2 different ones for the 450 watt Be Quiet brand - Straight Power and System Power.
http://www.bequiet.com/en/powersupply/328

Also, Your OS install is in German so you'd need to install drivers that were also German location, perhaps. What is your OS version?

The German version of Windows 7 does not include Internet Explorer, is that your version?

 
My friend has same setup - CPU, mobo and ddr so it should be compatible. I'm just gonna run that memtest for each stick individually.

EDIT:
My GPU is: N660-2GD5/OC [link]
PSU: Straight Power(E6) 450W [link]

and i was running that GPU with that PSU before i changed mobo CPU and ddr and there was no bsod.

My OS is in polish and its Windows 7 Professional Sp1 x64 - it does include IE
 
Thank you for adding the details. Sorry about the German reference, I should have looked more closely at the language. I was in a bit of a hurry, the Be Quiet site that gives the lists of PSU's and all their specs, has a long running script that really bogs down my system and I thought I'd lose my browser!

When you do your updates, do you select Polish language?
Do you update from the MSI site or the Nvidia site for the video card?

Motherboard -
http://www.asrock.com/mb/Intel/Z77%20Extreme4/?cat=Specifications


You do realise that if you use the same hdd with another motherboard, the chipset has to be the same?
If the new motherboard is an earlier version to the one it replaced then the chipsets might be different.

What was the brand / model of the replaced motherboard?
 
Sometimes distributors of Nvidia products tweak the gpu for a slight different setting, you might want to consider updating directly fronm the MSI site. One would assume that any tweaking would not inmpact on the drivers themselves but clock ratios might be different and settings may cause some sort of issue. Nvidia do get quite disgruntled when distributors tweak preset settings so there must be a reason as to why they would feel "disgruntled".

"The Drivers provided here are exclusively for MSI products only." Why only MSI? Do they include something that is not included with Nvidia drivers for the same product?
MSI Graphics Driver 306.97
http://www.msi.com/product/vga/N660-2GD5-OC.html#/?div=Driver&os=Win7%2064

Have you done any Windows updates?

Edit -
Bug Check - "Probably caused by : nvlddmkm.sys" - this is a Vista Nvidia driver....
 
It is never anything conclusive, you could fix one error then another error will result.
Update from the MSI site, not from Nvidia. MSI drivers can only be used with MSI products, have you ever wondered why that is so if they are the "same" as Nvidia drivers?

If your friend has the same parts then go ask him what drivers he updates and from what provider.
 
This dump is Driver Verified but no 3rd party driver was flagged, this usually points to hardware.

The bugcheck type was 0x77 KERNEL_STACK_INPAGE_ERROR:
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware
So the most likely offender is somewhere between the disk controller and the data on the drive, probably a bad block in the paging file.

Turn off Driver Verifier: verifier /reset.

Remove the paging file, reboot and run chkdsk /r /f and allow the machine to reboot again to complete the disk check. Create a new paging file and check the System/Application logs for details of the chkdsk findings/repairs.

2: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 0000000000000000, (page was retrieved from page cache)
Arg2: fffffa8007fae0a0, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffff8800ae347c0, address of signature on kernel stack

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


ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x77_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000334e551 to fffff800032c9c00

STACK_TEXT:
fffff880`033b0a18 fffff800`0334e551 : 00000000`00000077 00000000`00000000 fffffa80`07fae0a0 00000000`00000000 : nt!KeBugCheckEx
fffff880`033b0a20 fffff800`032fd8d0 : fffffa80`07fae6a0 00000000`00000000 fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x51e71
fffff880`033b0b30 fffff800`032fd85f : 00000000`00000000 00000000`00000001 fffffa80`069fb9e0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`033b0b90 fffff800`032fd5a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`069fb900 : nt!KiInSwapKernelStacks+0x1f
fffff880`033b0bc0 fffff800`03567ede : 6473dbae`561889de 22ed0bb3`9bb708c6 4d71c749`a23172fa d240bf0c`e4567817 : nt!KeSwapProcessOrStack+0x84
fffff880`033b0c00 fffff800`032ba906 : fffff880`02f65180 fffffa80`07252040 fffff880`02f6ffc0 fd1e8454`49caddd8 : nt!PspSystemThreadStartup+0x5a
fffff880`033b0c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+51e71
fffff800`0334e551 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+51e71

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6

FAILURE_BUCKET_ID: X64_0x77_0_VRF_nt!_??_::FNODOBFM::_string_+51e71

BUCKET_ID: X64_0x77_0_VRF_nt!_??_::FNODOBFM::_string_+51e71

Followup: MachineOwner
 
dxgmms1.sys refers to Directx, lots of people have been having issues with Directx and have oinly resoned it by re-installing Directx. Some games install their own version of Directx during installation, sometimes asking for permission first but may other games do it automatically.

Re-install Directx
 
I placed this on another post. Thought it might help. I chased Direct X and software problems for 2 months. Today I found the issue. Considering you moved stuff around I think you had the same problem as me. Hope the following helps:
-------------------------------------

The very same problem has plagued me since March 29th and it has been driving me nuts. I have gone through a TON of troubleshooting too and had replaced a hard drive and a sound card. At times I even felt it was fixed then sadly found out an hour later that it was not. My PC is only 3 years old and I felt it was not old enough to be experiencing problems.

Well today I am confident I found the solution.

Below was the exact error I was receiving:

This would randomly occur in games normally a few minutes in. Just prior to it horrible loud static would come through the speakers. Sometimes it would not blue screen at all it would just reboot or go to a black screen and not recover. I have even had this happen watching YouTube.

What I did to fix: (some of these may not be relevant but it is what i did.)

1.) I found a post where someone reseated their CPU and stated there must have been dirt on the pins because it started working afterwards. I did not see that at all on mine or understand how that could practically happen but I did find that my CPU was stuck in the socket even though I had the lock bar released. After I got it to release with much work I reseated it. I think the weight of the heatsink may had jammed it in. I had had problems in the past with too much pressure on the CPU and it caused games to freeze up. So I reseated it and applied new thermal paste.

2.) I have four DIMMs. I took all of the ram out while I had the CPU heat sink off and make sure I had them paired in accordance with their serial #s so they were in their original sets.

3.) If you have a video card with dual DVI ports try the 2nd DVI port if you are using the first one and vice versa. My thoughts today that maybe one of them went bad or if I used the 2nd one the data flow would be different and it would be less prone to error.

From what I read STOP errors tend to be hardware related. I think my CPU just got wedged down or the 1st DVI port on my video card went bad.

Not sure which but it has been working great even after powering it off and rebooting.

One other note: Most of the help sites I have found refer to this as a Direct X problem or an AMD or Nvidia problem.

In my particular case it was not a software issue at all. I can state this because I bought a brand new Western Digital hard drive, did a fresh install of Windows 7, flashed the bios, then loaded the current version of Catalyst drivers from AMD. This did not fix anything. It just allowed me to run two rounds of a game before a crash. I have seen posts from both Nvidia and AMD users with this problem and therefore believe in many cases it is not a driver issue from either company.

When I shifted my focus from software to checking the hardware I already had I got results.

FYI - possible solution: if your power supply has multiple 6 pin PCI Express power connectors try using the other one / set. Or use an adapter on the molexs

Check all of your power cabling. Especially if you have a 4pin extension cable going to the motherboard's power port for the memory. Reseat it if it does not look secure.

If you only have 2 sticks of ram try seating them in the other set of DIMM slots.

Hope this helps. If not post a response. As I said I have been troubleshooting for nearly 2 months so I can tell you other things I did / tried. Highly frustrating issue. I have seen many of the sites which you have which did not lend much help.
 
Solution