[Yazmin]

Loading Dump File [C:\Windows\Minidump\103013-5350-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e9e6d0
Debug session time: Wed Oct 30 00:01:01.783 2013 (UTC - 7:00)
System Uptime: 0 days 0:01:37.016
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c5b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt+a7f2a
fffff800`02d02f2a 488b4908 mov rcx,qword ptr [rcx+8]

EXCEPTION_RECORD: fffff880031e04c8 -- (.exr 0xfffff880031e04c8)
ExceptionAddress: fffff80002d02f2a (nt+0x00000000000a7f2a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880031dfd20 -- (.cxr 0xfffff880031dfd20;r)
rax=8b6a175628134268 rbx=fffffa8006706040 rcx=8b6a175628134268
rdx=fffffa8008003acb rsi=fffffa8009268d48 rdi=fffffa8007942e60
rip=fffff80002d02f2a rsp=fffff880031e0708 rbp=fffffa8008003270
r8=000000000000000c r9=00000000000007ff r10=0000000000000801
r11=0000000000000000 r12=fffff8a000380000 r13=0000000000000000
r14=fffff8a000381338 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0xa7f2a:
fffff800`02d02f2a 488b4908 mov rcx,qword ptr [rcx+8] ds:002b:8b6a1756`28134270=????????????????
Last set context:
rax=8b6a175628134268 rbx=fffffa8006706040 rcx=8b6a175628134268
rdx=fffffa8008003acb rsi=fffffa8009268d48 rdi=fffffa8007942e60
rip=fffff80002d02f2a rsp=fffff880031e0708 rbp=fffffa8008003270
r8=000000000000000c r9=00000000000007ff r10=0000000000000801
r11=0000000000000000 r12=fffff8a000380000 r13=0000000000000000
r14=fffff8a000381338 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0xa7f2a:
fffff800`02d02f2a 488b4908 mov rcx,qword ptr [rcx+8] ds:002b:8b6a1756`28134270=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8000306b770 to fffff80002d02f2a

STACK_TEXT:
fffff880`031e0708 fffff800`0306b770 : fffffa80`09268d48 fffffa80`06706040 fffff880`00000006 fffff8a0`02c5f7c0 : nt+0xa7f2a
fffff880`031e0710 fffffa80`09268d48 : fffffa80`06706040 fffff880`00000006 fffff8a0`02c5f7c0 fffff8a0`00283170 : nt+0x410770
fffff880`031e0718 fffffa80`06706040 : fffff880`00000006 fffff8a0`02c5f7c0 fffff8a0`00283170 00000000`00000000 : 0xfffffa80`09268d48
fffff880`031e0720 fffff880`00000006 : fffff8a0`02c5f7c0 fffff8a0`00283170 00000000`00000000 00000000`00000000 : 0xfffffa80`06706040
fffff880`031e0728 fffff8a0`02c5f7c0 : fffff8a0`00283170 00000000`00000000 00000000`00000000 fffffa80`092654c0 : 0xfffff880`00000006
fffff880`031e0730 fffff8a0`00283170 : 00000000`00000000 00000000`00000000 fffffa80`092654c0 00000000`00000001 : 0xfffff8a0`02c5f7c0
fffff880`031e0738 00000000`00000000 : 00000000`00000000 fffffa80`092654c0 00000000`00000001 00000000`00000002 : 0xfffff8a0`00283170


FOLLOWUP_IP:
nt+a7f2a
fffff800`02d02f2a 488b4908 mov rcx,qword ptr [rcx+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+a7f2a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

STACK_COMMAND: .cxr 0xfffff880031dfd20 ; kb

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner




-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




Loading Dump File [C:\Users\Alejandro\Desktop\Minidump\103013-4867-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e596d0
Debug session time: Wed Oct 30 00:06:54.362 2013 (UTC - 7:00)
System Uptime: 0 days 0:01:53.595
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0431561b8, 0, fffff8800119a039, 5}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : fltmgr.sys ( fltmgr+5039 )




--------------------------------------------------------------------------------------------------



Loading Dump File [C:\Users\Alejandro\Desktop\Minidump\102913-5241-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e996d0
Debug session time: Tue Oct 29 23:57:24.454 2013 (UTC - 7:00)
System Uptime: 0 days 0:21:14.687
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88003f178e6, fffff88008e8f9c0, 0}

*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : afd.sys ( afd+468e6 )


__________________________________________________________________________________________________________________________________________


Loading Dump File [C:\Users\Alejandro\Desktop\Minidump\102913-3666-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02eab6d0
Debug session time: Tue Oct 29 23:25:06.340 2013 (UTC - 7:00)
System Uptime: 0 days 0:02:47.573
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {b, fffffa80069d3320, 0, fffffa80069d3630}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.




I BUILD A NEW COMPUTER EVERYTHING IS NEW EXCEPT MY MEMORY RAM ITS FROM THE OTHER PC. AND WHEN I INSTALLED W7 I HAD TO REMOVE THE VIDEO CARD BECAUSE WITH THE VIDEO CARD CANT PASS THE EXPADING FILES.


I ATTACH ALL THE INFO THE PC AND THE MINIDUMPS

Attached Files

•  Minidump.rar   407.82KB   138 downloads

Edited by Yazmin, 30 October 2013 - 02:16 AM.

[Advertisements]

those error i have today error 0x0000109, 0x000000a, 0x000007e, fltmgr.sys, afd.sys, bad pool caller, bad pool header, page_fault_in_nonpaged_area, 0x00000050

[Yazmin]

those error i have today error 0x0000109, 0x000000a, 0x000007e, fltmgr.sys, afd.sys, bad pool caller, bad pool header, page_fault_in_nonpaged_area, 0x00000050

[Yazmin]

and i have all the driver update

Edited by Yazmin, 30 October 2013 - 02:15 AM.

[Yazmin]

its windows 7 ultimate

[phillpower2]

Yazmin

What type of OS disk do you have as in full retail, OEM, downloaded ISO, a burned copy or a back up that you made yourself.

Can you also provide the brand and model name or number details for the MB, CPU and the Ram.

Please do not reply to your own OP or last reply as it may lead to your request for help being overlooked, staff and members who assist on the forums will always check out a topic that has not received any replies to see if they are able to help, if you reply to your own OP it will appear to others viewing the board that you have received a reply and so are already being helped.

If you have something to add while waiting for a reply use the edit tab – bottom right of the dialogue input box and this will ensure that no information that you provide is overlooked (this can happen if your topic has more than one page) thank you for understanding.

[Yazmin]

Hi, I HAVE the Windows 7 ultimate 64BIT totally update from a new cd a bought and the

16gbs of ram Vengance 1600mhz 1.5v BUT I TOOK IT OF 14GBS AND I ONLY HAVE RIGHT NOW 2GBS
motherboard GIGABYTE GA-ZZZ7X-UD3H
INTEL I5-3570K CPU 3.40GHZ
hdd: 250 SSD (HAS THE WIN7)
1TB HDD SATA II
VIDEOCARD: EVGA GEFORCE GTX 660 2GBS
POWERSUPPLY: 700W OCZ

I ATTACH ALL THE INFO FROM EVEREST PROGRAM ABOUT MY PC

Attached Files

•  Report.rar   161.91KB   144 downloads

Edited by Yazmin, 30 October 2013 - 05:13 PM.

[phillpower2]

Hello

Sorry but I am a bit confused by the following from your last reply;

16gbs of ram Vengance 1600mhz 1.5v BUT I TAKE IT OF 14GBS I ONLY INSTALL ONLY 2GBS

16GB of Ram would normally be 4 X 4GB or 2 X 8GB sticks, what do you have to be able to only try a 2GB stick.

I would try two matching sticks of Ram to begin with and place them in DDR slots 1 and 2 as shown in the attachment below.

Please try restoring the MBs default factory settings in the BIOS in case there is a bad setting.

Your MB has a debug LED on it, if restoring the MBs default settings does not help check the debug LED and see what code it shows, you can then check your manual to see what it says.

[Yazmin]

Was problem with my ram so i only leave 1, 2gbs ram on the first slot but i will check if is the ram or its the slot from the motherboard

Edited by Yazmin, 30 October 2013 - 05:29 PM.

[Yazmin]

....

Edited by Yazmin, 30 October 2013 - 05:29 PM.

[GlendaPeter1]

Most of the time, PC freezes by lots of reasons. Corrupt registry, unnecessary applications, too many start-up items as well as virus infection would be the major reasons contributing to this problem. Many PC users simply utilize PC yet never consider how to maintain and optimize PC performance. I would suggest you to download any reliable program to fix registry, to manage unnecessary applications & start-up items like am using RegInOut for it. Download Anti-Virus like Avast or NOD32 to remove viruses from your PC.