Random crashes

mambowarrior · Nov 3, 2009

I have multiple times a day random crashes of the system on non particular issues. Sometimes it's with just surfing on the internet, sometimes it's when i start playing a AVI file, sometimes it's when i have the internetradio on.

New ASUS P5QL Pro motherboard with Windows 7 x64. 8GB. fresh install, moved from Vista 64 Bit. Vista had no problems...

Have Run memory test86 v2.11 and no errors. 2 cards: Nvidia videocard 9500GT and Creative Audigy 2 ZS soundcard. Updated all drivers (nvidia / creative) and offcourse latest drivers Asus / Windows Update.

Please advise... added the dumps and my pc nfo..

torrentg · Nov 3, 2009

Completely uninstall AVG Antivirus from system. Test. Do same for 3rd party firewall software, if any. Test.

usasma · Nov 3, 2009

Multiple different BSOD error messages, coupled with the hardware issues mentioned below - suggests to me that you may have a hardware issue if the AVG replacement doesn't fix things.

You have 3 problematic devices. Check your device manager for them. Either update the drivers or remove the devices from your system (if built in, disable them in Device Manager).
Here's what the MSINFO32 report says:

Code:

Maxtor&1394_Storage_Front_Panel*    1394\MAXTOR&1394_STORAGE_FRONT_PANEL*\0010B92100315C87    De stuurprogramma's voor dit apparaat zijn niet geïnstalleerd.

USB-apparaat voor massaopslag    USB\VID_0DDA&PID_0102\2003-06    Kan dit apparaat niet starten.  
(Integrated Circuit Solution, Inc. All-In-One Card Reader )

Smartcard    SCFILTER\CID_2920006F789000\7&28D44F20&0&ABN_AMRO_E.DENTIFIER2_READER_0_SCFILTER_CID_2920006F789000    De stuurprogramma's voor dit apparaat zijn niet geïnstalleerd.
(Some sort of card reader also)

If that doesn't fix things, then I'd suggest a HDD Diagnostic ( HD Diagnostic ) and a Memory Diagnostic ( Memory Diagnostics ) for starters.

A wide variety of errors. Here's the summary of the last 15 memory dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 21 15:59:48.877 2009 (GMT-5)
System Uptime: 1 days 9:09:21.859
BugCheck D1, {4f444646, 2, 0, fffff88004012cc3}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+ff )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 22 14:19:10.022 2009 (GMT-5)
System Uptime: 0 days 22:16:58.598
BugCheck 1000007E, {ffffffffc000001d, fffffa800a496a42, fffff88002e56788, fffff88002e55fe0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+37bd1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 06:44:48.844 2009 (GMT-5)
System Uptime: 2 days 16:24:10.254
BugCheck 3B, {c0000005, fffff800033945bf, fffff8800c8f7050, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopCloseFile+4f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 28 16:04:59.320 2009 (GMT-5)
System Uptime: 3 days 0:11:57.695
BugCheck A, {fffff800573950ba, 2, 0, fffff800030d3d3e}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+95ac )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 29 13:12:58.654 2009 (GMT-5)
System Uptime: 0 days 0:03:21.231
BugCheck D1, {fffffffffff8a000, 2, 0, fffff88006d927d1}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpIrpMajorRead+37d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 29 13:02:12.922 2009 (GMT-5)
System Uptime: 0 days 20:54:57.760
BugCheck 3B, {c0000005, fffff880010134f3, fffff8800bc97ef0, 0}
Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1b8f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 29 13:08:22.832 2009 (GMT-5)
System Uptime: 0 days 0:04:33.408
BugCheck 24, {1904fb, fffff88003f73028, fffff88003f72880, fffff8000339f95b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCacheSharedSecurityForCreate+b2 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  avgrsa.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct 30 06:53:55.160 2009 (GMT-5)
System Uptime: 0 days 3:36:25.142
BugCheck 3B, {c000001d, fffff800033bdabe, fffff8800b007ed0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupObjectName+8df )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 29 21:37:10.899 2009 (GMT-5)
System Uptime: 0 days 8:22:31.475
BugCheck 9F, {3, fffffa80077e2060, fffff80000b9c518, fffffa800ac4e740}
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : ctaud2k.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 31 17:26:07.338 2009 (GMT-5)
System Uptime: 0 days 10:31:40.914
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {fffffa8009b32010, fffff880049c8220, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 31 06:51:38.508 2009 (GMT-5)
System Uptime: 0 days 23:54:56.490
BugCheck 24, {1904fb, fffff8800cbde4f8, fffff8800cbddd50, fffff880012afb41}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRestartIndexEnumeration+1e1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 31 23:27:28.421 2009 (GMT-5)
System Uptime: 0 days 5:59:34.554
BugCheck BE, {fffff88006d943f6, 800000021eb89121, fffff88003ba6130, b}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+225 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  2 15:29:24.032 2009 (GMT-5)
System Uptime: 0 days 0:25:56.609
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+238 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  2 15:01:38.856 2009 (GMT-5)
System Uptime: 0 days 4:15:31.838
BugCheck FC, {fffff8a000141ec0, 94100001fca40963, fffff88002ffbf70, 0}
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferLists+29 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  2 06:56:59.479 2009 (GMT-5)
System Uptime: 1 days 7:27:22.057
BugCheck D1, {6ec3b3, 2, 1, fffff88001159fe8}
Probably caused by : volsnap.sys ( volsnap!IoGetIoPriorityHint+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe

mambowarrior · Nov 8, 2009

AVG is now from the system, as are the 3 devices. Still some crashes but less often. NTFS.sys crash. Will try new System HDD en repost if that was the solution.

mambowarrior · Nov 13, 2009

Replaced Prime HDD, re-installed Windows7 completely. Still getting bsod on:
BCCode: 3b
& FLTMGR

Roled back Nvidia driver to WDM microsoft Windows 7 driver.

mambowarrior · Nov 16, 2009

Still problems....
0xc0000005
0x50830
0x1904fb
0xffffffffc000001d

and so on.... All new hardware... What can be the issue...???

torrentg · Nov 16, 2009

Possibly this:

secdrv secdrv.SYS Wed Sep 13 09:18:38 2006

Update or uninstall it from system.

And always run the latest or beta NVIDIA driver. Not MS one.

Also, it's good to install latest chipset drivers - http://downloads.guru3d.com/Mainboard-drivers---NVIDIA_c19.html

mambowarrior · Nov 17, 2009

Hi torrentg,

Thanks for your add.. Unfortunaly it's still not working.
This is what i've done:

Reinstalled Win7 x64 (today again)
Runned only windows update (1 crash)
Updated hardware drivers (Nvidia Beta/creative/realtek/Asus/Intel) few crashes while installing
No bad hardware in Device Manager anymore...
Installing or having the PC standing by makes it sometimes crash... out of nothing...
Switched the 4x2GB memory from location.
Checked clocking of Asus, is set to automatic.

All errors in eventlog point to 41 kernel power error...

Herewith my newest dumps and systeminfo. I'm getting crazy and a lot of headacke!!!

torrentg · Nov 17, 2009

Alright. Without getting too complicated for the moment at least, I saw something that suggests a new bios update will do good.

So do yourself a favor and install the latest bios from 8/14/2009 here.

Post back and let us know how it goes after. Upload a new dump if bsod happens after doing this.

mambowarrior · Nov 20, 2009

Won't believe it that a Biosupdate just for a Keyboard fix, stops all errors and had only one crash after the installment...2 days up now... thank you so much!!!

mambowarrior · Nov 20, 2009

Crashes happen with copy command. (moving my music from one disk to the other, new one)

torrentg · Nov 20, 2009

Run chkdsk /r C:

from an elevated command prompt for each partition on the pc. Change C to match partition letter(s).

Then when finished, update the video driver to the latest from NVIDIA's site.

mambowarrior · Nov 21, 2009

It has already installed the latest driver. 191.07 is WHQL and i have the newest Beta 195.55 which was advised... running CHCKDSK now...

mambowarrior · Nov 25, 2009

Rolled back Nvidia driver to 191.07, still crashes... see the dumpfiles...
I get the crashes for instance when surfing, or moving files from one disk to another.
CHKSDK on all disks was performed, no errors.

Removed Creative Audio Soundcard, and using onboard soundcard now. Trying that option for now to rule out errors from that side. Only old ellement in the PC is one Harddisk on IDE...rest is new.

mambowarrior · Nov 25, 2009

Didn't work eather.... I'm now running again MEMtest86+ tot see if memory has errors. What i noticed, that SPD informations Display: 4x 2048 MB DDR2-400 memory installed, but when i check with the ASUS site, it says that the mainboard is :4 x DIMM, Max. 16 GB, DDR2 1066/800/667 Non-ECC,Un-buffered Memory
Dual Channel memory architecture

So maybe stupid question, but did they sold me the wrong memory?? And is that what is causing these problems??

mambowarrior · Nov 25, 2009

Memtest is reporting problems!! Didn't do so first time and second time... strange...
On the memory banks is written DDR2/800... so who's right???

john59 · Nov 25, 2009

Have a look here, this may be of some help.

http://www.sevenforums.com/crashes-debugging/41775-windows-7-crashing-sudden-shutdowns.html

John

pressenter · Aug 16, 2010

Hello,

i encountered lately the same problem, Win7, after working a few months properly, started crashing, very VERY often. Below is the latest minidump.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081610-17862-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
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`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Mon Aug 16 18:26:08.905 2010 (GMT+2)
System Uptime: 0 days 0:21:58.746
*********************************************************************
* 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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {190, 2, 0, fffff80002cd5edb}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+79edb )

Followup: MachineOwner
---------

0: 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: 0000000000000190, 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: fffff80002cd5edb, address which referenced memory

Debugging Details:
------------------

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c5c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000190 

CURRENT_IRQL:  0

FAULTING_IP: 
nt+79edb
fffff800`02cd5edb 66453b9080010000 cmp     r10w,word ptr [r8+180h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff80002ccd469 to fffff80002ccdf00

STACK_TEXT:  
fffff880`082c56e8 fffff800`02ccd469 : 00000000`0000000a 00000000`00000190 00000000`00000002 00000000`00000000 : nt+0x71f00
fffff880`082c56f0 00000000`0000000a : 00000000`00000190 00000000`00000002 00000000`00000000 fffff800`02cd5edb : nt+0x71469
fffff880`082c56f8 00000000`00000190 : 00000000`00000002 00000000`00000000 fffff800`02cd5edb 00000000`00000001 : 0xa
fffff880`082c5700 00000000`00000002 : 00000000`00000000 fffff800`02cd5edb 00000000`00000001 00000000`00000000 : 0x190
fffff880`082c5708 00000000`00000000 : fffff800`02cd5edb 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt+79edb
fffff800`02cd5edb 66453b9080010000 cmp     r10w,word ptr [r8+180h]

SYMBOL_NAME:  nt+79edb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

0: kd> lmvm nt
start             end                 module name
fffff800`02c5c000 fffff800`03239000   nt         (no symbols)           
    Loaded symbol image file: ntoskrnl.exe
    Image path: \SystemRoot\system32\ntoskrnl.exe
    Image name: ntoskrnl.exe
    Timestamp:        Tue Jul 14 01:40:48 2009 (4A5BC600)
    CheckSum:         0054B487
    ImageSize:        005DD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I run a q6600 with 8GB of ram, an geforce 8600gt on gigabyte GA-N650SLI-DS4L motherboard. Checked my memory and hdd, and found absolutely nothing. I would be very grateful if you guys could help.

Take care
Simon.

Random crashes

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer