Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random Freeze Ups (New Build)


  • Please log in to reply
12 replies to this topic

#1 xEnvious

xEnvious

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 20 January 2011 - 08:28 PM

Hello all, I've recently built a new computer and before I address my problem, here are my specs:

Intel Core i5-2500k 3.3Ghz
Asus P8P67 Pro
g.skill 1333 4gb (x2)
Corsair TX650W
EVGA Geforce GTX 460 768mb
Samsung Spinpoint F3 1TB

I know the gfx card and PSU works because I've used it on an old computer for many months now. So, the first issue was getting the computer to boot up properly: it wouldn't. But it was 3 in the morning so I called it a night. After coming home for school over 12 hours later, computer magically booted up again. I proceeded to install W7 64 bit and all was going well. As I was installing drivers, the computer would freeze up. The times it would freeze up would be random: at BIOS, while installing drivers, or simply being afk. I've googled around for solutions and the closest thing I found was this site. I tried everything in post #14 also by the OP. However, this still didn't fix the random freezes.

As of now, I am trying out each RAM stick by itself and it has been going at a record 30 minutes. The second stick lasted roughly 15 minutes, screen started to flicker, and I saw a split second of error popping out from the toolbar saying there was an error with the graphics card drive of some sort (it was too short to make out of anything but I saw 266.xx which lead me to think it was the graphics card driver) before the computer restarted itself. However, the computer has been running well for 30 minutes. I will run some memtests and update on that but I want to know your opinion on this matter and whether or not it's a mobo, RAM, or graphics card problem.

Thanks in advance.

