Search results for query: *

Hi, I'm a newbie to using SAS (almost a full week now woo-hoo lol) although used SQL Server for several years. I was curious if anybody knew of a tool similar to "SQL Search", which I love, for SAS? If you're not familiar with SQL Search it allows you to search database-wide on all objects for...

LMAO I know huh! I actually do like to figure things out though...but even I have my cutoff point.

gonna borrow a PSU and if that doesn't help then maybe reseat the CPU...not much else to try after that. Took the battery & video card out and put back in.

Currently trying to bring my system back from the dead; swapped RAM and got "SYSTEM FAILED CPU TEST" and still getting it after putting my original RAM back in...arghh

I will do that...classpnp.sys shows the same date/version and no not overclocking. Thx for sticking with me.

I see "memory corruption" in there so hopefully it's just RAM; still haven't had time to get to that yet

let me know if you'd like more; not sure why the first one pasted 3x

Loading Dump File [c:\Windows\MiniDump\Mini020913-03.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\i386' Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: c:\i386 Windows XP...

Loading Dump File [c:\Windows\MiniDump\Mini021713-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\i386' Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: c:\i386 Windows XP...

Apologies! Forget you said to run it from the command line originally...here are the last few dumps: Loading Dump File [c:\Windows\MiniDump\Mini021813-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\i386' Symbol search path is...

Mini020913-01.dmp kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * *...

Mini020913-02.dmp kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * *...

Mini020913-03.dmp kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * *...

Mini021713-01.dmp kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * *...

Finally got .NET Framework figured out and debugging tools installed; here's the !analyze from last few dumps: Mini021813-01.dmp kd> !analyze -v ******************************************************************************* *...

Latest update: Tried the new drive in Safe Mode, still crashed Got RAM from friend just need to actually swap it now I installed turbotax and that reqd .NET Framework so hopefully I can now install the debugging tools I borrowed a USB3.0 32gb jumpdrive from a friend and that worked fine

OK so is BIOS a 'safer' way meaning less chance of screwing myself for drivers? Memtest86+ is what I used but I'm still gonna start with swapping out RAM to rule out a false negative.

RAM tested ok but I checked it with 2 sticks in and it seems you're only supposed to do one at a time...so just swapping it will be easiest at this point. Good idea with the drivers, I didn't realize you can just load one at a time. I'll read up on Autoruns and try it out if the RAM is fine. thx

Before wasting more of your time (which I'm grateful for the help) and installing anything else on my computer let me try swapping out the RAM and ruling that out. Should get to that this weekend.

No I'm willing if you can point me to the correct installation of .NET Framework for XP 32bit