BSOD and freeze up problems

[faz0222]

Based on the fact that I had the same USB disconnections and BSODs while using XP on a different HDD with the same comp., don't you guys think this could be a hardware problem ? possibly the Motherboard ?
It just seem that whatever driver I fix it won't change a thing

 

[CarlTR6]

Do you have another mouse you can try?

 

[faz0222]

I was using a Logitech mouse when I started this thread, I'm now using a Saitek mouse. Same problems.
I think I have another mouse somewhere but it's still a logitech

 

[CarlTR6]

When you changed mice, did you completely uninstall the old mouse?

 

[faz0222]

I've just found a "Polar" mouse, a cheap wireless mouse that I use for my laptop.
I'll use that to test if it also disconnect ... not much hope

 

[faz0222]

When you changed mice, did you completely uninstall the old mouse?

yes, including clean restart before installing the new drivers

 

[CarlTR6]

Let us know the result of that mouse.

 

[faz0222]

well at least that was quick
direct blue screen, no delay or anything this time
Can you see anything interesting in that file ?

 

[CarlTR6]

This one is a different error code. Note the usual causes.

Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Just be check all possibilities, I suggest you run Check Disk.

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

Copy/paste the results into your next post.

To answer your question, yes, it could be a motherboard problem. You have tested three different mice and each has responded the same way. There nothing in the latest dump to pinpoint any specific problem. Still, I suggest you run Check Disk just to be sure.

Then I suggest you test your RAM with Memtest since memory corruption is involved in these crashes. Follow the instructions in the tutorial below. Post back with your results. Errors, if any, will show on your screen in red. It will take about 6-8 hours to run 7 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83605000 PsLoadedModuleList = 0x8374d810
Debug session time: Sun Oct 31 11:44:59.587 2010 (GMT-4)
System Uptime: 0 days 0:09:27.961
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, a8fab8fc, a8fab4e0, 8c3b382f}

Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+107 )

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: a8fab8fc
Arg3: a8fab4e0
Arg4: 8c3b382f

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


EXCEPTION_RECORD:  a8fab8fc -- (.exr 0xffffffffa8fab8fc)
ExceptionAddress: 8c3b382f (fltmgr!TreeUnlinkNoBalance+0x00000009)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 2000000c
Attempt to read from address 2000000c

CONTEXT:  a8fab4e0 -- (.cxr 0xffffffffa8fab4e0)
eax=ffffffff ebx=00000000 ecx=88ce9a60 edx=00000000 esi=20000000 edi=87041154
eip=8c3b382f esp=a8fab9c4 ebp=a8fab9c8 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
fltmgr!TreeUnlinkNoBalance+0x9:
8c3b382f ff760c          push    dword ptr [esi+0Ch]  ds:0023:2000000c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.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:  2000000c

READ_ADDRESS: GetPointerFromAddress: unable to read from 8376d718
Unable to read MiSystemVaType memory at 8374d160
 2000000c 

FOLLOWUP_IP: 
Ntfs!NtfsExtendedCompleteRequestInternal+107
8c44aa7b 5f              pop     edi

FAULTING_IP: 
fltmgr!TreeUnlinkNoBalance+9
8c3b382f ff760c          push    dword ptr [esi+0Ch]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from 8c3b3af4 to 8c3b382f

