Bluescreen!

[dehness]

-Removed all information

-Removed all information

 

[Tews]

Unfortunately the report did not include any .dmp files.. navigate to c:/windows/minidump and zip up any .dmp files and attach them to your next post for analysis..

 

[dehness]

-Removed all information

 

[Tews]

Your .dmp file is showing a VIDEO_TDR_FAILURE (116) error with nvlddmkm.sys, which the driver for your graphic card. Completely remover your graphic drivers and download the latest version... Nvidia Drivers For more information on what a VIDEO_TDR_FAILURE (116), is read this thread... STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

FAULTING_IP: 
nvlddmkm+aca80
900b8a80 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8e38cb74 909fe92c 00000116 86108008 900b8a80 nt!KeBugCheckEx+0x1e
8e38cb98 909ff74b 900b8a80 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8e38cbbc 90a2f92c 00000000 00000102 865db008 dxgkrnl!TdrIsRecoveryRequired+0xb8
8e38cc34 90a59a32 fffffcfb 0000096f 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8e38cc5c 90a5a153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8e38cc98 90a368f0 8e38cc90 8283febf 865db008 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8e38cd28 90a5b4b7 865db008 8283febf 865db008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8e38cd3c 90a5b573 865db008 00000000 8666a948 dxgmms1!VidSchiRun_PriorityTable+0xf
8e38cd50 829f8d16 865db008 b6a7c6f6 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8e38cd90 8289a159 90a5b4f4 865db008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+aca80
900b8a80 55              push    ebp

SYMBOL_NAME:  nvlddmkm+aca80

IMAGE_NAME:  
FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c7fdb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

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

 

[dehness]

-Removed all information

 

[zigzag3143]

Cool, thanks man. I can actually get into win7 without being in safe mode. Now its reverted back to the original BSOD problem I had, error code 124. I attached the dump file.

Sorry for my computer being so fail... I really appreciate the help.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\010102-21125-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8283e000 PsLoadedModuleList = 0x8297d570
Debug session time: Mon Dec 31 10:42:53.578 2001 (GMT-4)
System Uptime: 0 days 0:00:09.125
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 85746594, 0, 0}

Probably caused by : hardware

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

 

[dehness]

-Removed all information

 

[ttran]

Stop code 124 is hardware related. Please do these test to find out what can be problem
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Look for temperature using speedfan:
SpeedFan - Access temperature sensor in your computer

Run this free video stress test:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

 

[dehness]

-Removed all informationhttp://www.sevenforums.com/hardware...ta-dvd-rom-wont-work-together.html#post878255