Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

My new comp hanged ( Blackscreeen) randomly


  • Please log in to reply

#16
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I only wanted to ensure that you could download and install the updates. It was not intended that they would solve the problem - if you could NOT, that would have been indicative of another possible cause- which was raised in my mind by the event logs.


NO NEED to apologise, really - stressful for you not to have it running corrctly and an easy mistake to make.

PLEASE send me the error logs from system
  • 0

Advertisements


#17
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
I manage to just ticking error logs / system . But it still showing the "Critical" log.



Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 19/09/2012 20:47:35

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/09/2012 15:52:27
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/09/2012 11:46:02
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/09/2012 11:14:59
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/09/2012 10:04:29
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/09/2012 9:56:44
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/09/2012 9:18:38
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 15/09/2012 20:47:01
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 14/09/2012 16:46:40
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 12:58:35
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 12:46:09
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 12:30:38
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 11:47:50
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 11:40:20
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/09/2012 3:27:47
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 11/09/2012 15:21:25
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 12:07:41
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 11:50:14
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 11:41:25
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 9:56:39
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 8:10:30
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 7:53:07
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 7:42:38
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 7:33:18
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 6:15:11
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 5:44:23
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/09/2012 5:38:37
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/09/2012 15:52:29
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 23:51:02 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 16/09/2012 11:46:04
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:40:59 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 16/09/2012 11:15:03
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 18:32:29 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 16/09/2012 10:04:33
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 18:01:44 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 16/09/2012 9:56:48
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 17:54:38 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 16/09/2012 9:18:42
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 17:16:54 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 15/09/2012 20:47:05
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 4:45:21 on ?16/?9/?2012 was unexpected.

Log: 'System' Date/Time: 14/09/2012 16:46:44
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 0:44:09 on ?15/?9/?2012 was unexpected.

Log: 'System' Date/Time: 13/09/2012 12:29:45
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 13/09/2012 11:16:30
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 12:58:42
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 12:58:39
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 20:55:09 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 12/09/2012 12:46:14
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 12:46:13
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 20:44:38 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 12/09/2012 12:30:43
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 12:30:42
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:50:50 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 12/09/2012 11:47:55
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 11:47:54
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:44:20 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 12/09/2012 11:40:25
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 11:40:25
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff880525e0000, 0x0000000000000001, 0xfffff8800fe02f3a, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Log: 'System' Date/Time: 12/09/2012 11:40:25
Type: Error Category: 0
Event: 1005 Source: Microsoft-Windows-WER-SystemErrorReporting
Unable to produce a minidump file from the full dump file.

Log: 'System' Date/Time: 12/09/2012 11:40:23
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:32:47 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 12/09/2012 3:27:53
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 12/09/2012 3:27:52
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff880525e0000, 0x0000000000000001, 0xfffff8800fe06f3a, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Log: 'System' Date/Time: 12/09/2012 3:27:52
Type: Error Category: 0
Event: 1005 Source: Microsoft-Windows-WER-SystemErrorReporting
Unable to produce a minidump file from the full dump file.

Log: 'System' Date/Time: 12/09/2012 3:27:51
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 11:20:23 on ?12/?9/?2012 was unexpected.

