Windows 7 BSOD Freshly installed windows 7 - Random

[blacklotuss]

Hello all,

I have just installed my new SSD Drive and reinstalled Windows, my PC is a bit older but have yet to receive a BSOD on this one. Tried without the SDD drive and installed Windows again on my old drive but still happening, and I cannot get what is wrong. The BSOD happens randomly. The thing I most likely blame is either the USB drivers or the Graphic card drivers. Why? The USB drivers for some reason fail to install (never had this problem before), every time I turn on the PC it tells me that the drivers aren't installed properly but when I check the device manager the drivers are there (from Microsoft) and all the USB ports work without a problem, if I try to install the chipset from the official page for my motherboard (Asus P5QD Turbo) Windows block the install due to a lack of signatures (tried with bcdedit /set nointegritychecks ON - didn't help the install goes through but the problem stays the same), the same goes for the newest ATI Catalyst software so I had to "downgrade to 12.6" instead of using 13.9 downloaded from the official source. For some reason I cannot run Rammon, in the pictures. Any input from you guys is appreciated.

Added the USB screenshots

Cheers and thank you.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, eeb0c2, bb0c2, bb0c1}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+625f )

Followup: MachineOwner

Hi,
the above bugcheck is created when the gpu tries to directly interact with system memory. After completing what it wanted to do it notifies the driver but the information is incorrect and so the BSOD is tripped. This is usually down to either hardware or the gpu driver.

Just going back to the SSD though, are you running in ACHI mode? If not boot into bios and change over but before you do make sure it's enabled in windows otherwise you may start crashing. See this guide on how:
http://forums.guru3d.com/showthread.php?t=313676

You do have some very old drivers running and possible BSOD culprits too:

ASACPI.sys Mon Mar 28 03:30:36 2005: Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). There is a 2009 version on the support page under Utilities:
http://www.asus.com/uk/Motherboards/P5QD_Turbo/HelpDesk_Download/

L1E62x64.sys Thu Jun 11 07:45:22 2009: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller. A 2010 version of this driver can be found here:
Link Removed

I couldn't see an Audio driver but basically your chip is a Via 1708S and the most recent drivers are here:
Link Removed

Please run the Intel driver update utility:
Link Removed

You also have an eSATA port which is covered by this driver:
http://www.techspot.com/drivers/driver/file/information/17342/

Regarding your mention of USB drivers not installing. I couldn't find any USB drivers related to your system and I presume these are taken care of by the Intel chipset drivers as all your USB ports are USB 2.0 only. If your information differs from what I've written here then please let me know..

Test your gpu vram using this app:
Link Removed

Test using the burn-in stress test to check stability:
http://www.ozone3d.net/benchmarks/fur/
If the gpu fails in either test then it might have an issue.

Try removing the old GPU driver using this application:
Link Removed

Here is the GPU legacy driver for your system. Right click it first and 'run as admin':
Link Removed

Ok see how you go with the above and post if you get any new dump files or updates

 

[blacklotuss]

Hello thank you for your quick reply!

OK just going to do a check-list really quick:

ACHI mode - DONE
ASACPI.sys - Updated
L1E62x64.sys - Updated
Audio - Updated
Intel: The application does not find anything. I know this is going to sound annoying but what exactly am I looking for maybe I can find it manually since the automatic does not find anything. I'm guessing this is supposed to be the chipset driver but once again I get the unsigned problem.
eSata - Updated
GPU test - Done, no problems/crashes
GPU Drivers - now here comes the fun part, no matter what drivers I try to install I always get the message in the pictures above except the 12.6 version of ATI's legacy Drivers. I'm about to test the bcdedit /set nointegritychecks ON gig, hopefully it'll do the job shall write back later.

Any ideas what is up with the unsigned driver problems? I've always installed drivers from the ASUS homepage but never had this problem the same goes for ATI.

If you need any help translating the error messages in the pictures let me know, since they are all in Slovene.

 

[kemical]

Have you tried this:
http://www.wintips.org/how-to-fix-w...ure-for-this-file-error-in-windows-8-7-vista/
If the above still doesn't work then read on...
Ok let's try and work this out. I presume that when you were originally running this system with a normal HDD you didn't have this issue regarding the unsigned drivers?

If that's the case did the unsigned driver issue begin with the installation of the SSD? If it did I'd try re-installing Windows now you've changed the settings over to ACHI but make sure your doing a clean install.

 

[blacklotuss]

Ok so I needed to do both in order to get this working again.

bcdedit /set nointegritychecks ON
bcdedit /set testsigning on

Installed the 13.9 version of ATI everything works. I've also found out why the Intel utility doesn't find anything mine Intel is series 5 3400 and the lowest that is in the DB is series 6. Googled around a bit found out that ATI didn't sing the new drivers and was having problems due to that, for now no BSOD so for now I thank you!

P.S. Thank you also for the ACHI tip, works like a charm!

 

[kemical]

Thanks for letting me know and best of luck. You can always post back if need be.

 

[blacklotuss]

Well I'm back... :/ May I ask of you to check again?

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, bbde1, 2, 9d95c}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner

Hi,
The above can caused by either an issue with a driver or the memory. Looking through your driver stack I can see you've updated the drivers recommended above so it could be some faulty memory (could be why RAMMON wouldn't run). Now Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page I linked to you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

 

[blacklotuss]

Hi! Did not need to run it for 12hr but for about 1min replaced the bad stick now hoping for the best. May I ask where do you find these Bugchecks sot hat I need not bother you next time?

Cheers

 

[kemical]

Thanks for updating and I'm glad you got the culprit so easy sometimes it can be a bit of a marathon. You can find a list of Bugchecks below but seeing the bsod Bugcheck is only half the story. Sometimes the issue is trying to determine what caused the Bugcheck as they are not always so cut and dried as the one you posted. This is why we need to read the actual dump file to see what else occurred. Don't worry about posting in as it's never a bother when it's a genuine case. Here's the list:
http://msdn.microsoft.com/en-us/library/windows/hardware/hh994433(v=vs.85).aspx