New
#21
Could you enable driver verifier?
Driver Verifier - Enable and Disable
Might you have a spare video card by any chance?
Could you enable driver verifier?
Driver Verifier - Enable and Disable
Might you have a spare video card by any chance?
I enabled Driver Verifir and restarted my pc.. BSOD when booting: Attachment 91941
no, i haven't another video card!
Stop code 24 with ntfs.sys was blamed, which is your hard drive controller driver. Please run Disk Check and HD diagnostic: HD Diagnostic
BUGCHECK SUMMARY:
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.385\081810-18564-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\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`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50 Debug session time: Wed Aug 18 18:01:45.248 2010 (UTC + 7:00) System Uptime: 0 days 0:00:12.386 Loading Kernel Symbols ............................................................... ..................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff880031a69a8, fffff880031a6210, fffff80002aac2b3} Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+23f ) Followup: MachineOwner ---------
My HD completed both test without error.
(BSOD while playing zinga poker: Attachment 91964)
Well let's go for a hardware approach.
Disable or remove your Yukon network adapter, if possible. If you can't unlug it, go to Device Manager, right-click on it, and select Disable.
Then run this video card test: Video Card - Stress Test with Furmark
Be sure to report the max temp it achieves.
Do you have a friend that would lend you his video card?
...Summary of the Dumps:Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Aug 18 10:25:30.683 2010 (UTC - 4:00) System Uptime: 0 days 0:18:48.400 BugCheck 50, {fffff6fc8e611c80, 0, fffff80002aeb2e2, 2} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 ) BUGCHECK_STR: 0x50 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
after the test can i enable again yukon networl adapter?
no nobody can't lend me a video card!
I left work FurMark for 20 min, there wasn't artifacts and my GPU reached 79░C
Here there are a lot of Dump File: Attachment 92826
Is the Yukon Wireless adapter disabled in Device Manager?
I still see drivers loaded in RAM:...Summary of the Dumps:Code:yk62x64.sys Mon Jun 14 03:39:16 2010Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 23 12:55:21.287 2010 (UTC - 4:00) System Uptime: 0 days 1:18:36.004 BugCheck 3B, {c0000005, fffff80002df708e, fffff88007ff4d40, 0} Probably caused by : memory_corruption ( nt!MiApplyRawFixups+1e ) BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 23 07:21:31.903 2010 (UTC - 4:00) System Uptime: 0 days 0:11:27.010 BugCheck A, {fffffa8805da76f0, 2, 1, fffff80002a92a16} Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+256 ) BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 23 05:14:06.303 2010 (UTC - 4:00) System Uptime: 0 days 0:55:50.020 BugCheck 50, {fffff68012068a98, 0, fffff80002a48a37, 2} Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b ) BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 22 12:17:36.934 2010 (UTC - 4:00) System Uptime: 0 days 0:05:55.041 BugCheck 50, {fffffa801b07e658, 0, fffff80002aa2b9b, 2} Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f ) BUGCHECK_STR: 0x50 PROCESS_NAME: MsMpEng.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 22 07:32:31.118 2010 (UTC - 4:00) System Uptime: 0 days 0:47:41.850 BugCheck 50, {fffffa800d93c258, 0, fffff80002aa8b9b, 2} Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f ) BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Aug 21 13:14:58.978 2010 (UTC - 4:00) System Uptime: 0 days 0:26:46.085 BugCheck 50, {fffffa800c560f70, 0, fffff80002abc3fa, 2} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 ) BUGCHECK_STR: 0x50 PROCESS_NAME: dwm.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии