I have had my computer up and running for a wekk and i keep getting these crashes, this is the following report of them -
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Additional information about the problem:
BCCode: 34
BCP1: 00050830
BCP2: 8E17F870
BCP3: 8E17F450
BCP4: 82E88D2E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
I have ran Memtest86+ and no errors where found
also when you respond than you try to simplify it? I am not a girl who easily understand all the technical stuff.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Additional information about the problem:
BCCode: 34
BCP1: 00050830
BCP2: 8E17F870
BCP3: 8E17F450
BCP4: 82E88D2E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
I have ran Memtest86+ and no errors where found
also when you respond than you try to simplify it? I am not a girl who easily understand all the technical stuff.
bumping cause i really need help
Ok... First we will need the crash files....(.dmp) .. they are located in c:/windows/minidump ... you will need to zip them up, then attach them (use the paperclip icon) to your next post... we'll go from there..
can you tell me how i can get access to them? i know where to find them just says i am not allowed access to them
You will need to take ownership of them... follow this easy tutorial to do this... Adds Take Ownership Shortcut when Right Click on File, Folder or Drive... Once you have followed the tutorial, all you will have to do is right click on the file and select take ownership... then you will be able to zip them up... 
Take Ownership Shortcut
Take Ownership Shortcut
i did that, tooik ownership but it still won't let me upload
Copy the files to your desktop..right click on the flle .. select send to ... select Compressed (zipped folder) ... this will copy them as a zip file that you can then attach to your next post...
Attachment 88170
i think that is it. I apologise for my lack of knowledge in all this all I know is I am a gamer girl that wants to get her game on but the BSOD are stressing me out lol thank you very much for being patient with me
i think that is it. I apologise for my lack of knowledge in all this all I know is I am a gamer girl that wants to get her game on but the BSOD are stressing me out lol thank you very much for being patient with me
Thats what we're here for...Looking at them now... may take a few minutes ... everyone starts out sometime...
still i really appreciate it =D
Ok... Ive looked at the .dmp files but they were inconclusive, so if you're up to it, were going to have to run some more tests in order to pin it down some more...
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.
We need to enable driver verifier in order to get more conclusive .dmp files... follow these instructions..
Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
We are also getting a Memory Management error, which may indicate bad RAM...
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
This should run overnight for the best results..
I also found SPTD.sys in your loaded driver list...This is notorious for causing crashes... Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.
We need to enable driver verifier in order to get more conclusive .dmp files... follow these instructions..
Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
We are also getting a Memory Management error, which may indicate bad RAM...
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
This should run overnight for the best results..
I also found SPTD.sys in your loaded driver list...This is notorious for causing crashes... Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 00041289, The subtype of the bugcheck. Arg2: 06664001 Arg3: 00001b76 Arg4: 0440d209 Debugging Details: ------------------ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 82b029c7} Probably caused by : ntkrpamp.exe ( nt!KeWaitForGate+13d ) Followup: MachineOwner --------- .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, 82b029c7} Probably caused by : ntkrpamp.exe ( nt!KeWaitForGate+13d ) Followup: MachineOwner --------- ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 82b5681a, 8db8fb48, 8db8f720} Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+814 ) Followup: MachineOwner ---------
ok will do all that, got rid of daemon and all that, not as for the sptd remover tool, do i need it for anything important? cause it warns me that it will make applications that rely on it malfunction. waiting on ym computer to crash now, when it does do i upload the crash file? i will run memtest while i sleep already have it, did it once it said no errors
Run the tool, its ok.... Run memtest overnight... Upload any new .dmp files... You're doing GREAT!!
ahah thank you. this has been proper stressing my brain out, i am sure my own brain is gonna BSCOD on me soon. I shut down my computer and left it and turned it off at the wall for a few minutes cause it seems to crash within the first few hours of me turning the computer on. weirdly tho in the evenings i could be running a game, on the net, on msn and skype and no problems at all lol. it was crashing while on firefox which i uninstalled earlier cause it kept crashing (the programme not the computer) so on google chrome now
again thank you, i cannot say it enough. once we figure it out i can call he company who built it for me and get new ram sticks if needed i already rang and asked whether i would be charged and they said i wouldn't . good cause i didn't spend them my year's savings for a faulty computer lol
again thank you, i cannot say it enough. once we figure it out i can call he company who built it for me and get new ram sticks if needed i already rang and asked whether i would be charged and they said i wouldn't . good cause i didn't spend them my year's savings for a faulty computer lol
Thats good to know... takes a load off your mind I bet!
it kinda does but i am always worried they will change their mind and stiff me......
erm...thats sounds wrong...
i am worried they will backtrack on that promise is what i should have said
erm...thats sounds wrong...
i am worried they will backtrack on that promise is what i should have said
ok ran memtest over night no errors found, did everything else you asked. I also got sent a programme by my manufactourers and told to run it and then install windows again but crash still happened, these are the last 2 minidumps
Attachment 88520
Attachment 88520
Quote:
STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Quote:
ccHPx86.sys Fri Jun 19 19:23:00 2009
GEARAspiWDM.sys Mon May 18 08:16:53 2009
NAVENG.SYS Mon Jun 29 15:54:25 2009
NAVEX15.SYS Mon Jun 29 15:54:22 2009
netr73.sys Sun Sep 23 23:09:09 2007
SRTSP.SYS Mon Jun 22 22:12:04 2009
SRTSPX.SYS Mon Jun 22 22:15:26 2009
SYMEFA.SYS Tue Jun 23 17:50:40 2009
SYMEVENT.SYS Wed Jun 24 16:14:58 2009
SYMFW.SYS Mon Jul 06 20:21:46 2009 (4A52951A)
SymIMv.sys Mon Jun 22 19:04:43 2009 (4A400E0B)
SYMNDISV.SYS Mon Jul 06 20:25:19 2009 (4A5295EF)
SYMTDI.SYS Mon Jul 06 20:21:23 2009
GEARAspiWDM.sys Mon May 18 08:16:53 2009
NAVENG.SYS Mon Jun 29 15:54:25 2009
NAVEX15.SYS Mon Jun 29 15:54:22 2009
netr73.sys Sun Sep 23 23:09:09 2007
SRTSP.SYS Mon Jun 22 22:12:04 2009
SRTSPX.SYS Mon Jun 22 22:15:26 2009
SYMEFA.SYS Tue Jun 23 17:50:40 2009
SYMEVENT.SYS Wed Jun 24 16:14:58 2009
SYMFW.SYS Mon Jul 06 20:21:46 2009 (4A52951A)
SymIMv.sys Mon Jun 22 19:04:43 2009 (4A400E0B)
SYMNDISV.SYS Mon Jul 06 20:25:19 2009 (4A5295EF)
SYMTDI.SYS Mon Jul 06 20:21:23 2009
Update your older drivers, particularly the one in red font.
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
If you need help, please post and ask.
so hardware. means ram problem? should i just get new ones? its a new computer so under warranty
my bios were reset btw the manufacturers sent me a probgramme to deal with bios
This one is an error code A which is another hardware related error code.
Follow the advice in my post above and lets see what happens.
Quote:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\073110-26114-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82e54000 PsLoadedModuleList = 0x82f9c810 Debug session time: Sat Jul 31 13:30:32.877 2010 (GMT-4) System Uptime: 0 days 0:59:34.469 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {d0e5e3f4, 2, 0, 82ebdd8a} Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+138 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: d0e5e3f4, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82ebdd8a, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82fbc718 Unable to read MiSystemVaType memory at 82f9c160 d0e5e3f4 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTimerExpiration+138 82ebdd8a 8b48fc mov ecx,dword ptr [eax-4] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 82f7ac0c -- (.trap 0xffffffff82f7ac0c) ErrCode = 00000000 eax=d0e5e3f8 ebx=82f7f7b0 ecx=40000000 edx=90e5e3f8 esi=82f7f7b4 edi=82f7f680 eip=82ebdd8a esp=82f7ac80 ebp=82f7acdc iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!KiTimerExpiration+0x138: 82ebdd8a 8b48fc mov ecx,dword ptr [eax-4] ds:0023:d0e5e3f4=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 82ebdd8a to 82e9a7eb STACK_TEXT: 82f7ac0c 82ebdd8a badb0d00 90e5e3f8 82ec45c1 nt!KiTrap0E+0x2cf 82f7acdc 82ebc20e 00037f0a 85ac2648 82f87280 nt!KiTimerExpiration+0x138 82f7ad20 82ebc038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 82f7ad24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTimerExpiration+138 82ebdd8a 8b48fc mov ecx,dword ptr [eax-4] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTimerExpiration+138 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007 FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+138 BUCKET_ID: 0xA_nt!KiTimerExpiration+138 Followup: MachineOwner --------- 0: kd> lmtsmn start end module name 8b9ae000 8b9f6000 ACPI ACPI.sys Mon Jul 13 19:11:11 2009 (4A5BBF0F) 90eb0000 90f0a000 afd afd.sys Mon Jul 13 19:12:34 2009 (4A5BBF62) 90dd9000 90deb000 AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954) 91679000 9168a000 amdppm amdppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07) 8bb01000 8bb0a000 amdxata amdxata.sys Tue May 19 13:57:35 2009 (4A12F30F) 8bad5000 8bade000 atapi atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 8bade000 8bb01000 ataport ataport.SYS Mon Jul 13 19:11:18 2009 (4A5BBF16) 92009000 92585000 atikmdag atikmdag.sys Tue Apr 06 21:37:59 2010 (4BBBE1F7) 91693000 916bf000 atikmpag atikmpag.sys Tue Apr 06 21:23:11 2010 (4BBBDE7F) 8be30000 8be37000 Beep Beep.SYS Mon Jul 13 19:45:00 2009 (4A5BC6FC) 91616000 91658000 BHDrvx86 BHDrvx86.sys Thu Jul 09 20:59:15 2009 (4A569263) 90db3000 90dc1000 blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 8b83a000 8b842000 BOOTVID BOOTVID.dll Mon Jul 13 21:04:34 2009 (4A5BD9A2) 980ae000 980c7000 bowser bowser.sys Mon Jul 13 19:14:21 2009 (4A5BBFCD) 90d38000 90db3000 ccHPx86 ccHPx86.sys Fri Jun 19 19:23:00 2009 (4A3C1DD4) 984a0000 984be000 cdd cdd.dll unavailable (00000000) 930d2000 930e8000 cdfs cdfs.sys Mon Jul 13 19:11:14 2009 (4A5BBF12) 8be11000 8be30000 cdrom cdrom.sys Mon Jul 13 19:11:24 2009 (4A5BBF1C) 8b884000 8b92f000 CI CI.dll Mon Jul 13 21:09:28 2009 (4A5BDAC8) 8bfb1000 8bfd6000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 8b842000 8b884000 CLFS CLFS.SYS Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8bd76000 8bdd3000 cng cng.sys Mon Jul 13 19:32:55 2009 (4A5BC427) 91600000 9160d000 CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716) 931d3000 931e0000 crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 90cbc000 90d20000 csc csc.sys Mon Jul 13 19:15:08 2009 (4A5BBFFC) 90d20000 90d38000 dfsc dfsc.sys Mon Jul 13 19:14:16 2009 (4A5BBFC8) 90cb0000 90cbc000 discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 8c008000 8c019000 disk disk.sys Mon Jul 13 19:11:28 2009 (4A5BBF20) 91b3b000 91b54000 drmk drmk.sys Mon Jul 13 20:36:05 2009 (4A5BD2F5) 931eb000 931f4000 dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 931e0000 931eb000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 92e00000 92e11000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 931c9000 931d3000 Dxapi Dxapi.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 916bf000 91776000 dxgkrnl dxgkrnl.sys Thu Oct 01 20:48:33 2009 (4AC54DE1) 92585000 925be000 dxgmms1 dxgmms1.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 8bb3e000 8bb4f000 fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 8bb0a000 8bb3e000 fltmgr fltmgr.sys Mon Jul 13 19:11:13 2009 (4A5BBF11) 8bde1000 8bdea000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:11:14 2009 (4A5BBF12) 8bf7f000 8bfb1000 fvevol fvevol.sys Mon Jul 13 19:13:01 2009 (4A5BBF7D) 8c16a000 8c19b000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 98ed5000 98ed76c0 gdrv gdrv.sys Thu Mar 12 23:17:32 2009 (49B9D04C) 925dd000 925e2280 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5) 82e1d000 82e54000 hal halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 925be000 925dd000 HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F) 9310c000 9311f000 HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865) 9311f000 93125480 HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863) 93101000 9310c000 hidusb hidusb.sys Mon Jul 13 19:51:04 2009 (4A5BC868) 98029000 980ae000 HTTP HTTP.sys Mon Jul 13 19:12:53 2009 (4A5BBF75) 8c000000 8c008000 hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 90c58000 90cb0000 IDSvix86 IDSvix86.sys Thu May 27 04:00:42 2010 (4BFE26AA) 91a33000 91a40000 kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 931a9000 931b5000 kbdhid kbdhid.sys Mon Jul 13 19:45:09 2009 (4A5BC705) 80ba8000 80bb0000 kdcom kdcom.dll Mon Jul 13 21:08:58 2009 (4A5BDAAA) 91a4f000 91a83000 ks ks.sys Mon Jul 13 19:45:13 2009 (4A5BC709) 8bd63000 8bd76000 ksecdd ksecdd.sys Mon Jul 13 19:11:56 2009 (4A5BBF3C) 8bf2d000 8bf52000 ksecpkg ksecpkg.sys Mon Jul 13 19:34:00 2009 (4A5BC468) 92e1c000 92e2c000 lltdio lltdio.sys Mon Jul 13 19:53:18 2009 (4A5BC8EE) 91b54000 91b6f000 luafv luafv.sys Mon Jul 13 19:15:44 2009 (4A5BC020) 8b81e000 8b829000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89) 92e11000 92e1c000 monitor monitor.sys Mon Jul 13 19:25:58 2009 (4A5BC286) 91a40000 91a4d000 mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 93126000 93131000 mouhid mouhid.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 8babf000 8bad5000 mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) 980c7000 980d9000 mpsdrv mpsdrv.sys Mon Jul 13 19:52:52 2009 (4A5BC8D4) 980d9000 980fc000 mrxsmb mrxsmb.sys Mon Jul 13 19:14:24 2009 (4A5BBFD0) 980fc000 98137000 mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA) 98137000 98152000 mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5) 8bbcc000 8bbd7000 Msfs Msfs.SYS Mon Jul 13 19:11:26 2009 (4A5BBF1E) 8b800000 8b808000 msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 8bd38000 8bd63000 msrpc msrpc.sys Mon Jul 13 19:11:59 2009 (4A5BBF3F) 90c4e000 90c58000 mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 8c1eb000 8c1fb000 mup mup.sys Mon Jul 13 19:14:14 2009 (4A5BBFC6) 9fd85000 9fd98380 NAVENG NAVENG.SYS Thu Jul 01 14:05:22 2010 (4C2CD8E2) 9fc39000 9fd84080 NAVEX15 NAVEX15.SYS Thu Jul 01 14:13:10 2010 (4C2CDAB6) 8be38000 8beef000 ndis ndis.sys Mon Jul 13 19:12:24 2009 (4A5BBF58) 90deb000 90df6000 ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930) 91bb5000 91bc5000 ndisuio ndisuio.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 90fd8000 90ffa000 ndiswan ndiswan.sys Mon Jul 13 19:54:34 2009 (4A5BC93A) 91ad5000 91ae6000 NDProxy NDProxy.SYS Mon Jul 13 19:54:27 2009 (4A5BC933) 90f6b000 90f79000 netbios netbios.sys Mon Jul 13 19:53:54 2009 (4A5BC912) 90f0a000 90f3c000 netbt netbt.sys Mon Jul 13 19:12:18 2009 (4A5BBF52) 8beef000 8bf2d000 NETIO NETIO.SYS Mon Jul 13 19:12:35 2009 (4A5BBF63) 93131000 931a9000 netr73 netr73.sys Sun Sep 23 23:09:09 2007 (46F72A55) 8bbd7000 8bbe5000 Npfs Npfs.SYS Mon Jul 13 19:11:31 2009 (4A5BBF23) 90c44000 90c4e000 nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 82e54000 83264000 nt ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007) 8bc09000 8bd38000 Ntfs Ntfs.sys Mon Jul 13 19:12:05 2009 (4A5BBF45) 8c019000 8c020000 Null Null.SYS Mon Jul 13 19:11:12 2009 (4A5BBF10) 91b6f000 91bb5000 nwifi nwifi.sys Mon Jul 13 19:51:59 2009 (4A5BC89F) 90f43000 90f62000 pacer pacer.sys Mon Jul 13 19:53:58 2009 (4A5BC916) 90dc1000 90dd9000 parport parport.sys Mon Jul 13 19:45:34 2009 (4A5BC71E) 8ba3e000 8ba4f000 partmgr partmgr.sys Mon Jul 13 19:11:35 2009 (4A5BBF27) 98152000 98159000 parvdm parvdm.sys Mon Jul 13 19:45:29 2009 (4A5BC719) 8ba09000 8ba33000 pci pci.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 8baaa000 8bab1000 pciide pciide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17) 8bab1000 8babf000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:11:15 2009 (4A5BBF13) 8bdd3000 8bde1000 pcw pcw.sys Mon Jul 13 19:11:10 2009 (4A5BBF0E) 98159000 981f0000 peauth peauth.sys Mon Jul 13 20:35:44 2009 (4A5BD2E0) 91b0c000 91b3b000 portcls portcls.sys Mon Jul 13 19:51:00 2009 (4A5BC864) 8b829000 8b83a000 PSHED PSHED.dll Mon Jul 13 21:09:36 2009 (4A5BDAD0) 90fc0000 90fd8000 rasl2tp rasl2tp.sys Mon Jul 13 19:54:33 2009 (4A5BC939) 90e00000 90e18000 raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D) 90e18000 90e2f000 raspptp raspptp.sys Mon Jul 13 19:54:47 2009 (4A5BC947) 91a12000 91a29000 rassstp rassstp.sys Mon Jul 13 19:54:57 2009 (4A5BC951) 90c03000 90c44000 rdbss rdbss.sys Mon Jul 13 19:14:26 2009 (4A5BBFD2) 91a29000 91a33000 rdpbus rdpbus.sys Mon Jul 13 20:02:40 2009 (4A5BCB20) 8bff7000 8bfff000 RDPCDD RDPCDD.sys Mon Jul 13 20:01:40 2009 (4A5BCAE4) 8bdf6000 8bdfe000 rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 8bc00000 8bc08000 rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 8bf52000 8bf7f000 rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) 91bc5000 91bd8000 rspndr rspndr.sys Mon Jul 13 19:53:20 2009 (4A5BC8F0) 91776000 917a7000 Rt86win7 Rt86win7.sys Thu Jul 30 07:58:26 2009 (4A718AE2) 91ae6000 91b0c000 RtHDMIV RtHDMIV.sys Thu Jul 16 23:52:43 2009 (4A5FF58B) 92e33000 930d1540 RTKVHDA RTKVHDA.sys Tue Aug 18 05:30:35 2009 (4A8A74BB) 981f0000 981fa000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528) 917f2000 917fc000 serenum serenum.sys Mon Jul 13 19:45:27 2009 (4A5BC717) 90f79000 90f93000 serial serial.sys Mon Jul 13 19:45:33 2009 (4A5BC71D) 8c1e3000 8c1eb000 spldr spldr.sys Mon May 11 12:13:47 2009 (4A084EBB) 98ed8000 98f2b000 SRTSP SRTSP.SYS Mon Jun 22 22:12:04 2009 (4A4039F4) 90fb6000 90fbf080 SRTSPX SRTSPX.SYS Mon Jun 22 22:15:26 2009 (4A403ABE) 98e84000 98ed5000 srv srv.sys Mon Jul 13 19:15:10 2009 (4A5BBFFE) 98e35000 98e84000 srv2 srv2.sys Mon Jul 13 19:14:52 2009 (4A5BBFEC) 98000000 98021000 srvnet srvnet.sys Mon Jul 13 19:14:45 2009 (4A5BBFE5) 91a4d000 91a4e380 swenum swenum.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 8bb4f000 8bb9e000 SYMEFA SYMEFA.SYS Tue Jun 23 17:50:40 2009 (4A414E30) 90e68000 90e8d000 SYMEVENT SYMEVENT.SYS Wed Jun 24 16:14:58 2009 (4A428942) 90e9b000 90eaf500 SYMFW SYMFW.SYS Mon Jul 06 20:21:46 2009 (4A52951A) 90f62000 90f6b000 SymIMv SymIMv.sys Mon Jun 22 19:04:43 2009 (4A400E0B) 90e8d000 90e9b000 SYMNDISV SYMNDISV.SYS Mon Jul 06 20:25:19 2009 (4A5295EF) 90e34000 90e67600 SYMTDI SYMTDI.SYS Mon Jul 06 20:21:23 2009 (4A529503) 8c021000 8c16a000 tcpip tcpip.sys Mon Jul 13 19:13:18 2009 (4A5BBF8E) 91bd8000 91be5000 tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926) 8b808000 8b813000 TDI TDI.SYS Mon Jul 13 19:12:12 2009 (4A5BBF4C) 8bbe5000 8bbfc000 tdx tdx.sys Mon Jul 13 19:12:10 2009 (4A5BBF4A) 90fa6000 90fb6000 termdd termdd.sys Mon Jul 13 20:01:35 2009 (4A5BCADF) 98470000 98479000 TSDDD TSDDD.dll unavailable (00000000) 91658000 91679000 tunnel tunnel.sys Mon Jul 13 19:54:03 2009 (4A5BC91B) 9fd99000 9fdd9000 udfs udfs.sys Mon Jul 13 19:14:09 2009 (4A5BBFC1) 91a83000 91a91000 umbus umbus.sys Mon Jul 13 19:51:38 2009 (4A5BC88A) 931b5000 931c8b00 usbaudio usbaudio.sys Mon Jul 13 19:51:23 2009 (4A5BC87B) 930e8000 930ff000 usbccgp usbccgp.sys Mon Jul 13 19:51:31 2009 (4A5BC883) 930ff000 93100700 USBD USBD.SYS Mon Jul 13 19:51:05 2009 (4A5BC869) 925ed000 925fc000 usbehci usbehci.sys Mon Jul 13 19:51:14 2009 (4A5BC872) 91a91000 91ad5000 usbhub usbhub.sys Mon Jul 13 19:52:06 2009 (4A5BC8A6) 925e3000 925ed000 usbohci usbohci.sys Mon Jul 13 19:51:14 2009 (4A5BC872) 917a7000 917f2000 USBPORT USBPORT.SYS Mon Jul 13 19:51:13 2009 (4A5BC871) 8ba33000 8ba3e000 vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 8bdea000 8bdf6000 vga vga.sys Mon Jul 13 19:25:50 2009 (4A5BC27E) 8bb9e000 8bbbf000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 8c19b000 8c1a3380 vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C) 8ba4f000 8ba5f000 volmgr volmgr.sys Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8ba5f000 8baaa000 volmgrx volmgrx.sys Mon Jul 13 19:11:41 2009 (4A5BBF2D) 8c1a4000 8c1e3000 volsnap volsnap.sys Mon Jul 13 19:11:34 2009 (4A5BBF26) 90f93000 90fa6000 wanarp wanarp.sys Mon Jul 13 19:55:02 2009 (4A5BC956) 8bbbf000 8bbcc000 watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 8b92f000 8b9a0000 Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 8b9a0000 8b9ae000 WDFLDR WDFLDR.SYS Mon Jul 13 19:11:25 2009 (4A5BBF1D) 90f3c000 90f43000 wfplwf wfplwf.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 98210000 9845a000 win32k win32k.sys unavailable (00000000) 9168a000 91693000 wmiacpi wmiacpi.sys Mon Jul 13 19:19:16 2009 (4A5BC0F4) 8b9f6000 8b9ff000 WMILIB WMILIB.SYS Mon Jul 13 19:11:22 2009 (4A5BBF1A) Unloaded modules: 98f95000 98fff000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 98f2b000 98f95000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 8bfd6000 8bfe3000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8bfe3000 8bfee000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8bfee000 8bff7000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8be00000 8be11000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
Have you updated the drivers that CarlTR6 suggested?
hmmm the netr73.sys seems to be related to my wireless adapter i have to pick up on the wireless internet router in my house
im confused to i update all the drivers on that list then?
ah wait a a second... the wireless adaptor my mum got apparently is for windows 2k XP or Vista...is this the cause of my problems?
althought it sounds like i have hardware issues as well
althought it sounds like i have hardware issues as well
In this case, I think the cause is -
1. Norton
2. Obsolete drivers
Dumps, unfortunately, do not always pinpoint a cause and we have to troubleshoot eliminating things until we find the cause. So uninstall Norton and update the remaining drivers - especially that 2007 driver.
Install Microsoft Security Essentials in place of Norton. MSE does not cause crashes. There are valid reasons for this recommendation.
Yes, netr73.sys is your wireless adapter driver. Go to the manufacture's website and search for the driver for your adapter model. You want to find one that is dated July 13 2009 or later.
But also, uninstall Norton.
But also, uninstall Norton.
oh i already uninstalled it XD and i also made sure i have no daemon tools either.
yeah this adapter is out dated they dont even have software updates for it, i will get a new one its no big deal, this is what happens when you mum gets the cheap option. so if i get another one that is up to date and compatible with windows 7 should this fix it?
also the MSE is there a link to one for windows 7? one i found is vista/ xp
also the MSE is there a link to one for windows 7? one i found is vista/ xp
Very good. Did you use the uninstall tool I mentioned? I saw the Norton drivers in the last dump you uploaded.
I want to explain hardware a little more clearly. Hardware consists of your motherboard, CPU, RAM, hard drives, adapter cards (such as network, wireless, audio, video adapters), mouse, keyboard, monitor, cared reader, etc. Other things can affect your hardware, particularly RAM such as obsolete drivers, corrupted drivers, obsolete software, third party antivirus programs, third party firewalls, and defective hardware peripherals (printer, mouse, keyboard disk drives, etc).
In your case, since you tested your RAM, we are looking for other things than can adversely affect your RAM. I hope this helps you to understand.
I want to explain hardware a little more clearly. Hardware consists of your motherboard, CPU, RAM, hard drives, adapter cards (such as network, wireless, audio, video adapters), mouse, keyboard, monitor, cared reader, etc. Other things can affect your hardware, particularly RAM such as obsolete drivers, corrupted drivers, obsolete software, third party antivirus programs, third party firewalls, and defective hardware peripherals (printer, mouse, keyboard disk drives, etc).
In your case, since you tested your RAM, we are looking for other things than can adversely affect your RAM. I hope this helps you to understand.
yeah this adapter is out dated they dont even have software updates for it, i will get a new one its no big deal, this is what happens when you mum gets the cheap option. so if i get another one that is up to date and compatible with windows 7 should this fix it?
also the MSE is there a link to one for windows 7? one i found is vista/ xp
also the MSE is there a link to one for windows 7? one i found is vista/ xp
Here is the link to MSE - http://www.microsoft.com/security_essentials/
thanks =]
i will get a new adaptor on monday and after i post this i will uninstall my adaptor and just work offline for a while. i will get a new one and see if it helps.
just to clarify you think the is most likely the cause then? once i get new one should be sorted?
honestly i have been so stressed over this and i can't believe it might be something as silly as buying an out dates wireless adaptor lol
i will get a new adaptor on monday and after i post this i will uninstall my adaptor and just work offline for a while. i will get a new one and see if it helps.
just to clarify you think the is most likely the cause then? once i get new one should be sorted?
honestly i have been so stressed over this and i can't believe it might be something as silly as buying an out dates wireless adaptor lol
oh i meant i unistalled norton with the tool you provided =]
I think Norton played a bigger role than the wireless adapter did. You will notice that last error code mentioned antivirus programs as a possible cause. Try running with the adapter now that you have uninstalled Norton and see what happens. I believe it will bite you sooner or later, though.
How did you do with updating the other drivers?
How did you do with updating the other drivers?
well it was crashing before i had norton
i havent done them yet do i do all of them listed cause you said some where norton ones
i havent done them yet do i do all of them listed cause you said some where norton ones
ok GEARAspiWDM.sys is itunes
not sure what NAVENG.SYS belongs too, possibly symantec so norton
NAVEX15.SYS is norton
SRTSP.SYS norton
ccHPx86.sys i don't know
SRTSPX.SYS- norton
SYMEFA.SYS norton
SYMEVENT.SY norton
SYMFW.SYS norton
SymIMv.sys norton
SYMNDISV.SYS norton
SYMTDI.SYS norton
ok so since mostr of them are norton they are gone, need to sort out the itunes one and then there is that unknown one
since my bluescreens happened before and after norton i will say that this wireless thing was a main cause especially since majority of crashes happened while on the net, is that a fair assumption?
not sure what NAVENG.SYS belongs too, possibly symantec so norton
NAVEX15.SYS is norton
SRTSP.SYS norton
ccHPx86.sys i don't know
SRTSPX.SYS- norton
SYMEFA.SYS norton
SYMEVENT.SY norton
SYMFW.SYS norton
SymIMv.sys norton
SYMNDISV.SYS norton
SYMTDI.SYS norton
ok so since mostr of them are norton they are gone, need to sort out the itunes one and then there is that unknown one
since my bluescreens happened before and after norton i will say that this wireless thing was a main cause especially since majority of crashes happened while on the net, is that a fair assumption?
If you uninstalled Norton, those should be gone and you are going to take care of the 2007 driver on Monday. The remaining one is a 2009 driver and it may work OK.
GEARAspiWDM.sys Mon May 18 08:16:53 2009 - CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x by GEAR Software Inc (www.gearsoftware.com). It is possible this driver was part of Norton, too. It may be gone.
netr73.sys Sun Sep 23 23:09:09 2007 -
It is always better to have up to date drivers, though
GEARAspiWDM.sys Mon May 18 08:16:53 2009 - CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x by GEAR Software Inc (www.gearsoftware.com). It is possible this driver was part of Norton, too. It may be gone.
netr73.sys Sun Sep 23 23:09:09 2007 -
It is always better to have up to date drivers, though
just had another crash this is the minidump
Attachment 88551
Attachment 88551
Quote:
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\Downloads\073110-30264-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82e40000 PsLoadedModuleList = 0x82f88810 Debug session time: Sat Jul 31 15:24:22.893 2010 (GMT-4) System Uptime: 0 days 1:43:05.095 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ..... 2: kd> !analyze ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, a27a99b0, a27a9590, 8bc33521} Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+15 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 001904fb Arg2: a27a99b0 Arg3: a27a9590 Arg4: 8bc33521 Debugging Details: ------------------ EXCEPTION_RECORD: a27a99b0 -- (.exr 0xffffffffa27a99b0) ExceptionAddress: 8bc33521 (Ntfs!NtfsAcquireResourceExclusive+0x00000015) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00006485 Attempt to read from address 00006485 CONTEXT: a27a9590 -- (.cxr 0xffffffffa27a9590) eax=00006449 ebx=c00000d8 ecx=00000702 edx=0000d7ea esi=ba251c88 edi=00000002 eip=8bc33521 esp=a27a9a78 ebp=a27a9a78 iopl=0 nv up ei pl nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213 Ntfs!NtfsAcquireResourceExclusive+0x15: 8bc33521 8b403c mov eax,dword ptr [eax+3Ch] ds:0023:00006485=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: rundll32.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00006485 READ_ADDRESS: GetPointerFromAddress: unable to read from 82fa8718 Unable to read MiSystemVaType memory at 82f88160 00006485 FOLLOWUP_IP: Ntfs!NtfsAcquireResourceExclusive+15 8bc33521 8b403c mov eax,dword ptr [eax+3Ch] FAULTING_IP: Ntfs!NtfsAcquireResourceExclusive+15 8bc33521 8b403c mov eax,dword ptr [eax+3Ch] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from 8bc3357c to 8bc33521 STACK_TEXT: a27a9a78 8bc3357c 85b43ee0 ba251c88 b0c42c00 Ntfs!NtfsAcquireResourceExclusive+0x15 a27a9a9c 8bc39e88 85b43ee0 ba251c88 00000000 Ntfs!NtfsAcquireExclusiveFcb+0x42 a27a9ac8 8bca6433 85b43e00 ba251c88 00000000 Ntfs!NtfsAcquireFcbWithPaging+0x8d a27a9bf4 8bcba381 85b43ee0 856cc438 b0c42d08 Ntfs!NtfsOpenFile+0x303 a27a9cdc 8bc40210 85b43ee0 856cc438 a329f95c Ntfs!NtfsCommonCreate+0xd84 a27a9d1c 82eb010e a329f8f4 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20 a27a9d1c 82eb0205 a329f8f4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a a329f858 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsAcquireResourceExclusive+15 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf45 STACK_COMMAND: .cxr 0xffffffffa27a9590 ; kb FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsAcquireResourceExclusive+15 BUCKET_ID: 0x24_Ntfs!NtfsAcquireResourceExclusive+15 Followup: MachineOwner --------- 2: kd> lmtsmn start end module name 8b9a4000 8b9ec000 ACPI ACPI.sys Mon Jul 13 19:11:11 2009 (4A5BBF0F) 90c10000 90c6a000 afd afd.sys Mon Jul 13 19:12:34 2009 (4A5BBF62) 915ce000 915e0000 AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954) 91430000 91441000 amdppm amdppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07) 8bafa000 8bb03000 amdxata amdxata.sys Tue May 19 13:57:35 2009 (4A12F30F) 8bace000 8bad7000 atapi atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 8bad7000 8bafa000 ataport ataport.SYS Mon Jul 13 19:11:18 2009 (4A5BBF16) 91600000 91b7c000 atikmdag atikmdag.sys Tue Apr 06 21:37:59 2010 (4BBBE1F7) 9144a000 91476000 atikmpag atikmpag.sys Tue Apr 06 21:23:11 2010 (4BBBDE7F) 8c17d000 8c184000 Beep Beep.SYS Mon Jul 13 19:45:00 2009 (4A5BC6FC) 90dea000 90df8000 blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 8b830000 8b838000 BOOTVID BOOTVID.dll Mon Jul 13 21:04:34 2009 (4A5BD9A2) 948f5000 9490e000 bowser bowser.sys Mon Jul 13 19:14:21 2009 (4A5BBFCD) 96da0000 96dbe000 cdd cdd.dll unavailable (00000000) 8c157000 8c176000 cdrom cdrom.sys Mon Jul 13 19:11:24 2009 (4A5BBF1C) 8b87a000 8b925000 CI CI.dll Mon Jul 13 21:09:28 2009 (4A5BDAC8) 8c100000 8c125000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 8b838000 8b87a000 CLFS CLFS.SYS Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8bd94000 8bdf1000 cng cng.sys Mon Jul 13 19:32:55 2009 (4A5BC427) 915c1000 915ce000 CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716) 92600000 9260d000 crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 90d6e000 90dd2000 csc csc.sys Mon Jul 13 19:15:08 2009 (4A5BBFFC) 90dd2000 90dea000 dfsc dfsc.sys Mon Jul 13 19:14:16 2009 (4A5BBFC8) 90d62000 90d6e000 discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 8c0ef000 8c100000 disk disk.sys Mon Jul 13 19:11:28 2009 (4A5BBF20) 90f91000 90faa000 drmk drmk.sys Mon Jul 13 20:36:05 2009 (4A5BD2F5) 92618000 92621000 dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 9260d000 92618000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 90faa000 90fbb000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 929a5000 929af000 Dxapi Dxapi.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 91476000 9152d000 dxgkrnl dxgkrnl.sys Thu Oct 01 20:48:33 2009 (4AC54DE1) 91b7c000 91bb5000 dxgmms1 dxgmms1.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 8bb37000 8bb48000 fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 8bb03000 8bb37000 fltmgr fltmgr.sys Mon Jul 13 19:11:13 2009 (4A5BBF11) 8bc00000 8bc09000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:11:14 2009 (4A5BBF12) 8c0bd000 8c0ef000 fvevol fvevol.sys Mon Jul 13 19:13:01 2009 (4A5BBF7D) 8be00000 8be31000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 9ff7e000 9ff806c0 gdrv gdrv.sys Thu Mar 12 23:17:32 2009 (49B9D04C) 91bd4000 91bd9280 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5) 82e09000 82e40000 hal halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 91bb5000 91bd4000 HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F) 928e8000 928fb000 HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865) 928fb000 92901480 HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863) 928dd000 928e8000 hidusb hidusb.sys Mon Jul 13 19:51:04 2009 (4A5BC868) 94870000 948f5000 HTTP HTTP.sys Mon Jul 13 19:12:53 2009 (4A5BBF75) 8c0b5000 8c0bd000 hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 90e89000 90e96000 kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 92999000 929a5000 kbdhid kbdhid.sys Mon Jul 13 19:45:09 2009 (4A5BC705) 80baf000 80bb7000 kdcom kdcom.dll Mon Jul 13 21:08:58 2009 (4A5BDAAA) 90ea5000 90ed9000 ks ks.sys Mon Jul 13 19:45:13 2009 (4A5BC709) 8bd81000 8bd94000 ksecdd ksecdd.sys Mon Jul 13 19:11:56 2009 (4A5BBF3C) 8be72000 8be97000 ksecpkg ksecpkg.sys Mon Jul 13 19:34:00 2009 (4A5BC468) 90fd6000 90fe6000 lltdio lltdio.sys Mon Jul 13 19:53:18 2009 (4A5BC8EE) 90fbb000 90fd6000 luafv luafv.sys Mon Jul 13 19:15:44 2009 (4A5BC020) 8b814000 8b81f000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89) 929af000 929ba000 monitor monitor.sys Mon Jul 13 19:25:58 2009 (4A5BC286) 90e96000 90ea3000 mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 92902000 9290d000 mouhid mouhid.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 8bab8000 8bace000 mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) 9490e000 94920000 mpsdrv mpsdrv.sys Mon Jul 13 19:52:52 2009 (4A5BC8D4) 94920000 94943000 mrxsmb mrxsmb.sys Mon Jul 13 19:14:24 2009 (4A5BBFD0) 94943000 9497e000 mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA) 9497e000 94999000 mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5) 8c1d6000 8c1e1000 Msfs Msfs.SYS Mon Jul 13 19:11:26 2009 (4A5BBF1E) 8b9f5000 8b9fd000 msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 8bd56000 8bd81000 msrpc msrpc.sys Mon Jul 13 19:11:59 2009 (4A5BBF3F) 90d58000 90d62000 mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 8c0a5000 8c0b5000 mup mup.sys Mon Jul 13 19:14:14 2009 (4A5BBFC6) 8bb48000 8bbff000 ndis ndis.sys Mon Jul 13 19:12:24 2009 (4A5BBF58) 91400000 9140b000 ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930) 9484d000 9485d000 ndisuio ndisuio.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 90e17000 90e39000 ndiswan ndiswan.sys Mon Jul 13 19:54:34 2009 (4A5BC93A) 90f2b000 90f3c000 NDProxy NDProxy.SYS Mon Jul 13 19:54:27 2009 (4A5BC933) 90cc2000 90cd0000 netbios netbios.sys Mon Jul 13 19:53:54 2009 (4A5BC912) 90c6a000 90c9c000 netbt netbt.sys Mon Jul 13 19:12:18 2009 (4A5BBF52) 8be34000 8be72000 NETIO NETIO.SYS Mon Jul 13 19:12:35 2009 (4A5BBF63) 9290d000 92985000 netr73 netr73.sys Sun Sep 23 23:09:09 2007 (46F72A55) 8c1e1000 8c1ef000 Npfs Npfs.SYS Mon Jul 13 19:11:31 2009 (4A5BBF23) 90d4e000 90d58000 nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 82e40000 83250000 nt ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007) 8bc27000 8bd56000 Ntfs Ntfs.sys Mon Jul 13 19:12:05 2009 (4A5BBF45) 8c176000 8c17d000 Null Null.SYS Mon Jul 13 19:11:12 2009 (4A5BBF10) 94807000 9484d000 nwifi nwifi.sys Mon Jul 13 19:51:59 2009 (4A5BC89F) 90ca3000 90cc2000 pacer pacer.sys Mon Jul 13 19:53:58 2009 (4A5BC916) 915a9000 915c1000 parport parport.sys Mon Jul 13 19:45:34 2009 (4A5BC71E) 8ba37000 8ba48000 partmgr partmgr.sys Mon Jul 13 19:11:35 2009 (4A5BBF27) 94999000 949a0000 parvdm parvdm.sys Mon Jul 13 19:45:29 2009 (4A5BC719) 8ba02000 8ba2c000 pci pci.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 8baa3000 8baaa000 pciide pciide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17) 8baaa000 8bab8000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:11:15 2009 (4A5BBF13) 8bdf1000 8bdff000 pcw pcw.sys Mon Jul 13 19:11:10 2009 (4A5BBF0E) 9fe0f000 9fea6000 peauth peauth.sys Mon Jul 13 20:35:44 2009 (4A5BD2E0) 90f62000 90f91000 portcls portcls.sys Mon Jul 13 19:51:00 2009 (4A5BC864) 8b81f000 8b830000 PSHED PSHED.dll Mon Jul 13 21:09:36 2009 (4A5BDAD0) 915e0000 915f8000 rasl2tp rasl2tp.sys Mon Jul 13 19:54:33 2009 (4A5BC939) 90e39000 90e51000 raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D) 90e51000 90e68000 raspptp raspptp.sys Mon Jul 13 19:54:47 2009 (4A5BC947) 90e68000 90e7f000 rassstp rassstp.sys Mon Jul 13 19:54:57 2009 (4A5BC951) 90d0d000 90d4e000 rdbss rdbss.sys Mon Jul 13 19:14:26 2009 (4A5BBFD2) 90e7f000 90e89000 rdpbus rdpbus.sys Mon Jul 13 20:02:40 2009 (4A5BCB20) 8c1be000 8c1c6000 RDPCDD RDPCDD.sys Mon Jul 13 20:01:40 2009 (4A5BCAE4) 8c1c6000 8c1ce000 rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 8c1ce000 8c1d6000 rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 8c078000 8c0a5000 rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) 9485d000 94870000 rspndr rspndr.sys Mon Jul 13 19:53:20 2009 (4A5BC8F0) 9152d000 9155e000 Rt86win7 Rt86win7.sys Thu Jul 30 07:58:26 2009 (4A718AE2) 90f3c000 90f62000 RtHDMIV RtHDMIV.sys Thu Jul 16 23:52:43 2009 (4A5FF58B) 92625000 928c3540 RTKVHDA RTKVHDA.sys Tue Aug 18 05:30:35 2009 (4A8A74BB) 9fea6000 9feb0000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528) 91bf3000 91bfd000 serenum serenum.sys Mon Jul 13 19:45:27 2009 (4A5BC717) 90cd0000 90cea000 serial serial.sys Mon Jul 13 19:45:33 2009 (4A5BC71D) 8c070000 8c078000 spldr spldr.sys Mon May 11 12:13:47 2009 (4A084EBB) 9ff2d000 9ff7e000 srv srv.sys Mon Jul 13 19:15:10 2009 (4A5BBFFE) 9fede000 9ff2d000 srv2 srv2.sys Mon Jul 13 19:14:52 2009 (4A5BBFEC) 9feb0000 9fed1000 srvnet srvnet.sys Mon Jul 13 19:14:45 2009 (4A5BBFE5) 90ea3000 90ea4380 swenum swenum.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 8be97000 8bfe0000 tcpip tcpip.sys Mon Jul 13 19:13:18 2009 (4A5BBF8E) 9fed1000 9fede000 tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926) 8c017000 8c022000 TDI TDI.SYS Mon Jul 13 19:12:12 2009 (4A5BBF4C) 8c000000 8c017000 tdx tdx.sys Mon Jul 13 19:12:10 2009 (4A5BBF4A) 90cfd000 90d0d000 termdd termdd.sys Mon Jul 13 20:01:35 2009 (4A5BCADF) 96d70000 96d79000 TSDDD TSDDD.dll Mon Jul 13 20:01:40 2009 (4A5BCAE4) 9140f000 91430000 tunnel tunnel.sys Mon Jul 13 19:54:03 2009 (4A5BC91B) 929ba000 929fa000 udfs udfs.sys Mon Jul 13 19:14:09 2009 (4A5BBFC1) 90ed9000 90ee7000 umbus umbus.sys Mon Jul 13 19:51:38 2009 (4A5BC88A) 92985000 92998b00 usbaudio usbaudio.sys Mon Jul 13 19:51:23 2009 (4A5BC87B) 928c4000 928db000 usbccgp usbccgp.sys Mon Jul 13 19:51:31 2009 (4A5BC883) 928db000 928dc700 USBD USBD.SYS Mon Jul 13 19:51:05 2009 (4A5BC869) 91be4000 91bf3000 usbehci usbehci.sys Mon Jul 13 19:51:14 2009 (4A5BC872) 90ee7000 90f2b000 usbhub usbhub.sys Mon Jul 13 19:52:06 2009 (4A5BC8A6) 91bda000 91be4000 usbohci usbohci.sys Mon Jul 13 19:51:14 2009 (4A5BC872) 9155e000 915a9000 USBPORT USBPORT.SYS Mon Jul 13 19:51:13 2009 (4A5BC871) 8ba2c000 8ba37000 vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 8c184000 8c190000 vga vga.sys Mon Jul 13 19:25:50 2009 (4A5BC27E) 8c190000 8c1b1000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 8bfe0000 8bfe8380 vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C) 8ba48000 8ba58000 volmgr volmgr.sys Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8ba58000 8baa3000 volmgrx volmgrx.sys Mon Jul 13 19:11:41 2009 (4A5BBF2D) 8c031000 8c070000 volsnap volsnap.sys Mon Jul 13 19:11:34 2009 (4A5BBF26) 90cea000 90cfd000 wanarp wanarp.sys Mon Jul 13 19:55:02 2009 (4A5BC956) 8c1b1000 8c1be000 watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 8b925000 8b996000 Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 8b996000 8b9a4000 WDFLDR WDFLDR.SYS Mon Jul 13 19:11:25 2009 (4A5BBF1D) 90c9c000 90ca3000 wfplwf wfplwf.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 96b10000 96d5a000 win32k win32k.sys Sat May 01 10:49:02 2010 (4BDC3F5E) 91441000 9144a000 wmiacpi wmiacpi.sys Mon Jul 13 19:19:16 2009 (4A5BC0F4) 8b9ec000 8b9f5000 WMILIB WMILIB.SYS Mon Jul 13 19:11:22 2009 (4A5BBF1A) Unloaded modules: 9ff81000 9ffeb000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 8c125000 8c132000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 8c132000 8c13d000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 8c13d000 8c146000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 8c146000 8c157000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
In the meantime, lets run a disk check to eliminate that as a possible cause. Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP). [quote]
Copy/paste the results into your next post.
Next run a disk test from your HD manufacturer: HD Diagnostic
We want to confirm of eliminate the hard drive as a possible cause.
CHKDSK is verifying files (stage 1 of 3)...
126976 file records processed. File verification completed.
134 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The index entry length is incorrect for index entry type 0x5.
00 00 00 00 00 00 00 00 10 08 00 00 02 00 00 00 ................
a5 3f 01 00 00 00 01 00 af 9e a9 9a 57 30 cb 01 �?......����W0..
The first free byte, 0x700, in index header of index $I30
in file 0x13fa5 is not equal to 0x5e8.
Error detected in index $I30 for file 81829.
The VCN 0x4c0 of index $I30 in file 0x13fa5 is inconsistence with
the VCN 0xcc0 stored inside the index buffer.
Error detected in index $I30 for file 81829.
The index bitmap $I30 in file 0x13fa5 is incorrect.
Error detected in index $I30 for file 81829.
Unable to locate the file name attribute of index entry x86_microsoft-windows-d..ingapplet.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5fa136fe0c1b6b89.man?fest
of index $I30 with parent 0x13fa5 in file 0x1b33b.
Index entry x86_microsoft-windows-d..ingapplet.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5fa136fe0c1b6b89.man?fest in index $I30 of file 81829 is incorrect.
Unable to locate the file name attribute of index entry x86_microsoft-windows-ie-imagesupport_31bf3856ad364e35_8.0.7600.16385_none_5885662ecb64099b.man?fest
of index $I30 with parent 0x13fa5 in file 0x1b9db.
Index entry x86_microsoft-windows-ie-imagesupport_31bf3856ad364e35_8.0.7600.16385_none_5885662ecb64099b.man?fest in index $I30 of file 81829 is incorrect.
173118 index entries processed. Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
ok getting to hd stuff now
126976 file records processed. File verification completed.
134 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The index entry length is incorrect for index entry type 0x5.
00 00 00 00 00 00 00 00 10 08 00 00 02 00 00 00 ................
a5 3f 01 00 00 00 01 00 af 9e a9 9a 57 30 cb 01 �?......����W0..
The first free byte, 0x700, in index header of index $I30
in file 0x13fa5 is not equal to 0x5e8.
Error detected in index $I30 for file 81829.
The VCN 0x4c0 of index $I30 in file 0x13fa5 is inconsistence with
the VCN 0xcc0 stored inside the index buffer.
Error detected in index $I30 for file 81829.
The index bitmap $I30 in file 0x13fa5 is incorrect.
Error detected in index $I30 for file 81829.
Unable to locate the file name attribute of index entry x86_microsoft-windows-d..ingapplet.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5fa136fe0c1b6b89.man?fest
of index $I30 with parent 0x13fa5 in file 0x1b33b.
Index entry x86_microsoft-windows-d..ingapplet.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5fa136fe0c1b6b89.man?fest in index $I30 of file 81829 is incorrect.
Unable to locate the file name attribute of index entry x86_microsoft-windows-ie-imagesupport_31bf3856ad364e35_8.0.7600.16385_none_5885662ecb64099b.man?fest
of index $I30 with parent 0x13fa5 in file 0x1b9db.
Index entry x86_microsoft-windows-ie-imagesupport_31bf3856ad364e35_8.0.7600.16385_none_5885662ecb64099b.man?fest in index $I30 of file 81829 is incorrect.
173118 index entries processed. Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
ok getting to hd stuff now
ran a seagate hard drive test as its what i have and it passed. was only the short test though, should i do a longer one?
Sure; it won't cost anything and you will know for sure that it is not your hard drive.
Note that the HDD might be OK, and the filesystem itself is corrupt (for some unknown reason). If the HDD checks out, you might have to consider backing up your data and reinstalling on a reformatted partition.
Không có nhận xét nào:
Đăng nhận xét