 | |
| |
| 05 Jul 2011 | #1 |
| | BSOD...need help!!! My Computer Specs: -Windows 7 Ultimate x64 -retail version -The computer was built in 2008, replaced harddrive in 2010, replaced rams and CPU cooling fan 2 months ago. -The OS was installed about 2 month ago, and 3 months ago, and it was a reformat 2 times. -Overclocked my computer a bit. The BSOD started around the time after i replaced new rams, and the time when my computer update to the new SP1 for Windows 7. 3 months ago when i reformated my computer, BSOD happened for about a month or so. Then i reformat again. Until now, the Computer still BSOD at random times, mostly when I'm just browsing around on internet, or watching movies from video files on my computer. Usually it BSOD once or twice in a day or every few days. But today it BSOD 3 times and the time it happened was very close. This had pushed my patient, so i'm seeking help on here now. I hope someone can help me please! I had the dump file zipped and uploaded on here... |
My System Specs | |
| 05 Jul 2011 | #2 |
| | Your Wacom(tablet) Mouse Filter driver is the most probable cause, update it Drivers | Wacom Americas ASACPI.sys the 2005 version is a huge cause of BSODs  InformationThe 2005 version 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) Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {190477, fffff8800bed8f08, fffff8800bed8760, fffff8800125d138}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapUserBuffer+28 )
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: 0000000000190477
Arg2: fffff8800bed8f08
Arg3: fffff8800bed8760
Arg4: fffff8800125d138
Debugging Details:
------------------
EXCEPTION_RECORD: fffff8800bed8f08 -- (.exr 0xfffff8800bed8f08)
ExceptionAddress: fffff8800125d138 (Ntfs!NtfsMapUserBuffer+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800bed8760 -- (.cxr 0xfffff8800bed8760)
rax=fffffa8007530830 rbx=000000016a3d8100 rcx=dffffa8007ade780
rdx=0000000000000010 rsi=0000000000000001 rdi=0000000000000000
rip=fffff8800125d138 rsp=fffff8800bed9140 rbp=fffff8800bed96e0
r8=fffff8800bed91d8 r9=fffff8800bed92a0 r10=fffff8800bed9298
r11=fffff8a000095390 r12=fffff8a0001316f0 r13=fffffa8007afd750
r14=fffffa8007530830 r15=fffffa8007530b88
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
Ntfs!NtfsMapUserBuffer+0x28:
fffff880`0125d138 f6410a05 test byte ptr [rcx+0Ah],5 ds:002b:dffffa80`07ade78a=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: drvinst.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: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsMapUserBuffer+28
fffff880`0125d138 f6410a05 test byte ptr [rcx+0Ah],5
FAULTING_IP:
Ntfs!NtfsMapUserBuffer+28
fffff880`0125d138 f6410a05 test byte ptr [rcx+0Ah],5
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff8800130eb05 to fffff8800125d138
STACK_TEXT:
fffff880`0bed9140 fffff880`0130eb05 : fffff880`0bed91f0 fffff8a0`001316f0 00000000`00000000 fffff880`013089a8 : Ntfs!NtfsMapUserBuffer+0x28
fffff880`0bed9180 fffff880`0130d754 : fffffa80`07afd750 fffffa80`07530830 00000000`00000003 00000000`ffffff30 : Ntfs!NtfsReadUsnJournal+0xb5
fffff880`0bed92f0 fffff880`012fb88a : fffffa80`07afd750 fffff8a0`001316f0 00000001`6a3d8100 fffff980`00000101 : Ntfs!NtOfsPostNewLength+0xc8
fffff880`0bed9380 fffff880`0130e203 : fffff8a0`0ef52801 fffff880`0bed96e0 fffffa80`07afd750 fffffa80`07afd750 : Ntfs!NtfsCommitCurrentTransaction+0x22a
fffff880`0bed9410 fffff880`012ea6b9 : fffff8a0`0ef52680 00000000`03854000 fffff8a0`0ef52680 fffffa80`07afd750 : Ntfs!NtfsCheckpointCurrentTransaction+0x27
fffff880`0bed9440 fffff880`012e95db : fffffa80`07afd750 fffff880`0bed96e0 fffffa80`0938fc10 fffff880`0112cf01 : Ntfs!NtfsSetEndOfFileInfo+0x2a9
fffff880`0bed9540 fffff880`0125b574 : fffffa80`07afd750 fffffa80`0938fc10 fffff880`0bed9601 fffff880`0bed9600 : Ntfs!NtfsCommonSetInformation+0x2cb
fffff880`0bed9620 fffff880`01128bcf : fffff880`0bed9750 fffffa80`0938fc10 fffffa80`07afd750 fffff880`0bed9648 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`0bed96a0 fffff880`011276df : fffffa80`04985660 fffffa80`04985660 fffffa80`04985600 fffffa80`0938fc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0bed9730 fffff800`02eb6be4 : fffffa80`091fad00 fffffa80`091fad00 fffff8a0`0fb75840 fffff880`009e9180 : fltmgr!FltpDispatch+0xcf
fffff880`0bed9790 fffff800`02e162b8 : fffffa80`091fad00 00000000`007b2915 fffffa80`08c9e650 00000000`00000000 : nt!FsRtlSetFileSize+0xc4
fffff880`0bed9800 fffff800`02dc9356 : fffff8a0`0fbe77b0 00000000`00000044 00000000`08000000 00000000`007b2915 : nt! ?? ::NNGAKEGL::`string'+0x40db0
fffff880`0bed9930 fffff800`02da7c92 : fffff880`0bed9b80 fffff880`0bed9ca0 00000000`00000000 fffff880`0bed9b78 : nt!MmCreateSection+0x5a6
fffff880`0bed9b30 fffff800`02acbf93 : fffffa80`079f7b60 00000000`0054bea8 fffff880`0bed9bc8 00000000`00000138 : nt!NtCreateSection+0x171
fffff880`0bed9bb0 00000000`771617ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0054be88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771617ba
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs!NtfsMapUserBuffer+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792f9
STACK_COMMAND: .cxr 0xfffff8800bed8760 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsMapUserBuffer+28
BUCKET_ID: X64_0x24_Ntfs!NtfsMapUserBuffer+28
Followup: MachineOwner
--------- |
| My System Specs |
| 05 Jul 2011 | #3 |
| | just one question, the Asus update link you posted...the motherboard is different than mine. Mine is a Asus P5KC ...and the one you posted is P7P55D LE does it make a different by updating what you post for my P5KC? Thanks a lot! |
| My System Specs |
| . |
| |
| 05 Jul 2011 | #4 |
| | 
Quote: Originally Posted by Gin520  just one question, the Asus update link you posted...the motherboard is different than mine. Mine is a Asus P5KC ...and the one you posted is P7P55D LE does it make a different by updating what you post for my P5KC? Thanks a lot! |
| My System Specs |
| 05 Jul 2011 | #5 |
| | Sorry to bother you with this. but this is a new BSOD today, I was watching a movie on Realplayer while using msn and browsing on internet. And then this suddenly happened. I have attached the new zipped dump file Hope to hear back from you about this soon...thank you! |
| My System Specs |
| 05 Jul 2011 | #6 |
| | just one quick additional question... could all this BSOD happening because of the new SP1 from Windows 7? I see a lot of people with BSOD...and I mean, I never had any BSOD before SP1, even if my stuff wasn't updated. |
| My System Specs |
| 06 Jul 2011 | #7 |
| |
Quote: Originally Posted by Gin520 just one quick additional question... could all this BSOD happening because of the new SP1 from Windows 7? I see a lot of people with BSOD...and I mean, I never had any BSOD before SP1, even if my stuff wasn't updated. Enable Driver Verifier then upload the new dumps which are created Driver Verifier - Enable and Disable |
| My System Specs |
| 06 Jul 2011 | #8 |
| | I did what you told me. I updated the Wacom drive, with the CD that came with it, also went to the Wacom website to download the new update as well. Also used the Verifier, but when i restart the computer, it always BSOD before i can even get into the Windows. So i uncheck few things on Verifier, and restart again...it still BSOD. I uploaded the two dump in the zip. Thank you for your help. |
| My System Specs |
| 06 Jul 2011 | #9 |
| | The cause is you nvlddmkm.sys driver used by your Nvidia video card Uninstall the driver Use Driver Sweeper to remove leftover Nvidia display driver files Reinstall the current version Drivers - Download NVIDIA Drivers If still getting crashes test your RAM RAM - Test with Memtest86+ If any errors are found you should get new RAM I recommend removing IObit Smart Defrag, it can cause some file system errors From safemode you can safely disable the driver verifier Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002dda1f0, fffff88002fd9ba8, fffff88002fd9400}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+83ae2 )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002dda1f0, The address that the exception occurred at
Arg3: fffff88002fd9ba8, Exception Record Address
Arg4: fffff88002fd9400, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ObOpenObjectByName+410
fffff800`02dda1f0 488901 mov qword ptr [rcx],rax
EXCEPTION_RECORD: fffff88002fd9ba8 -- (.exr 0xfffff88002fd9ba8)
ExceptionAddress: fffff80002dda1f0 (nt!ObOpenObjectByName+0x0000000000000410)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000008
Attempt to write to address 0000000000000008
CONTEXT: fffff88002fd9400 -- (.cxr 0xfffff88002fd9400)
rax=ffffffff8000005c rbx=fffffa8005f0fb10 rcx=0000000000000008
rdx=fffffa8004800000 rsi=fffff80002a5f000 rdi=fffffa8005f0fb10
rip=fffff80002dda1f0 rsp=fffff88002fd9de0 rbp=0000000000000000
r8=fffffa8004800000 r9=0000000000000000 r10=fffff88002fd9eb0
r11=fffff88002fd9520 r12=fffff8a0006e92a0 r13=0000000000000000
r14=fffffa80039f9d00 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ObOpenObjectByName+0x410:
fffff800`02dda1f0 488901 mov qword ptr [rcx],rax ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000008
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0e100
0000000000000008
FOLLOWUP_IP:
nvlddmkm+83ae2
fffff880`0f11cae2 ?? ???
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80002cdab60 -- (!locks fffff80002cdab60)
Resource @ nt!PiEngineLock (0xfffff80002cdab60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002cdab60
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002dad9ac to fffff80002dda1f0
STACK_TEXT:
fffff880`02fd9de0 fffff800`02dad9ac : 00000000`00000000 00000000`00000000 00000000`002d9100 fffff880`02fd9f80 : nt!ObOpenObjectByName+0x410
fffff880`02fd9eb0 fffff800`02db8a92 : fffff880`02fda2e0 fffffa80`00020019 fffff880`02fda200 00001f80`00000000 : nt!CmOpenKey+0x28a
fffff880`02fda000 fffff800`02addf93 : fffff800`02a5f000 fffffa80`0397b508 00000000`00000004 fffff800`02afc84f : nt!NtOpenKey+0x12
fffff880`02fda040 fffff800`02ada530 : fffff800`02d4e608 fffff6fb`7dbf0000 fffff880`02fda2d0 fffffa80`0397b840 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02fda1d8 fffff800`02d4e608 : fffff6fb`7dbf0000 fffff880`02fda2d0 fffffa80`0397b840 fffff800`02d4e830 : nt!KiServiceLinkage
fffff880`02fda1e0 fffff800`02d4e5c5 : 00000000`00000000 00000000`00020019 fffff880`02fda4a8 00000000`00000000 : nt!IopOpenRegistryKeyEx+0x38
fffff880`02fda240 fffff800`02d4e732 : fffffa80`04bda060 00000000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeviceObjectToDeviceInstance+0x39
fffff880`02fda270 fffff800`02d4e841 : 00000000`00000010 00000000`00000000 00000000`00000010 00000000`00010282 : nt!IopOpenOrCreateDeviceRegistryKey+0x11e
fffff880`02fda430 fffff880`0f11cae2 : fffffa80`04615680 fffff800`02dd5bc4 00000000`00000000 fffffa80`039f9b30 : nt!IoOpenDeviceRegistryKey+0x11
fffff880`02fda470 fffffa80`04615680 : fffff800`02dd5bc4 00000000`00000000 fffffa80`039f9b30 fffff880`02fda6c0 : nvlddmkm+0x83ae2
fffff880`02fda478 fffff800`02dd5bc4 : 00000000`00000000 fffffa80`039f9b30 fffff880`02fda6c0 00000000`00000000 : 0xfffffa80`04615680
fffff880`02fda480 fffff800`02d4905d : fffffa80`05c21080 00000000`00000000 00000000`65536f49 00000000`00000022 : nt!ObpCloseHandle+0x94
fffff880`02fda4d0 fffff800`02f7adcb : fffffa80`05c21330 fffffa80`04bda060 fffffa80`05c21480 fffffa80`05c6a080 : nt!IoCreateDevice+0x37d
fffff880`02fda650 fffff800`02f7aea5 : ffffd319`2f220722 fffffa80`05c6a080 00000000`00000004 fffff880`0f143510 : nt!VfFilterAttach+0xeb
fffff880`02fda6b0 fffff800`02bd7e55 : fffff880`02fda860 fffff880`02fda828 00000000`00000000 fffffa80`04bda060 : nt!VfDevObjPreAddDevice+0x35
fffff880`02fda6e0 fffff800`02ebf1d5 : 00000000`00000000 fffffa80`05c6a080 00000000`00000002 fffffa80`04bd96e0 : nt!PpvUtilCallAddDevice+0x45
fffff880`02fda720 fffff800`02ec6701 : fffffa80`04bd96e0 fffffa80`04bd96e0 00000000`00000000 00000000`00000000 : nt!PnpCallAddDevice+0xd5
fffff880`02fda7a0 fffff800`02ec7c92 : fffffa80`04bcd910 fffffa80`04bd96e0 00000000`00000002 fffffa80`04bda060 : nt!PipCallDriverAddDevice+0x661
fffff880`02fda950 fffff800`02ec812c : fffff800`02cd84e0 00000000`00000000 00000000`00000001 fffff800`02d49248 : nt!PipProcessDevNodeTree+0x2b2
fffff880`02fdabc0 fffff800`02bd8902 : 00000001`00000003 fffff800`02c7c2b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`02fdac10 fffff800`02ae9021 : fffff800`02bd8600 fffff8a0`006d1101 fffff800`02c7c200 ff31b4e8`ff31b4e8 : nt!PnpDeviceActionWorker+0x302
fffff880`02fdacb0 fffff800`02d7b32e : ff2bb3e7`ff2cb4e7 fffffa80`04615680 00000000`00000080 fffffa80`039f9b30 : nt!ExpWorkerThread+0x111
fffff880`02fdad40 fffff800`02ad0666 : fffff880`009e9180 fffffa80`04615680 fffff880`009f3f40 ff27b0e7`ff27b0e7 : nt!PspSystemThreadStartup+0x5a
fffff880`02fdad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: nvlddmkm+83ae2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
STACK_COMMAND: .cxr 0xfffff88002fd9400 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_nvlddmkm+83ae2
BUCKET_ID: X64_0x7E_VRF_nvlddmkm+83ae2
Followup: MachineOwner
--------- |
| My System Specs |
| 08 Jul 2011 | #10 |
| | I did what you told me, update the Wacom. Still BSOD. So i did a memtest, and there were no errors for both my DDR3 rams. ran it for 7 hours and all 8 pass, no errors. So i decided to just freshly reformat my computer again. keeping just the basic stuff no printer, no wacom. installed the updates, except SP1. updated that ASACPI, and also updated the video card driver to the latest. and I installed Avast antivirus, Firefox, Realplayer, KMPlayer, DivX Plus player As i was doing the last update for Windows, it BSOD. and when i was installing adobe reader, it BSOD. I uploaded 2 dump file, and Thank you for your help again. ----------------------------------------------------------- just adding one one more additional dump, after i used the verifier. the one with (070811-23462-01) is the new one after verifier. so there's 3 dump now. and also a CBS.log from the sfc/scannow from cmd... Last edited by Gin520; 08 Jul 2011 at 08:29 AM.. |
| My System Specs |