Oh and this is the latest dump file I recovered:

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012011-38641-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03043e50
Debug session time: Thu Jan 20 19:42:18.867 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:56.381
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800417e4e0, fffff8801062323c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b723c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800417e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801062323c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+7b723c
fffff880`1062323c 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02ed5b48 fffff880`10b25ef8 : 00000000`00000116 fffffa80`0417e4e0 fffff880`1062323c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02ed5b50 fffff880`10af9867 : fffff880`1062323c fffffa80`05f77000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ed5b90 fffff880`10b25d07 : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`0417e4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02ed5c40 fffff880`0fe37ec1 : fffffa80`03a16d50 00000000`00000080 00000000`00000000 fffffa80`05f73010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02ed5cc0 fffff800`0311ac06 : 00000000`fffffc32 fffffa80`05f92060 fffffa80`036b5040 fffffa80`05f92060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02ed5d00 fffff800`02e54c26 : fffff800`02ff0e80 fffffa80`05f92060 fffff800`02ffec40 fffff880`0124d534 : nt!PspSystemThreadStartup+0x5a
fffff880`02ed5d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+7b723c
fffff880`1062323c 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+7b723c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

Edited by xEnvious, 20 January 2011 - 08:30 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 21 January 2011 - 07:01 AM

Worth reading, IMO, http://forums.techguy.org/windows-vista/793532-bsod-issue.html .

Louis

#3 xEnvious

xEnvious
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 21 January 2011 - 08:19 AM

Thanks for the reply and link, Louis. I actually did try reinstalling the driver by uninstalling it last night. However, the moment the driver uninstalled, the screen went blank and I had no control over anything. The computer was still on: fans running, mobo LEDs green, but there was nothing on the screen. I forced shut down the comp and tried turning it back on. The computer froze again at ASUS POST screen. I turned off the computer again and after waiting for a few minutes, I turned it back on. Windows was starting on low resolution since I had no drivers, and Windows Update searched for a driver. I got that installed, restarted the computer, and installed the nVidia drivers from their site.

The computer survived the night and is still running. So, what I'm wondering is if I'll continue having this problem every time I reformat or if it's a hardware issue. There are a few things I summarized from this:
It couldn't be the memory because I tried each stick individually but I'll run a memtest when I come home (is memtest86+ fine over memtest86?)
It could be the motherboard and possible shorting but all of a sudden is fine now.
It could be the graphics card since BSOD debugging and error pop ups show point it towards that direction.
It's also weird how things are working now after drivers are installed.

I would just like some insight on where the problem may be and want to figure it out within 30 days so I could return anything to newegg if need be or even RMA some parts. I'll update back with the memtest results.

Thanks again

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 21 January 2011 - 11:22 AM

Not that I know...but uninstalling video drivers seemingly should not have had any major impact.

The default Windows drivers should have loaded on reboot.

Freezing and other flaky symptoms...would have me wondering about the PSU.

Since you used parts which are not new...it could be any number of things. If it were me...I'd go back to sqare one...disassemble it all and then assemble, testing at the install/connection of each new item.

If your video card is the problem...that should be evident very quickly, assuming that it's nothing more complicated.

FWIW: I don't suggest ever using Windows Update to obtain drivers, go to the appropriate motherboard/system/component website. Those sites will be more current and probably won't guide you to an inappropriate driver download/install.

<<I know the gfx card and PSU works because I've used it on an old computer for many months now.>>

That statement makes both suspects, IMO.

Memtest86+ is the way to go, known problems with the older Memtest86. See Known Problems, http://en.wikipedia.org/wiki/Memtest .

Memtest86+ Guide-How To's - Overclockers Forums - http://www.overclockers.com/forums/showthread.php?t=409152

Louis

#5 xEnvious

xEnvious
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 21 January 2011 - 01:55 PM

Hey there, Louis.

The computer is working fine but I'm just worried about future times when I have to reformat and whatnot. I'd like to keep it the way it is yet I'm really itching to know what the problem is.

So apparently memtest86+ doesn't work for sandy bridge architecture or something. It doesn't show either RAM speed even when I tried one stick at a time. Gives me an error along the lines of "708k e820 off"

I'm also curious to ask why you would think the graphics card or PSU might be the problem if they were seemingly working fine on an older build?

Thanks again.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 21 January 2011 - 05:43 PM

One of the most basic lessons life teaches some of us...what worked yesterday...may not function properly tomorrow or the day after.

Man-made items are rife with flaws, some detected, some undetected.

The advantage that new components have over old, used components...a warranty.

Louis

#7 xEnvious

xEnvious
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 24 January 2011 - 06:38 PM

Hello again.
I'm back after a few tests. I tried using another video card (EVGA GeForce 8800 GTS) and did a clean install. Ran for almost 24 hours with no errors or weird shutdowns. Now, I switched back to the GeForce 460 GTX and hopefully everything will go well from here and it was just a bad installation of Windows 7 of some sort.

Thanks for the help, Louis.
Will report back soon if the problem persists or new ones pop up *knocks on wood*

EDIT: Spoke too soon. Screen flickered and turned off but monitor stays on. Another BSOD about nvlddmkm.sys. Went ahead and filed a RMA.

Edited by xEnvious, 24 January 2011 - 07:28 PM.


#8 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 24 January 2011 - 09:39 PM

Keep us posted :).

Louis

#9 Aaron21

Aaron21

  • Members
  • 28 posts
  • OFFLINE
  •  
  • Local time:01:16 AM

Posted 27 January 2011 - 10:13 PM

I was having similar issues, see "Randomly freezes". It turned out to be the Motherboard.
Just a thought, Good Luck.

#10 xEnvious

xEnvious
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 06 February 2011 - 02:02 AM

So I'm back again after my comp magically running well for so long. While browsing the internet, my monitor starts to go on and off and the computer just freezes up so I have to force turn it off. I boot up the PC again, choose "start Windows normally". When Windows loads up, I notice my screen is the regular 800x600 resolution and I see this familiar "1033" error as locale ID in the BSOD error window and it immediately freezes again. This time, I turn off the computer and unplug the PSU for a few minutes and turn it back on. While it's booting up, it stays on the Marvell screen and says "Overclocking failed. Press F1 to go to setup" so I went to set up and just clicked "save & exit" without changing anything. Also, I haven't done any OC'ing so everything's running on stock. During this time, the BOOT_LED light is red. POST, BIOS, Windows loading screen and when my desktop should load up, the screen goes on and off again. While doing this, the CPU_LED goes red for a few seconds then it goes away and the computer doesn't respond to anything while all fans are running. Since it's late now, I'm planning to swap video cards again to see if that's the problem.

Can anyone shed a light and see what else I can try?

short update: ran W7 in safe mode and it actually loads the desktop so I'm guessing it's a driver issue or the graphics card is faulty :(
another short update: wow this is like boy who cried wolf. Windows loads up fine now O_o

Edited by xEnvious, 06 February 2011 - 02:22 AM.


#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 06 February 2011 - 12:23 PM

LOL...sometimes strange things happen on computers, better to be lucky :).

Louis

#12 xEnvious

xEnvious
  • Topic Starter

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:16 AM

Posted 24 March 2011 - 11:19 AM

Hello, I am back with 2 replaced parts: motherboard and graphics card.

The motherboard was due to Intel recalling their Sandy Bridge motherboards and the graphics card started acting up again with blank screens, etc. After being desktopless for 2 days, it seems like the graphics card was the verdict and everything is working fine now. *knocks on wood*

Thanks Louise for helping, you can now close this thread :)

#13 hamluis

hamluis

    Moderator


  • Moderator
  • 55,902 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:16 AM

Posted 24 March 2011 - 03:19 PM

We don't ordinarily close threads...they may be useful to other members now or in the future.

Happy computing :).

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users