Hi!
my name is mike and i recently bought an Ascer Aspire 6930 .The problem appeared while i was playing gta 4 and i alt tabbed . Then again the second day while i did the same thing . Here is my upload with the minidump . If someone can help please. Thank you for reading ! have a nice day
These 3 crashes have different causes. All of which are win 7 files. I would run a system file check to verify and repair them
Type cmd in search>right click and run as admin>sfc /scannow (notee the space between sfc and "/")
If you are overclocking stop
Let us know the results of sfc as you may have to run it again
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Minidump\032210-23103-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*F:\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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9be50 Debug session time: Mon Mar 22 17:23:02.096 2010 (GMT-4) System Uptime: 0 days 4:32:10.328 Loading Kernel Symbols ............................................................... ................................................................ ......................................... Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c2cdb4b8, 0, fffff960007bdcd0, 0} Could not read faulting driver name Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+b0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff900c2cdb4b8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff960007bdcd0, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d060e0 fffff900c2cdb4b8 FAULTING_IP: cdd!CddBitmapHw::Release+b0 fffff960`007bdcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: GTAIV.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880093186a0 -- (.trap 0xfffff880093186a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff900c2cda020 rbx=0000000000000000 rcx=fffff900c01a3370 rdx=fffffa8004730060 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960007bdcd0 rsp=fffff88009318830 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0000000000001c9e r11=fffff88009318850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cdd!CddBitmapHw::Release+0xb0: fffff960`007bdcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] ds:fffff900`c2cdb4b8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b4f1e4 to fffff80002acff00 STACK_TEXT: fffff880`09318538 fffff800`02b4f1e4 : 00000000`00000050 fffff900`c2cdb4b8 00000000`00000000 fffff880`093186a0 : nt!KeBugCheckEx fffff880`09318540 fffff800`02acdfee : 00000000`00000000 fffff900`c00bf010 fffff900`c0235b00 fffff800`02adbb02 : nt! ?? ::FNODOBFM::`string'+0x42907 fffff880`093186a0 fffff960`007bdcd0 : 00000000`00000000 00000258`00000000 0000098a`c30099f0 fffff900`c204ed40 : nt!KiPageFault+0x16e fffff880`09318830 fffff960`00155080 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c1f86cd0 : cdd!CddBitmapHw::Release+0xb0 fffff880`09318870 fffff960`0015d4a9 : 00000000`00000000 00000000`00000001 fffff900`c1f86cd0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358 fffff880`093189c0 fffff960`00154920 : 00000000`00000258 00000000`00000000 fffff900`c2b72400 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9 fffff880`09318a20 fffff960`00154063 : fffffa80`06c2d700 00000000`00000001 fffffa80`04730060 fffffa80`05368e70 : win32k!GdiProcessCallout+0x200 fffff880`09318aa0 fffff800`02db25e1 : fffffa80`06c2d770 00000000`00000000 00000000`00000000 fffffa80`04730060 : win32k!W32pProcessCallout+0x6b fffff880`09318ad0 fffff800`02d8bcb8 : 00000000`00000000 00000000`00000001 fffffa80`04433900 00000000`00000000 : nt!PspExitThread+0x2b1 fffff880`09318ba0 fffff800`02acf153 : fffffa80`04433930 00000000`00000000 fffffa80`04730060 fffffa80`04912ad0 : nt!NtTerminateProcess+0x138 fffff880`09318c20 00000000`76ea017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0021de28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ea017a STACK_COMMAND: kb FOLLOWUP_IP: cdd!CddBitmapHw::Release+b0 fffff960`007bdcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: cdd!CddBitmapHw::Release+b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdd IMAGE_NAME: cdd.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bde94 FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+b0 BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+b0 Followup: MachineOwner ---------
Composing this as zigzag3143 posted :)
No firm evidence from the 3 memory dumps.
Please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
- - The most common drivers are listed on this page: Driver ReferenceHow To Find Drivers:
- 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.
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
If that doesn't stop the BSOD's, then please run Driver Verifier according to these directions:Code:VSTAZL6.SYS Wed Oct 15 20:53:42 2008 - SoftK56 Modem Driver by Conexant Systems - http://www.carrona.org/dvrref.html#VSTAZL6.SYS VSTCNXT6.SYS Wed Oct 15 20:52:22 2008 - SoftK56 Modem Driver by Conexant Systems - http://www.carrona.org/dvrref.html#VSTCNXT6.SYS VSTDPV6.SYS Wed Oct 15 20:57:45 2008 - SoftK56 Modem Driver by Conexant Systems - http://www.carrona.org/dvrref.html#VSTDPV6.SYS winbondcir.sys Wed Mar 28 01:50:09 2007 - Winbond MCE CIR Port driver (infrared receiver) probably best obtained from the PC Manufacturer - http://www.carrona.org/dvrref.html#winbondcir.sys
Summary of the BSOD's: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.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Mar 23 15:24:33.225 2010 (GMT-4) System Uptime: 0 days 0:25:20.457 BugCheck 3B, {c0000005, fffff80002a4f01e, fffff88009548e20, 0} Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 ) BUGCHECK_STR: 0x3B PROCESS_NAME: cstrike.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Mar 23 14:10:44.327 2010 (GMT-4) System Uptime: 0 days 13:32:44.559 BugCheck 3B, {c0000005, fffff96000194283, fffff8800836c060, 0} Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 ) BUGCHECK_STR: 0x3B PROCESS_NAME: dwm.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Mon Mar 22 17:23:02.096 2010 (GMT-4) System Uptime: 0 days 4:32:10.328 BugCheck 50, {fffff900c2cdb4b8, 0, fffff960007bdcd0, 0} Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+b0 ) BUGCHECK_STR: 0x50 PROCESS_NAME: GTAIV.exe
@zigzag: verification 100% complete
Windows Resource Protection did not found any integrity violations. what now?
Remove or update the drivers specified in my post (the dialup modem and the InfraRed (IR) driver).
Then run Driver Verifier if the BSOD's continue.
Quote