System specs.
Attachment 42892
Memory dump
Attachment 42893
Common things I'm doing when it Bsod's
Gaming / reading on the internet / walking away with nothing running to grab a pepsi.
Things I've done
Upgraded all drivers for all hardware, Reinstalled windows, Ripped my hair out.
(Thinking I might just downgrade back to vista, never had these issues with it...)
Let me know if anyone can help. Amazed this hasn't Bsod'd on me while typing this.
Hi and welcome. Most of the dmps are similar. I see several issues. First hardware. In the 124 bugcheck, the hardware abstraction layer was involved. In the others it is always IRQ
I suspect you may have a memory issue making it appear more randon than it actually is.
I would
download and run memtestx86 for several hours
run a system file check to verify and repair your system files.
type cmd in search>right click and ru n as admin>sfc /scannow
If you are overclocking stop
If you are running a raid update its driver
Hope this helps
Ken J+
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\121909-19219-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50 Debug session time: Sat Dec 19 04:01:34.700 2009 (GMT-5) System Uptime: 0 days 3:17:32.698 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2a893f3, d, 8, 2a893f3} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) 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: 0000000002a893f3, memory referenced Arg2: 000000000000000d, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000002a893f3, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0 0000000002a893f3 CURRENT_IRQL: d FAULTING_IP: +5b35952f01eed884 00000000`02a893f3 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff80000b9c930 -- (.trap 0xfffff80000b9c930) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=75c8ab129245cc01 rbx=0000000000000000 rcx=0000000000000011 rdx=000000000000ee41 rsi=0000000000000000 rdi=0000000000000000 rip=0000000002a893f3 rsp=fffff80000b9cac0 rbp=fffff80000b9cb40 r8=0000000000011b92 r9=0000000000000000 r10=0000000000000000 r11=fffff80000b9ca60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc 00000000`02a893f3 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a8c469 to fffff80002a8cf00 FAILED_INSTRUCTION_ADDRESS: +5b35952f01eed884 00000000`02a893f3 ?? ??? STACK_TEXT: fffff800`00b9c7e8 fffff800`02a8c469 : 00000000`0000000a 00000000`02a893f3 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx fffff800`00b9c7f0 fffff800`02a8b0e0 : 00000000`00000000 00000000`00000000 fffffa80`05854340 fffff880`041b47da : nt!KiBugCheckDispatch+0x69 fffff800`00b9c930 00000000`02a893f3 : fffffa80`04d33d48 fffffa80`04d33000 fffffa80`04d33000 fffffa80`0559e190 : nt!KiPageFault+0x260 fffff800`00b9cac0 fffffa80`04d33d48 : fffffa80`04d33000 fffffa80`04d33000 fffffa80`0559e190 fffffa80`04d33000 : 0x2a893f3 fffff800`00b9cac8 fffffa80`04d33000 : fffffa80`04d33000 fffffa80`0559e190 fffffa80`04d33000 00001f80`00000000 : 0xfffffa80`04d33d48 fffff800`00b9cad0 fffffa80`04d33000 : fffffa80`0559e190 fffffa80`04d33000 00001f80`00000000 00000000`0001fca1 : 0xfffffa80`04d33000 fffff800`00b9cad8 fffffa80`0559e190 : fffffa80`04d33000 00001f80`00000000 00000000`0001fca1 fffffa80`04fad120 : 0xfffffa80`04d33000 fffff800`00b9cae0 fffffa80`04d33000 : 00001f80`00000000 00000000`0001fca1 fffffa80`04fad120 fffffa80`04fd8eb8 : 0xfffffa80`0559e190 fffff800`00b9cae8 00001f80`00000000 : 00000000`0001fca1 fffffa80`04fad120 fffffa80`04fd8eb8 00000000`00000000 : 0xfffffa80`04d33000 fffff800`00b9caf0 00000000`0001fca1 : fffffa80`04fad120 fffffa80`04fd8eb8 00000000`00000000 00000001`3c4b16ac : 0x1f80`00000000 fffff800`00b9caf8 fffffa80`04fad120 : fffffa80`04fd8eb8 00000000`00000000 00000001`3c4b16ac 00000000`000133d6 : 0x1fca1 fffff800`00b9cb00 fffffa80`04fd8eb8 : 00000000`00000000 00000001`3c4b16ac 00000000`000133d6 00000000`00000002 : 0xfffffa80`04fad120 fffff800`00b9cb08 00000000`00000000 : 00000001`3c4b16ac 00000000`000133d6 00000000`00000002 fffff880`0ff5a445 : 0xfffffa80`04fd8eb8 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02a8b0e0 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 Followup: MachineOwner ---------Code:121209-23041-01.dmp 12/12/2009 6:45:35 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffffff`ffffff82 00000000`00000002 00000000`00000001 fffff800`02acb865 ntoskrnl.exe ntoskrnl.exe+71f00 121509-20529-01.dmp 12/15/2009 2:54:53 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00a1ad77 00000000`00000002 00000000`00000001 fffff880`0185625a tcpip.sys tcpip.sys+5625a 121909-19219-01.dmp 12/19/2009 4:11:48 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`02a893f3 00000000`0000000d 00000000`00000008 00000000`02a893f3 ntoskrnl.exe ntoskrnl.exe+71f00 122009-18688-01.dmp 12/20/2009 6:41:03 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`02ae1fa6 00000000`00000002 00000000`00000008 00000000`02ae1fa6 ntoskrnl.exe ntoskrnl.exe+71f00 122009-21387-01.dmp 12/20/2009 2:04:42 PM 0x00000124 00000000`00000000 fffffa80`04b03028 00000000`b2000040 00000000`00000800 hal.dll hal.dll+12903
I saw these problems coming a mile away. When I went from Vista to 7 I had to change my bios settings a bit or there was no way it was going to run stable. Yeah, but what do I know, I'm just a stupid overclocker.
I would hate to give any advice that actually required the user to adjust those dreaded bios settings. Those settings are only for overclocking right?... or maybe not.
Quote