New
#1
2 BSOD's in last 10 min
I have just recently had 2 bsod in the last 10 min anyone else having this problem
I have just recently had 2 bsod in the last 10 min anyone else having this problem
I will bet you are 64 bit, right?
I have just finished my 18 analysis and 16 were 64bit. we really need the dmp file to tell you what caused it. use these to find and upload. https://www.sevenforums.com/crash-loc...d-problem.html
thanks
Ken J+
here is the mini dump 4 bsods today i think. and yes its 64 bit.
Magicboy, seems to be a corrupt Network driver.
Open command prompt (run as admin) and type this:
You should also try to remove and then reinstall your network driver.Code:sfc /scannow
~Lordbob
Thanks im running the scan just now, I recently reinstalled the network driver to try to stop first boot of day crashing but that didn't work. My computer is also running slower than it did when i got it. it takes about 20 seconds saying starting windows then about 10 seconds to use it. I didnt know if that had anything to do with it. thanks
20 seconds is a good start time. Mine is a lot more than that.....
Also, open up the Network and Sharking center, click on change adapter settings, then right click on your adapter and hit properties. What is installed, and what is not?
~Lordbob
I'm in it but how do i know whats installed and whats not, and that scan just finished and said windows resource protection did not find any integrity violations.
Even before I look at them I will bet it is memory. be right back
Well guess what, memory corruption.
64bit is extremely sensitive to memory changes.
here is what I would do
downlaod memtestx86 and run it for 5 passes. Yes its a long time. we need to find out if it is memory or heat
run a system file check
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking STOP
make sure all the BIOS settings are stock
Good Luck
Ken J+
Code:011710-16286-01.dmp 1/17/2010 8:00:56 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02f10090 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder\011710-16286-01.dmp 4 15 7600 011710-17877-01.dmp 1/17/2010 7:55:52 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02f00090 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder\011710-17877-01.dmp 4 15 7600 011710-20950-01.dmp 1/17/2010 11:05:52 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`039a1890 00000000`00000000 fffff880`02d57a59 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\New folder\011710-20950-01.dmp 4 15 7600Code:Loading Dump File [C:\Users\K\Desktop\New folder\011710-16286-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 Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e50 Debug session time: Sun Jan 17 15:00:09.566 2010 (GMT-5) System Uptime: 0 days 0:04:39.002 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {28, 2, 0, fffff80002f10090} Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000028, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002f10090, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031040e0 0000000000000028 CURRENT_IRQL: 2 FAULTING_IP: nt!MiFindNodeOrParent+0 fffff800`02f10090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: iexplore.exe TRAP_FRAME: fffff880033165c0 -- (.trap 0xfffff880033165c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f10090 rsp=fffff88003316758 rbp=0000000000000000 r8=fffff880033167a0 r9=0000000000000000 r10=fffffa8003dd7da0 r11=fffffa800404a070 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!MiFindNodeOrParent: fffff800`02f10090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:6748:00000000`00000028=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecd469 to fffff80002ecdf00 STACK_TEXT: fffff880`03316478 fffff800`02ecd469 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`03316480 fffff800`02ecc0e0 : fffff880`00fbd604 fffffa80`03dd7de8 00000000`00000008 fffff880`00fbe8ff : nt!KiBugCheckDispatch+0x69 fffff880`033165c0 fffff800`02f10090 : fffff800`02f13e17 fffff880`02fd3180 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x260 fffff880`03316758 fffff800`02f13e17 : fffff880`02fd3180 00000000`00000002 00000000`00000000 00000000`000008e1 : nt!MiFindNodeOrParent fffff880`03316760 fffff800`02f13d9d : 00000000`63416d4d 00000000`00000002 00000000`00000000 00000000`00001000 : nt!MiLocateAddressInTree+0x17 fffff880`03316790 fffff800`02f13ea8 : 00000000`00000000 fffffa80`06b82000 fffffa80`054896b0 fffffa80`03dd7e90 : nt!MiGetSharedProtosAtDpcLevel+0xbd fffff880`033167e0 fffff800`02e6a19b : fffffa80`04295018 fffff800`02ee1490 fffff880`033168d8 fffff880`02fd3180 : nt!MiGetSharedProtos+0x18 fffff880`03316810 fffff800`02fd2810 : 00000000`00000000 fffffa80`03dd7de0 fffff880`02fd3180 fffff800`02edbf21 : nt! ?? ::FNODOBFM::`string'+0x92bb fffff880`03316840 fffff800`02fd29f0 : fffffa80`041b5b30 00000003`00000000 fffffa80`03dd7da0 fffffa80`03dd7e90 : nt!MiEmptyPageAccessLog+0x160 fffff880`033168b0 fffff800`02fd2bf6 : fffffa80`05489000 00000000`00003350 fffff680`00037fc0 00000000`00000000 : nt!MiAllocateAccessLog+0x80 fffff880`033168e0 fffff800`02f361d8 : 00000003`00000000 b5000000`6549f867 00000000`00000000 00000000`00003350 : nt!MiLogPageAccess+0x46 fffff880`03316930 fffff800`02f4ea0e : fffffa80`041b5ec8 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt! ?? ::FNODOBFM::`string'+0x21846 fffff880`03316ae0 fffff800`02ee26e2 : 00000000`00000117 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x49926 fffff880`03316b80 fffff800`02ee296f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03316bd0 fffff800`03171166 : fffffa80`03a06680 00000000`00000080 fffffa80`039e7040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`03316d40 fffff800`02eac486 : fffff880`02f63180 fffffa80`03a06680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316710 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiFindNodeOrParent+0 fffff800`02f10090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiFindNodeOrParent+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 Followup: MachineOwner ---------
Last edited by zigzag3143; 17 Jan 2010 at 16:51.
Ok good. There should be a short list of some weird things like TCP/IP Protocol 4 and 6, etc. They should either have a checkmark or not.
~Lordbob