Log: 'System' Date/Time: 11/09/2012 15:21:31
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 11/09/2012 15:21:29
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 23:17:35 on ?11/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 13:16:41
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 13:10:41
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 12:07:46
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 12:07:45
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000117 (0xfffffa800c903010, 0xfffff880067b96cc, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\090912-8892-01.dmp. Report Id: 090912-8892-01.

Log: 'System' Date/Time: 09/09/2012 12:07:44
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 20:04:14 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 11:50:19
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 11:50:20
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff880527e0000, 0x0000000000000001, 0xfffff88010052a5b, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Log: 'System' Date/Time: 09/09/2012 11:50:20
Type: Error Category: 0
Event: 1005 Source: Microsoft-Windows-WER-SystemErrorReporting
Unable to produce a minidump file from the full dump file.

Log: 'System' Date/Time: 09/09/2012 11:50:18
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:43:25 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 11:41:30
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 11:41:26
Type: Error Category: 0
Event: 6 Source: Microsoft-Windows-Kernel-General
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.

Log: 'System' Date/Time: 09/09/2012 11:41:29
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 19:39:39 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 9:56:44
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 09/09/2012 9:56:43
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 17:53:50 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 8:10:32
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 16:00:07 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 7:53:11
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 15:49:38 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 7:42:43
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff880527e0000, 0x0000000000000001, 0xfffff8800fffdf3a, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Log: 'System' Date/Time: 09/09/2012 7:42:43
Type: Error Category: 0
Event: 1005 Source: Microsoft-Windows-WER-SystemErrorReporting
Unable to produce a minidump file from the full dump file.

Log: 'System' Date/Time: 09/09/2012 7:42:42
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 15:35:18 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 7:33:22
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 14:18:11 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 6:15:15
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 14:12:23 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 5:44:27
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 13:39:37 on ?9/?9/?2012 was unexpected.

Log: 'System' Date/Time: 09/09/2012 5:38:41
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 6:15:57 on ?9/?9/?2012 was unexpected.
  • 0

#18
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Well you only have to look yourself at the unexpected shutdowns

There are six on the 16 Sept alone.


Every time that occurs of course, data that is being written is likely to be corrupted

Start with this, I know you say you have done it, MEMTEST but please do it this way

See my post 2 and 4 on this link
adopt the procedure for your ram configuration and test that way please

http://www.geekstogo...sod-page-fault/

Before you run the memtest send me please the minidump files as I see you have had BSOD - zip them please
send them as attachments the ones from the 12 Sept will do
  • 0

#19
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
"Before you run the memtest send me please the minidump files as I see you have had BSOD - zip them please
send them as attachments the ones from the 12 Sept will do"

When i opened the minidump folder, this is the only one i saw. Which is dated 9/9/2012.
Hope it still can of some use.

Attached Files


  • 0

#20
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Yiour dump file

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0464f000 PsLoadedModuleList = 0xfffff800`04894e90
Debug session time: Sun Sep 9 08:05:07.299 2012 (UTC - 4:00)
System Uptime: 0 days 0:14:59.314
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa800c903010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880067b96cc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
VirtuWDDM+86cc
fffff880`067b96cc ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`04abb4f0 fffff880`048d85f7 : fffffa80`0c903010 fffff880`04924e93 fffffa80`0c903010 fffff880`048a6807 : watchdog!WdDbgReportRecreate+0xa3
fffff880`04abba10 fffff880`048d92bc : fffff8a0`02193ed0 fffff8a0`02193ed0 00000000`00000080 fffffa80`0c903010 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`04abba60 fffff880`048ad6b3 : 00000000`00000001 fffffa80`0acef000 00000000`00000000 fffff880`0000002e : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`04abba90 fffff880`048d9e0f : 00000000`0000000f ffffffff`fffe7960 fffffa80`0c903010 00000000`00000010 : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`04abbb40 fffff880`049a8ec1 : fffffa80`0c3ba350 00000000`00000080 00000000`00000000 fffffa80`0acdf010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04abbbc0 fffff800`0496ccce : 00000000`01b6cde1 fffffa80`0ad0b770 fffffa80`0698a840 fffffa80`0ad0b770 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04abbc00 fffff800`046c0fe6 : fffff880`04b65180 fffffa80`0ad0b770 fffff880`04b6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04abbc40 00000000`00000000 : fffff880`04abc000 fffff880`04ab6000 fffff880`04abafd0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
VirtuWDDM+86cc
fffff880`067b96cc ?? ???

SYMBOL_NAME: VirtuWDDM+86cc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VirtuWDDM

IMAGE_NAME: VirtuWDDM.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f5dba1d

FAILURE_BUCKET_ID: X64_0x117_IMAGE_VirtuWDDM.sys

BUCKET_ID: X64_0x117_IMAGE_VirtuWDDM.sys





Please proceed with the ram check as detailed it is either that or the graphics driver, I suspect the ram
  • 0

#21
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Please dont be offended , but honestly , my intuition tells me it would be the GPU or the GPU driver.
As i tried to install my brother's GTX 660 Ti and start up again , used for an hour and do some stress test and the computer working perfectly fine, as perfect when i removed my 460 and only using onboard display. ( Been running onboard for at least 3 days to a week already. I didnt even turn off my computer and just let it run and so far no crashes .

Anyway, i will proceed the MEMTEST as you instructed too, coz it would still be best to narrow down to the only option when there's 2 left only.
But i gotta need some maybe a day to get the result. Busy friday here.

And thank you , i mean really thank you for doing all these, its really take so much time and energy analyzing and processing these data.
  • 0

#22
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I agree to the extent that the crash I had analysed for you, using a service that I subscribe to, shows beyond doubt that - THAT crash was the graphics and connected drivers

HOWEVER the reason I suspect RAM and I may well be wrong is all the previous reports we have obtained from the event viewer.
  • 0

#23
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Sigh , back to square one again .
I changed my GPU to an old model ATI Radeon HD6770. And it still hanged after a day use ( cleaned up all the old driver b4 use ) .
I started the Memtest as you say now, just finished tested 2 RAMs individually and waiting the result for the Single Channel mode.

would it be possible if the problem is caused by a bad window install that fail to communicate with the GPU driver ?
Coz if the memtest came out clean , i might consider re-installing window and give it a try.

Edited by Honlo, 23 September 2012 - 08:38 PM.

  • 0

#24
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Lets wait and see what memtest says

Edited by Macboatmaster, 30 September 2012 - 08:41 AM.

  • 0

#25
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Argh ... I got the result .

I ran the test like that ,
Let 2 Ram stick be A & B .
Let 4 Ram slot as Slot 1 ,2 ,3 ,4 .

A1 > B1 > A2 > B2 .... etc
No error occurred .
Then i run it on Single Channel , that is
A1B2 , no error occurred.
Then i run it on Dual Channel , that is
A1B3, no error occurred.

Each memtest i tried about 3-5 times respectively.
the result is completely clean.

Edited by Honlo, 24 September 2012 - 08:50 PM.

  • 0

Advertisements


#26
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
OKAY
Thanks
Try this please

http://msdn.microsof...1(v=vs.85).aspx

see actions to prevent

so
1. RUN please a chkdsk /r
either from the GUI of computer
eg right click drive
click properties
click tools
click error checking
click check now
click to check the second box so that both are now checked
click start and follow as instructed.
OR
cmd prompt with admin rights
type
chkdsk /r
key enter
and agree on restart
type exit
key enter and restart

Then please send results as here
http://www.sevenforu...viewer-log.html
on getting the results from event viewer
windows logs
application
wininit
click copy on right pane
paste please as the results not as a file that I have to open

Edited by Macboatmaster, 26 September 2012 - 09:44 AM.

  • 0

#27
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Sorry if there is some chinese word that u might not understand , i could translate it if its very key.
But dont think the log indicated any problem.
Also i reinstalled window twice and still the random crashes still exist when i install any video card.


記錄檔名稱: Application
來源: Microsoft-Windows-Wininit
日期: 2012/9/30 下午 05:14:09
事件識別碼: 1001
工作類別: 無
等級: 資訊
關鍵字: 傳統
使用者: 不適用
電腦: GODBOY-PC
描述:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
127744 file records processed.

File verification completed.
676 large file records processed.

0 bad file records processed.

2 EA records processed.

67 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
182766 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
127744 file SDs/SIDs processed.

Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
27512 data files processed.

CHKDSK is verifying Usn Journal...
35849080 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
127728 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
12161934 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

125032447 KB total disk space.
76086624 KB in 95461 files.
64748 KB in 27513 indexes.
0 KB in bad sectors.
233339 KB in use by the system.
65536 KB occupied by the log file.
48647736 KB available on disk.

4096 bytes in each allocation unit.
31258111 total allocation units on disk.
12161934 allocation units available on disk.

Internal Info:
00 f3 01 00 69 e0 01 00 26 89 03 00 00 00 00 00 ....i...&.......
47 01 00 00 43 00 00 00 00 00 00 00 00 00 00 00 G...C...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

事件 Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-09-30T09:14:09.000000000Z" />
<EventRecordID>1980</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>GODBOY-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
127744 file records processed.

File verification completed.
676 large file records processed.

0 bad file records processed.

2 EA records processed.

67 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
182766 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
127744 file SDs/SIDs processed.

Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
27512 data files processed.

CHKDSK is verifying Usn Journal...
35849080 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
127728 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
12161934 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

125032447 KB total disk space.
76086624 KB in 95461 files.
64748 KB in 27513 indexes.
0 KB in bad sectors.
233339 KB in use by the system.
65536 KB occupied by the log file.
48647736 KB available on disk.

4096 bytes in each allocation unit.
31258111 total allocation units on disk.
12161934 allocation units available on disk.

Internal Info:
00 f3 01 00 69 e0 01 00 26 89 03 00 00 00 00 00 ....i...&amp;.......
47 01 00 00 43 00 00 00 00 00 00 00 00 00 00 00 G...C...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>
  • 0

#28
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
The chkdsk results are certainly OK
From the link I sent you in post 26 and from your dump file in post 20

BUT especially from this

As i tried to install my brother's GTX 660 Ti and start up again , used for an hour and do some stress test and the computer working perfectly fine, as perfect when i removed my 460 and only using onboard display. ( Been running onboard for at least 3 days to a week already. I didnt even turn off my computer and just let it run and so far no crashes


I am reasonably sure it must be an issue with, other drivers or applications on the computer. I do not think it is a temperature issue, as the stress testing would raise temps, so it would likely have crashed then.

I think it best if you send me these please

1. Pitstop
(I know you attached some screenshots before but please send me the URL from Pitstop as described.)

PLEASE NOTE - may I ask that you do not make any changes, recommended.

It is of course your computer, but if you make changes after sending me the results, it makes my job harder.
Run this please and send me the results

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).