STACK_TEXT:  
a8fab9c8 8c3b3af4 20000000 87041134 86d033dc fltmgr!TreeUnlinkNoBalance+0x9
a8fab9e0 8c3c7208 87041154 ffffffff ffffffff fltmgr!TreeUnlinkMulti+0x22
a8faba00 8c3c7962 87041100 00004000 ffffffff fltmgr!DeleteNameCacheNodes+0x84
a8faba28 8c3c79f5 86d03008 87041100 00000000 fltmgr!PurgeStreamNameCache+0x96
a8faba50 8c3c7bb5 86d03008 00000000 88ce0990 fltmgr!FltpPurgeVolumeNameCache+0x77
a8faba6c 8c3c81c9 85eb2d98 88dc3b60 00000000 fltmgr!FltpReinstateNameCaching+0x65
a8faba8c 8c3aeb40 86d03008 88dc3b60 00000000 fltmgr!FltpReinstateNameCachingAllFrames+0x45
a8fabaac 8366db33 86cfb300 8843f820 88ce0990 fltmgr!FltpPassThroughCompletion+0x92
a8fabaf4 8c44aa7b 0000000a b194c0f8 88cb10b8 nt!IopfCompleteRequest+0x128
a8fabb0c 8c4ebfbc 88cb10b8 8843f820 00000000 Ntfs!NtfsExtendedCompleteRequestInternal+0x107
a8fabb84 8c45832b 88cb10b8 8843f820 24bd70d3 Ntfs!NtfsCommonSetInformation+0x84d
a8fabbf0 836414bc 86d04020 8843f820 8843f820 Ntfs!NtfsFsdSetInformation+0x107
a8fabc08 8c3af20c 86cfb300 8843f820 00000000 nt!IofCallDriver+0x63
a8fabc2c 8c3af3cb a8fabc4c 86cfb300 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
a8fabc64 836414bc 86cfb300 8843f820 00000000 fltmgr!FltpDispatch+0xc5
a8fabc7c 8385597f 8f6544c7 000002a8 02bdf580 nt!IofCallDriver+0x63
a8fabd18 8364844a 000002a8 02bdf5f8 048743d0 nt!NtSetInformationFile+0xa3f
a8fabd18 775064f4 000002a8 02bdf5f8 048743d0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02bdf638 00000000 00000000 00000000 00000000 0x775064f4


SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  Ntfs!NtfsExtendedCompleteRequestInternal+107

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

STACK_COMMAND:  .cxr 0xffffffffa8fab4e0 ; kb

FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsExtendedCompleteRequestInternal+107

BUCKET_ID:  0x24_Ntfs!NtfsExtendedCompleteRequestInternal+107

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

 

[faz0222]

No error with Memtest.

Here is the CHKDSK log

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          11/1/2010 10:41:09 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Anthony-PC
Description:


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)...
  307968 file records processed.                                         

File verification completed.
  413 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  60 reparse records processed.                                      

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

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

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

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

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

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

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

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

 153496575 KB total disk space.
  81798036 KB in 183797 files.
     96380 KB in 32462 indexes.
         0 KB in bad sectors.
    415999 KB in use by the system.
     65536 KB occupied by the log file.
  71186160 KB available on disk.

      4096 bytes in each allocation unit.
  38374143 total allocation units on disk.
  17796540 allocation units available on disk.

Internal Info:
00 b3 04 00 cb 4c 03 00 d3 f9 05 00 00 00 00 00  .....L..........
33 02 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  3...<...........
70 62 26 00 50 01 24 00 20 1e 24 00 00 00 24 00  pb&.P.$. .$...$.

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/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="2010-11-01T14:41:09.000000000Z" />
    <EventRecordID>19102</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Anthony-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)...
  307968 file records processed.                                         

File verification completed.
  413 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  60 reparse records processed.                                      

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

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

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

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

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

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

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

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

 153496575 KB total disk space.
  81798036 KB in 183797 files.
     96380 KB in 32462 indexes.
         0 KB in bad sectors.
    415999 KB in use by the system.
     65536 KB occupied by the log file.
  71186160 KB available on disk.

      4096 bytes in each allocation unit.
  38374143 total allocation units on disk.
  17796540 allocation units available on disk.

Internal Info:
00 b3 04 00 cb 4c 03 00 d3 f9 05 00 00 00 00 00  .....L..........
33 02 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  3...<...........
70 62 26 00 50 01 24 00 20 1e 24 00 00 00 24 00  pb&.P.$. .$...$.

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

What should I test next ?
Is there any way to test the motherboard itself ? :huh:

 

[CarlTR6]

Your RAM is probably good and your hard disk checks out fine. There is no way that you can test your motherboard; that requires bench testing in a shop. However you can test your CPU and your RAM with Prime95. Follow the instructions in this tutorial: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.