Solved BSOD caused by Illustrator perhaps? Also corrupted certificates

[markdibley]

Hi

I have been trying to fix this for years now. Even took it to a shop, who did the same stress tests I did and it appears stable. Everytime I build this it is stable when I use it. Then I pass it over to my gf who uses it fine for a couple of days, maybe a couple of weeks. And then it BSODs at random times, usually when working with Illustrator.

I have swapped out everything except the memory, cpu and mobo. I have done memstat. THought it was a dodgy usb hub on a monitor for a while, but when we thought it was fixed the BSOD came back and we had to switch back to a very old XP laptop.

Any help would be very grateful.y received.

Oh, and also all certificates fail for absolutely everything on the internet.

 

[markdibley]

Actually, the more I look at this computer the more it looks like it has a serious virus as Essentials isn't running, it won't start, it won't uninstall and I can't install any other anti-virus software. I am going to try to rebuild one more time. But an explanation of why it BSOD'd would be helpful as it does it with every build whether there is a virus or not (I think this came from downloading fonts).

 

[Layback Bear]

Couple of things to try if you like.
http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

If you are clean try this.
http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[markdibley]

Hello again

Thanks Layback Bear. That advice was really useful. I didn't have a virus and the update has fixed the problem of certificates and other things. I hae even managed to configure my speakers/headset properly.

However, I am still curious to know what caused the BSOD. Looking through the logs that I uploaded I was wondering if it was due to a PnP device. My gf uses a Wacom Bamboo tablet and I am wondering if that is the cause.

I believe the drivers for everything is up to date. I tested the Intel ones and updated the graphics driver. The Bamboo driver is up to date.

I also believe that there are the logs of the other BSODs that I have experienced, but I am unsure if there is a pattern between them all.

Thanks again

mark

 

[z3r010]

Most of the BSOD's were caused by a memory management errors, if your BSOD have stopped then fine but if they continue you will need to do some ram testing etc.

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+356c3 )

 

[markdibley]

Hi z3r010

Thanks. I will try the system one more time and see if another BSOD occurs. Each time I swear I will just go back to XP or buy a new computer and scrap this one, but I don't want to give up on it.

I have run memtest86 (sorry - earlier I refered to it as memstat - I work on linux OS) on this machine several times without a single problem. I have also reseated and swapped over the memory sticks. I do know my gf uses maximum memory when working in Illustrator and I have increased the paging file on drive E to 12GB (drive C is an SSD so has no paging file). Is there anything else you can recommend?

Thanks again for pointing me to the memory issue.

Mark

 

[Layback Bear]

Their are many opinions on where page filing should be. I leave mine on the ssd.
For graphic Illustrator more ram would help. Something around 1066 or 1333.
From your motherboard specs.
Support for DDR3 2200+/1800/1600/1333/1066/800 MHz memory modules
CPU specs.
Memory SpecificationsMax Memory Size (dependent on memory type)
16 GBMemory Types
DDR3-1066/1333# of Memory Channels

 

[markdibley]

Well, it was all working fine. Once again I had it running smoothly, shutting down, starting up, no BSOD, no problems at all.

I passed it over to my gf, who switched it on, it went straight into system recovery and says that Windows on F: (it was on C is unrepairable.

It's enough to make me cry to be honest.

I will try the repair install again. It wouldn't work from the USB key that I used before (interestingly, when booting from the USB key the key is treated as a HDD and not a USB-FD. Also, the instructions don't remind you to remove the key, or change the boot order when the machine reboots for the first time after the "update").

However, it does appear that something has happened to the SSD for it to complete lose C: which makes me think that there is nothing reliable in this build.

 

[markdibley]

Well I am junking the machine and buying a new one. I managed to restore the machine to an earlier point, but none of the services are running, every application responds with "The specified procedure could not be found" and apparently Bing desktop (which has never been installed, is corrupted (poor Bing). I couldn't "update" because clicking on setup on a USB key or inserting a disk resulted in "The specified procedure could not be found".

I know I will never buy Gigabyte boards again. I will be returning the Corsair SSD as faulty and Windows 7....I've never found an advantage of it over XP. However, I need a 64bit OS so that I can utilise more than 2GB memory so I will probably go through all of this again in a couple of days time.

I'm going to get Novatech Barebone Bundle - Intel Core i5 3470 and with luck it will be more reliable.

Thanks again for peoples help.

 

[Layback Bear]

I's sorry for your problems. Could you keep us informed on your new build?

 

[markdibley]

Hi Layback Bear

Well, the new build is going well. To my chagrin the board in this new barebones machine is a Gigabyte board, but so far it has been behaving perfectly. I have installed W7HP on the 120GB SSD from the old build (had to do it twice as the first time it put the MBR on the HDD also from the old build). With fresh drivers etc. everything is working very fast and very smoothly.

One modification I have made has been to move the library directories on to the HDD using the instructions from this forum (I figured that there was enough room on the SSD for user system files and it was unlikely writing those files would cause adverse wear given the machine's current usage. However, when the machine was switched on today, in the user directory there were 2 of each of the library folders (My Docs, My Music etc). It looks like the library folders have been recreated on the SSD. Does anyone know why this might have happened or how to prevent it happening again?

Also, I have a large music library on a NAS, but I couldn't get WMP12 to discover this DNLA library. Instead, as I have mapped a drive to the NAS I thought I could simply add the files directly to the WMP library. However, when the machine was switched on today WMP12 spent 10 minutes loading the music all over again. So, is there a trick to getting WMP12 to discover a DNLA service on a NAS (ReadyNAS Duo). Or is there a better way to add files to the library so that they are not reloaded every time the machine is switched on?

Oh, and there is a chance that I might have fixed the original machine. I had 2 (identical) sticks of memory which I thought were in slots 1 and 3, but when I was fitting a temporary HDD (and reseating all the frontpanel cables that had fallen off the board) I noticed that the sticks were actually in slots 2 and 4. Could this cause the BSOD? I am guessing there is a chance that it was (the new rebuild using XP seems ok although it feels slow and I can't get the mic to work). I also noticed the memory settings in the BIOS were set to turbo rather than standard. Something else I wish I had noticed before buying a new machine. Oh well.

Thanks again

Mark

 

[Layback Bear]

Take a look through your old motherboard manual. Most motherboards do have a preference to where to install ram. I recommend when having a problem with a computer set the bios to default. You can always set them to your liking later step at a time and test. I can't help you with moving your music around because I have never done it. Windows Explorer still has many mysteries in my mind. Because your computers are up and working I would recommend marking this thread solved and start a new thread on moving things. You would get a better response by people that have the necessary knowledge in those subjects.
Happy computing.