Another one

[happycamper1]

Got a 0x00000a after all the driver issue have been fix, please help

 

[ttran]

i can't see much from the minidump. It looks like you have all drivers up to date. Because of that, I would recommend to enable Driver Verifier to know what drivers are bad, then we will go from there:
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Also, please run System files check:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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$DI01.669\062810-21387-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Tue Jun 29 13:04:22.042 2010 (UTC + 7:00)
System Uptime: 0 days 0:06:54.322
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2f, 2, 1, fffff80002ad0e23}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+43 )

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

~Tuan

 

[happycamper1]

just hit another one, could this because of a bad drive? I have 3 drivers on mine, and i think the F drive is the problem here the attachment please help.

 

[ttran]

You partly right. As the newest minidump indicate. This might be a hard drive issue. The bugcheck code is 24, which is usually hard drive, also ntfs.sys is hard drive controller driver. I'm not a hardware specialist, but I would suggest you to do these 2 things, then you can reply back the result to us, someone here will take a look at it
First of all, please run a check disk:
http://www.sevenforums.com/tutorials/433-disk-check.html
Next, please run HD diagnostic test:
HD Diagnostic

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.721\062810-20888-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Tue Jun 29 13:25:49.871 2010 (UTC + 7:00)
System Uptime: 0 days 0:18:34.790
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003b59fa8, fffff88003b59810, fffff80002ae6972}

Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )

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

~Tuan

 

[happycamper1]

since the drive has nothing on it besides my games file should I just unplug the drive and use the other 2 ?

 

[happycamper1]

did the diskcheck test, it came out clean, however it seems that both time it crashes, it was using files from the drive, should I go ahead and do what I had mention before?

 

[ttran]

You have 3 hard drives??? And you guess that the problem come from particular one? Sorry I'm not quite clear what u were asking friend??

 

[happycamper1]

Yes, the game files are from one particular hard drive and it uses only the files on that hard drive, everytime I launch the game from it, after a while the particular drive would crash, i just saw on the bsod, it said to check that particular drive as well. I guess it is safe to just disconnect

 

[ttran]

Have you ever tried to re-install the games? Also run the HD diagnostic as I mentioned earlier to check that particular hard drive

 

[happycamper1]

I am now reinstalling the games through steam, I disconnect the HD, and now using the scan disk option and the other ones as well.