New version of previous problem

[davecas]

- x86 (32-bit) or x64 ? 64
- the original installed OS on the system? Win7 This one
- an OEM or full retail version? OEM - installed by shop that built it
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 5-6 wks- What is the age of OS installation (have you re-installed the OS?) Same, not reinstalled

Previously I was having BSODs and freeze-ups. I updated the driver ASACPI.sys 2005 as previous recommended. This has fixed the BSODs as I have not had one since then (~2 wks). But I have continued to have random freeze-ups. System just goes static and I need to do a hard reset to get it going again.

I had brought it back to the shop initially and they replaced the RAM (though I got the feeling they could not trace the real source). I have since ran MEMTEST through 11 passes for over 22 hrs and got zero memory errors. I am still getting random freeze-ups. It was fine the past 2 days and just froze again now. The last time, it happened to me 3-4 times in a row within minutes of rebooting.

BIOS is current. Windows is current. The system is not overheating that I can tell and it is not heavily loaded when it freezes. This is very frustrating on a new PC and the shop has not been a great help so far. I will bring it back soon for more work if I cannot find a solution here, but I would rather not lose the PC for a week or more if possible.

Thanks for any help you can offer.

-Dave

 

[davecas]

Since I am not getting much response, I am guessing this may be a bit off the beaten path for this forum. Can anyone at least tell me if there is a better place to ask this question? Is it somehow hardware related (other than the Memtest I already ran that looked fine)?

Thanks,
Dave

 

[davecas]

I'll throw one more wrinkle into this... I got my first BSOD the other night since updating the ASACPI driver. I also had this system built with a dual boot so I could continue using an application that won't work in 7 (needs XP). The past day I've been working in XP, for the first time other than to check it out initially, and now after about 30+ hrs in XP, it froze up on me for the first time in XP.

Since the memory did not throw any errors in 24 hrs and 11 full passes of Memtest, this seems like it may be MB related. Anyone have any clues what to pursue?

Thanks,
Dave

 

[DeanP]

Hi Dave. I am sorry that no one is assisting your problem - we aren't here 24/7.
Your latest dump was way back from November - make sure you configured it correctly to create dump files.

You have some old drivers, update the drivers or uninstall the driver/driver associated with the program.

UsbFltr.sys Mon Apr 09 22:09:44 2007
Ortek USB Keypad Driver - Ortek USB Keypad - Waytech Development, Inc.

DgiVecp.sys Fri Oct 31 16:38:29 2008
Samsung Driver - unable to indentifiy.

To make things easier, can you please fill the system specs? Also, what devices are currently plugged in to your computer (i.e: mouse, keyboard, webcam, etc...)?

If you are having problems, please let me know.

Happy New Year!

DeanP

 

[davecas]

Dean, Thanks for the help. I realize that asking for help on an open forum is a hit or miss proposition as you are asking for free help, but it's always worth a shot, IMHO.

I put in my detailed system specs for you to look over.

I looked into the drivers you noted. I don't think the Samsung one is an issue as the old one was listed for NT, whereas the other OS's listed (Vista, X64, P) were all 3/09 dates. But I went to Samsung and updated my printer driver in any case (assuming it was the printer). Not sure there was a newer version or not as I'm not sure how to find dates on printer drivers (all the other hardware drivers I get how to find it, just not printers).

No idea what the Waytech driver was about. Assuming it was for my generic Dynex multimedia (Best Buy cheapo), I updated the keyboard driver with the newest from MS.

Pretty sure I attached the correct file in the above post, but I just made a new one after those changes to be safe and attached it below. I didn't run Perfmon this time.

As I noted before, if this isn't a simple driver issue, I need to bring it back and have them make it right. This is about the end of the rope, unless you have some magic here. I hate to lose use of it for a week or two, but right now it is very frustrating to use...

Thanks again for your help!

 

[davecas]

Bumpity bump...Any ideas out there?