BSOD Crashing

[RicoXR4]

Hi all,

Have just recently (today) upgraded to Win7 from XP. As a result I have had to do a clean install on my system, formatting the windows partition before doing so.

Throughout the day I have been installing standard software and copying my backup files. I have experienced several crashes and restarts while doing so (even when the computer was at idle).

As per the thread instructions I have attached the error reporting and system check.

OS: Windows 7 x32 Professional, bought yesterday from Microsoft (online, student discount)

System is essentially a few months old (all components upgraded, including motherboard that is apparently Win7 ready).

Your help is greatly appreciated!

 

[yowanvista]

ASACPI.sys the 2004 version is a huge cause of BSODs

   Information

The old versions of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Your X10 USB Wireless Transceiver driver is out of date
Update it, http://www.x10.com/support/support_soft1.htm
This device is obsolete and the manufacturer hasn't updated the software for Windows 7

x10ufx2.sys        0x963b2000    0x963bc000    0x0000a000    0x456f66e0    01/12/2006 03:18:56

Intel Display driver is out of date
http://www.intel.com/support/detect.htm

igdkmd32.sys        0x8dc25000    0x8e122000    0x004fd000    0x4a01d354    06/05/2009 22:13:40

 

[RicoXR4]

Thanks Yowan, I have updated these drivers and hoping for the best.

Now to try and figure out Win7...

 

[RicoXR4]

Updated and installed the above drivers and restarted, however shortly after another BSOD. Have attached updated log files.

Thankyou in advance

 

[yowanvista]

I suspect faulty RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[RicoXR4]

Memtest completed, no errors found.

Any other suspicions?

 

[RicoXR4]

More crashing occured today at different stages through the boot, attached.

Thanks

 

[yowanvista]

Please update that X10 Wireless Transceiver driver, the driver is incompatible with Windows 7

Run http://www.sevenforums.com/tutorials/433-disk-check.html

*******************************************************************************
*                                                                             *
*                        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: 8079972c
Arg3: 80799310
Arg4: 8883cb80

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


EXCEPTION_RECORD:  8079972c -- (.exr 0xffffffff8079972c)
ExceptionAddress: 8883cb80 (Ntfs!NtfsAcquireExclusiveScb+0x0000000c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000050
Attempt to read from address 00000050

CONTEXT:  80799310 -- (.cxr 0xffffffff80799310)
eax=857815a0 ebx=85781568 ecx=00000727 edx=00000000 esi=00000000 edi=857815a0
eip=8883cb80 esp=807997f4 ebp=80799800 iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
Ntfs!NtfsAcquireExclusiveScb+0xc:
8883cb80 ff7650          push    dword ptr [esi+50h]  ds:0023:00000050=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.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:  00000050

READ_ADDRESS: GetPointerFromAddress: unable to read from 82b79848
Unable to read MiSystemVaType memory at 82b58e20
 00000050 

FOLLOWUP_IP: 
Ntfs!NtfsAcquireExclusiveScb+c
8883cb80 ff7650          push    dword ptr [esi+50h]

FAULTING_IP: 
Ntfs!NtfsAcquireExclusiveScb+c
8883cb80 ff7650          push    dword ptr [esi+50h]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 888d1d4a to 8883cb80

STACK_TEXT:  
80799800 888d1d4a 85781568 00000000 85781568 Ntfs!NtfsAcquireExclusiveScb+0xc
8079981c 88838587 85781568 85781614 85781568 Ntfs!NtfsDeallocateRecordsComplete+0x20
80799834 8883ab98 85781568 00000001 00000000 Ntfs!NtfsCleanupIrpContext+0x18
80799854 88836074 85781568 8697fba0 00000000 Ntfs!NtfsExtendedCompleteRequestInternal+0x79
80799964 8883987a 85781568 8697fba0 08ffa343 Ntfs!NtfsCommonWrite+0x24ca
807999dc 82a47593 8569e020 8697fba0 8697fba0 Ntfs!NtfsFsdWrite+0x2e1
807999f4 885ab20c 856ba1f0 8697fba0 00000000 nt!IofCallDriver+0x63
80799a18 885ab3cb 80799a38 856ba1f0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
80799a50 82a47593 856ba1f0 8697fba0 8697fba0 fltmgr!FltpDispatch+0xc5
80799a68 82c3a98f 858a0028 8697fba0 8697fd78 nt!IofCallDriver+0x63
80799a88 82c80621 856ba1f0 858a0028 00000001 nt!IopSynchronousServiceTail+0x1f8
80799b24 82a4e1ea 856ba1f0 800005f4 00000000 nt!NtWriteFile+0x6e8
80799b24 82a4d655 856ba1f0 800005f4 00000000 nt!KiFastCallEntry+0x12a
80799bc0 82c1d480 80000190 800005f4 00000000 nt!ZwWriteFile+0x11
80799c3c 82c1f94d 80000190 80799c80 00000001 nt!CmpDoFileWrite+0x15c
80799c58 82c1d7d3 8961b008 00000004 80799c80 nt!CmpFileWrite+0x33
80799ca0 82c1d83a 01431378 c000014d 00000000 nt!HvpWriteDirtyDataToLog+0x229
80799cb8 82bf7e2b 930afda8 8a476a28 00000000 nt!HvOptimizedSyncHive+0x1c
80799cd8 82befb47 8a476a08 00000000 0000034c nt!CmFlushKey+0x22e
80799d28 82a4e1ea 0000034c 008cf14c 776570b4 nt!NtFlushKey+0x17a
80799d28 776570b4 0000034c 008cf14c 776570b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
008cf14c 00000000 00000000 00000000 00000000 0x776570b4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsAcquireExclusiveScb+c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7892c

STACK_COMMAND:  .cxr 0xffffffff80799310 ; kb

FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsAcquireExclusiveScb+c

BUCKET_ID:  0x24_Ntfs!NtfsAcquireExclusiveScb+c

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

 

[RicoXR4]

Disk checks completed on both partitions, no errors reported.

Have rerun the tests, have now got an error reported as part of the perfmon /report, see attached.

 

[RicoXR4]

Removed the front panel that incorporated card reader, usb, jacks etc and haven't had a crash since *touch wood*. This (and the case) was the only thing carried over from my old system, suspect this was the issue.

If I don't get another crash over the weekend will mark as solved. Thanks very much for the help yowan!

 

[MvdB]

Removed the front panel that incorporated card reader, usb, jacks etc and haven't had a crash since *touch wood*. This (and the case) was the only thing carried over from my old system, suspect this was the issue.

If I don't get another crash over the weekend will mark as solved. Thanks very much for the help yowan!

Are you saying it was a temp issue or have you de-installed old drivers for things like the cardreader?

 

[RicoXR4]

No dice...continuing to crash over the weekend. Seems to happen ramdomly (not during boot).

Please find attached updated log files.

Any help is much appreciated!