BSOD Win7 64bit , Help!

Do u have any other minidumps, didn't see much from the one u post

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.190\061210-15600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0404c000 PsLoadedModuleList = 0xfffff800`04289e50
Debug session time: Sat Jun 12 15:17:01.545 2010 (UTC - 7:00)
System Uptime: 0 days 0:42:53.808
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80004107a83, 0, 45b292a6}
Probably caused by : ntkrnlmp.exe ( nt!KiDpcInterrupt+173 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80004107a83, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000045b292a6, Parameter 1 of the exception
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!KiDpcInterrupt+173
fffff800`04107a83 4c8b4dd0        mov     r9,qword ptr [rbp-30h]
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000045b292a6
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800042f40e0
 0000000045b292a6 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  StarEdit.exe
CURRENT_IRQL:  0
EXCEPTION_RECORD:  fffff8800a9389e8 -- (.exr 0xfffff8800a9389e8)
ExceptionAddress: fffff80004107a83 (nt!KiDpcInterrupt+0x0000000000000173)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000045b292a6
Attempt to read from address 0000000045b292a6
TRAP_FRAME:  fffff8800a938a90 -- (.trap 0xfffff8800a938a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000007efdb000 rbx=0000000000000000 rcx=fffffa8004cf7720
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004107a83 rsp=fffff8800a938c20 rbp=fffff8800a938ca0
 r8=fffffa8005afd9a8  r9=0000000000000000 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiDpcInterrupt+0x173:
fffff800`04107a83 4c8b4dd0        mov     r9,qword ptr [rbp-30h] ss:fffff880`0a938c70=0000000077a6fef1
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800040f6929 to fffff800040bc600
STACK_TEXT:  
fffff880`0a938218 fffff800`040f6929 : 00000000`0000001e ffffffff`c0000005 fffff800`04107a83 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a938220 fffff800`040bbc42 : fffff880`0a9389e8 00000000`76e3eef4 fffff880`0a938a90 00000000`017c03b3 : nt!KiDispatchException+0x1b9
fffff880`0a9388b0 fffff800`040ba7ba : 00000000`00000000 00000000`76e3eef4 80000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a938a90 fffff800`04107a83 : 00000000`00000000 fffffa80`04cf7720 fffff880`0a938ca0 00000000`7efdb000 : nt!KiPageFault+0x23a
fffff880`0a938c20 00000000`769a8caf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x173
00000000`0018fbe4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x769a8caf

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiDpcInterrupt+173
fffff800`04107a83 4c8b4dd0        mov     r9,qword ptr [rbp-30h]
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt!KiDpcInterrupt+173
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiDpcInterrupt+173
BUCKET_ID:  X64_0x1E_c0000005_nt!KiDpcInterrupt+173
Followup: MachineOwner
---------

Please zip up the entire contents of the Minidump folder and upload it with your next post.

This memory dump points to ntkrnlmp.exe - this is the kernel (core) of the OS. If this was the cause of the error, you'd be having many more problems than just the occasional BSOD.

So, we've gotta look elsewhere for the source of the error. Unfortunately, this is a STOP 0x1E error (more info here: BSOD Index ) That means that this can be either a hardware or a software error.

So, let's try and force the software error by using Driver Verifier. We've got a couple of possibilities here - it may point to a 3rd party software error or it may not. If it doesn't, we've got more troubleshooting to do. So, please follow these directions to run Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 18:17:01.545 2010 (UTC - 4:00)
System Uptime: 0 days 0:42:53.808
BugCheck 1E, {ffffffffc0000005, fffff80004107a83, 0, 45b292a6}
Probably caused by : ntkrnlmp.exe ( nt!KiDpcInterrupt+173 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  StarEdit.exe

Please download and run this ASACPI installer: https://www.sevenforums.com/attachmen...b_win7_atk.zip

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 26 20:26:36.922 2010 (GMT-4)
System Uptime: 0 days 1:54:54.185
BugCheck 3B, {c000001d, fffff8000418318d, fffff8800b026fd0, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpDispatchReplyToWaitingThread+18d )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 14:57:18.225 2010 (GMT-4)
System Uptime: 0 days 1:52:20.350
BugCheck A, {fffff50009fd4fa8, 2, 1, fffff8000400e42c}
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 18:34:55.470 2010 (GMT-4)
System Uptime: 0 days 3:36:33.733
BugCheck A, {1c7, 2, 1, fffff800040fde86}
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+146 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  emule.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 15:56:52.867 2010 (GMT-4)
System Uptime: 0 days 0:10:57.130
BugCheck 3B, {c0000005, fffff800040808a9, fffff8800ad5e1e0, 0}
Probably caused by : win32k.sys ( win32k!GetQueueStatus+e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 21:53:09.537 2010 (GMT-4)
System Uptime: 0 days 12:38:45.800
BugCheck 50, {ffffffffffffff84, 1, fffff80004186415, 0}
Probably caused by : memory_corruption ( nt!MiQueuePageAccessLog+5 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 14:40:32.680 2010 (GMT-4)
System Uptime: 0 days 1:26:47.943
BugCheck A, {46a8085d0, 2, 1, fffff800040c0085}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiAdjustWorkerThreadPriority+19e )
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 18:17:01.545 2010 (GMT-4)
System Uptime: 0 days 0:42:53.808
BugCheck 1E, {ffffffffc0000005, fffff80004107a83, 0, 45b292a6}
Probably caused by : ntkrnlmp.exe ( nt!KiDpcInterrupt+173 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  StarEdit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 13 21:09:29.796 2010 (GMT-4)
System Uptime: 0 days 0:00:12.074
BugCheck 1000007E, {ffffffffc0000005, fffff80004358716, fffff880045e7c48, fffff880045e74b0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiReadPnpRegistryValue+107 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 13 21:10:40.428 2010 (GMT-4)
System Uptime: 0 days 0:00:46.706
BugCheck C4, {f6, 190, fffffa8007d153e0, fffff8800544c257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  AiNap.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

If the ASACPI.sys driver that you download has the same date/time stamp as the one that's currently installed - you have no way of knowing if it has been replaced.

So, rename the ASACPI.sys file (that's in C:\Windows\System32\drivers) to ASACPI.BAK
Then install the new one and it should just slide right in there.
Verify that you have both the .sys and the .BAK when done.

The one cited in the crash was:

Code:

ASACPI.sys   Wed May 13 21:25:17 2009

I've seen a lot of people claiming that the file isn't necessary - but none of those can cite any documentation that proves it. There are some people who don't have it and don't have problems - but this is a complex, low-level driver issue that's not just as simple as "If it worked for me, it'll work for you."

AFAIK, you just double click on AsAcpiIns.exe in the folder named 64 - that should install it.
BTW - if you find it elsewhere, copy it over to C:\Windows\System32\drivers