Go to: http://www.pCPitstop.com

Click on "Free Computer Check-up" listed below PC Pitstop OverDrive

In the User Login - Click on "Sign up FREE!" OR YOU CAN RUN THE TEST ANON. without signing up. - you will see that at the end of that screen. The results will still be saved long enough for me to look at them.

If you do wish to sign up - for some reason

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 do not follow any procedures, until I have seen it for the reason outlined above

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration.

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.


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.

PLEASE DO NOT RUN ANY other tests on offer




2. Please send me this as well

1, diownload the free edition
http://www.piriform....speccy/download

2. Run and send me the URL
http://www.piriform....cy/using-speccy
see publish to web

Edited by Macboatmaster, 30 September 2012 - 09:56 AM.

  • 0

#29
Honlo

Honlo

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Im not sure u want me to perform both test during my Display card is installed or not .
But here's the 2 links for the tests using onboard .

http://www.pcpitstop...?conid=25081296
http://speccy.pirifo...LX6aA6QpnnIxunC



if you want me to test it with display card installed , but tell me.
I will do it again.
  • 0

#30
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts

if you want me to test it with display card installed , but tell me.


It makes no difference as all I wanted - was details of what is on the coomputer, the system etc.

I am signing off it is 0057 UK time I will be back about 1800

I will post as soon as posible after when I have had a look at the results

I have had a quick glance and you have

MSIE 7.0
on Windows 7.

That IE 7 is way out of date - if the report is correct
IE9 is the current version for 7
Not only does it have vastly increased funtionality, but also increased security and you should not be running IE7

I actually thought that you could not install IE7 on Windows 7 ( as I thought it cam with IE8 - I thought you could only use IE7 in XP Mode - so maybe the report is wrong.
Would you please check what you do have and indeed are you running XP mode etc.

Edited by Macboatmaster, 01 October 2012 - 06:28 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP