I keep getting an error saying that the public symbols is not available. I'm on my second BSOD since I've installed RC and I'm not sure what is causing it

Try the free WhoCrashed program, which may reveal the reason for crashing your computer. It is friendlier than the Windows MiniDump reader. Download it from here http://www.resplendence.com/whocrashed and install it. To run it click Analyze, then scroll down to see the error(s). When it is first run, it will download the Windows Debugging package, which is perfectly normal. All minidumps found on the system will be listed.

Thanks for that! I gave it a go - doesn't say a specific file but most likely it's a driver. I'm going to assume it's my Kasperky security app since Windows 7 isn't finding it anyway

Symbols for Win7 are available to Connect and MSDNsubscribers. I wasn't able to locate them on Technet.I've debugged quite a few crash dumps with Win7 without the symbols - what sort of error are you getting?

This is what I got from the windows tool... Opened log file 'c:\debuglog.txt' 2: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols WARNING: Whitespace at end of path element 2: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q 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 ........................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffa80c654bdc0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002a92dcc, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------

I found this also, it's a link to the Windows 7 Beta Symbols that are freely downloadable: http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#dIt seems that there's also some difficulty with your Symbol path. The error message states that there's some whitespace after the symbol address. Try copying the next line exactly and putting it into the debugger...File...Symbol File Path (I use the GUI and have, so far, avoided the command line kd tool). Don't forget to save the workspace afterwards to ensure that the path is saved.SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsI've seen this sort of message before (not only with ntoskrnl.exe) and usually assume that it's due to updates to the OS that haven't made it into the symbol files store yet. It's not an issue usually, but the warning message usually means that Windows thinks that the problem is with that file.Could you post the stuff after the "Debugging Details:" ? That may give us some more clues as to the cause of the problem. If a core Windows file (such as ntoskrnl.exe)is referred toas a problemin a crash dump, it's usually a result of something else (a 3rd party driver) accessing it improperly. So diagnostics first revolve around trying to determine what the driver is.In many cases, a STOP 0x50 error is caused by memory, conflicting programs, or conflicting hardware. I'd suggest running the built in Memory Test first, and follow this with checking all of your software to make sure it's compatible (particularly your antivirus software). - John

Thanks everyone. I think it was Kaspersky. I removed it and I haven't seen a blue screen since. Now running Security Essentials for antivirus :)