New
#1
BSOD playing BF3, fresh instal of W7
Hi i just got multiple BSODs after installing W7 Home Premium. I had have BSODs before that.
Hi i just got multiple BSODs after installing W7 Home Premium. I had have BSODs before that.
The single DMP file is corrupt. We need more. Thanks
Sorry, if you mean minidump file. It's here.
My PC seems to work now, after windows installed service pack 1 and some other updates. I'll post here new crash reports if it happens again.
Hi! Can you tell something about this?
Problem Devices:Code:USB-Controller PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_03\FFFFFFFFFFFFFFFF00 The drivers for this device are not installed.
Crashes may be due to a virus. Recommend a full scan with avast! and also with Malwarebytes : Free anti-malware, anti-virus and spyware removal download. After downloading Malwarebytes, update it, do not start the trial, and run a full scan of your system.Code:Loading Dump File [D:\Kingston\BSODDmpFiles\Vulcan7\Windows_NT6_BSOD_jcgriff2\042512-18735-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea8670 Debug session time: Wed Apr 25 12:48:00.121 2012 (UTC - 6:00) System Uptime: 0 days 0:41:37.931 Loading Kernel Symbols ............................................. Loading User Symbols Missing image name, possible paged-out or corrupt data. Loading unloaded module list .....Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ...Missing image name, possible paged-out or corrupt data. .....Missing image name, possible paged-out or corrupt data. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {11, 7, 0, fffff880049b9bc9} Probably caused by : Unknown_Module_fffffa80`00000024 ( Unknown_Module_fffffa80`00000024>+83bf8dc ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000011, memory referenced Arg2: 0000000000000007, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880049b9bc9, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f12100 0000000000000011 CURRENT_IRQL: 0 FAULTING_IP: +3162613763613638 fffff880`049b9bc9 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System LAST_CONTROL_TRANSFER: from fffff880042c672d to fffff880042c66e4 STACK_TEXT: fffff800`03fabc68 fffff880`042c672d : 00000000`00000001 fffffa80`083bf900 ffffffff`fffffffe 00000000`00000050 : 0xfffff880`042c66e4 fffff800`03fabc70 00000000`00000001 : fffffa80`083bf900 ffffffff`fffffffe 00000000`00000050 00000000`00000001 : 0xfffff880`042c672d fffff800`03fabc78 fffffa80`083bf900 : ffffffff`fffffffe 00000000`00000050 00000000`00000001 fffff800`02ce94a9 : <Unloaded_Unknown_Module_00000000`00000000>+0x1 fffff800`03fabc80 ffffffff`fffffffe : 00000000`00000050 00000000`00000001 fffff800`02ce94a9 00000000`002fe58b : <Unloaded_Unknown_Module_fffffa80`00000024>+0x83bf8dc fffff800`03fabc88 00000000`00000050 : 00000000`00000001 fffff800`02ce94a9 00000000`002fe58b fffffa80`083ce2d0 : 0xffffffff`fffffffe fffff800`03fabc90 00000000`00000001 : fffff800`02ce94a9 00000000`002fe58b fffffa80`083ce2d0 fffff800`02e55e80 : <Unloaded_Unknown_Module_00000000`00000000>+0x50 fffff800`03fabc98 fffff800`02ce94a9 : 00000000`002fe58b fffffa80`083ce2d0 fffff800`02e55e80 00000000`00000000 : <Unloaded_Unknown_Module_00000000`00000000>+0x1 fffff800`03fabca0 fffff800`02cd793c : fffff800`02e55e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x52a fffff800`03fabd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: Unknown_Module_fffffa80`00000024>+83bf8dc fffffa80`083bf900 ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: Unknown_Module_fffffa80`00000024>+83bf8dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module_fffffa80`00000024 IMAGE_NAME: Unknown_Module_fffffa80`00000024 DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0xD1_Unknown_Module_fffffa80_00000024_+83bf8dc BUCKET_ID: X64_0xD1_Unknown_Module_fffffa80_00000024_+83bf8dc Followup: MachineOwner ---------
The crashes may also be due to the uninstalled USB controller... Please install it from your motherboard's support site: ASUS - Motherboards- ASUS M4A88TD-M/USB3 -> Download -> Windows 7 64bit -> USB -> USB 3.0 Host Controller Driver 1.0.20.0 for Windows 32/64bit XP & 32/64bit Vista& 32/64bit 7.