Showing posts with label Blue Screen of Death. Show all posts
Showing posts with label Blue Screen of Death. Show all posts

23 November, 2014

Printing problem in Crystal Reports for VS2005 - SOLVED!

Crystal Reports
Crystal Reports (Photo credit: Wikipedia)
23-Nov-2014


A week or so ago, I had my old work desktop PC formatted and installed with Windows 7. I opted for that because I don't want any leftovers from previous users cluttering up my work. Say I'm fussy, but that is me. At least I can safely say, if ever the time comes that I leave the company, that they can format the hard disk drive, without ever worrying about 'others' having leftover files in the HDD of the PC that I used for X number of years.

Now, that new Windows 7 OS is sure better than XP Professional SP3, and while I am able to make use of the better hardware and better OS, in that the very reason why I had the Windows 7 installed after a format is that the hardware is better, even when it was running Windows XP. Yap, there was another desktop PC involved. I had a swap. I had the faster PC for a swap, and requested for a total clean sweep of the hard disk, which mandated the installation of Windows 7. I didn't know that, but it was a pleasant surprise - when I was told that due to the formatting of the hard disk, I will now be getting Windows 7 instead of Windows XP. I said, "Err... okay!"

When all applications have been reinstalled back, I discovered that the main software I use in my daily work is getting a problem: it wasn't able to run Crystal Reports, or to be precise, all sections work, except the Crystal Reports form.

When that problem was fixed, a new one came about: printing function. All else, like exporting, viewing pages, etc., work. I was stuck, as again, printing the generated report was a mandatory part of the process flow that I call work.

I asked for help, which didn't easily come. I figure, I had to do it on my own. And that was even harder because I don't have internet access at work. I should say it is hard, but I feel safer and more comfortable, with much ado about wasting time browsing while working, etc., etc. So I do my web seraching at home, then attempt all solutions and resolutions when I come back to the office.

To cut to the chase, here's what I did, and unfortunately, I am not quite sure on the exact item that fixed the problem. And yes, I am using Windows 7 64-bit OS. Sadly, some of the articles that I checked insisted that it has nothing to do with the bit-ness of the OS of the client, or the local PC, but the bit-ness of the server. That is contrary to my experience.

  1. I turned on .NET Framework 3.5 through the Control Panel, Turning Windows features on or off.
  2. I installed ReportViewer.exe
  3. I installed cr_net_2005_x86.msi
  4. I installed CRRedist2005_x86.msi
  5. I installed CRRedist2005_X64.msi

Five items, and I didn't know which one did the fix. So I suggest that if you are following my method, help me out by doing one-by-one, and noting which one does the fix, so I can update my post.

Hope this helps somebody, as it did me.

Till then!

22 August, 2013

BSOD using Vuze

English: New icon for the Vuze client (formerl...
English: New icon for the Vuze client (formerly Azureus); is a departure from old icon (Photo credit: Wikipedia)
22-August-2013


The laptop I am using isn't one that is perfect, and while it may be blazing fast and surprisingly efficient and can withstand my habit of opening many applications in quick successions with 1 or 2 seconds, it still gives me the blank face of blue screen sometimes, and just spurts our numbers and letters that I don't understand.

However, one very consistent behaviour I know is my use of Vuze.

Searching on the error codes would come out with an endless list of posts and articles, and looking at some, there is a consistency that I found. It is the use of Vuze - due to some setting in Windows 7 network usage (limit). And I for one would like to push things to the limit: I would often open up a lot of torrent files, since my internet service plan is unlimited, and fast, I expect that everything else would be the same: unlimited and fast.

Well, some things would comply, but differently: a fast Blue Screen Of Death response, right after I click on Vuze application shortcut.

Like I said, I found out that the cause is the heavy network traffic, which kicks in when Vuze starts up due to the many torrents currently active.

The suggested solution to tweak some settings, disable some checks, turning on some, blah, blah, blah... well, I can't follow. Not to that level.

So what I did was reinstall Vuze. That required uninstalling Vuze first, and deleting the settings, so whatever uploads and downloads are active will be cleared. And of course, I did a backup before that.

After reinstallation, I put back in torrent files, one after another. And each time, I would close Vuze, then open it again after a while. When the BSOD came back, I noted down the number of active torrents, and set the limit to a number lower, to be safe.

Do I still get BSOD when activating Vuze? You bet I do. But at least, I know why now. And that is something within my control.

Sometimes, it is even with no torrent running but with many other resource-heavy applications and programs, activating Vuze will surely throw out a BSOD. So I just make sure that computer has stabilized for some time before I turn Vuze on.

The thing is, you can't have too many torrents active when opening Vuze. I am able to go over the limit when Vuze is already opened and running stable, only that I have to be sure that these torrents will complete by the time I have to shut down my laptop or before I close Vuze. And that, also, is within my control.

Till then!
Enhanced by Zemanta