BSOD & System instability

[Zarakiel]

Hi everyone,

I bought a new computer and, since the first day, experiencing BSOD and application crashes.


Here is the config :

MoBo Asus P7P55 LX
Proc Intel Core i5 750
RAM 2x2Go Corsair XMS3 1600 9-9-9-24
GC ATI Radeon HD 4870
HDD System Intel SSD X25-V 40Go
HDD Data Western Digital 500Go 7200RPM
OS Windows Seven 64Bits


The OS is a full retailer and I installed it myself.
Since the first day, I get MEMORY_MANAGEMENT or SYSTEM_SERVICE_EXCEPTION errors during the morning and only Firefox/IE crashes, Kaspersky database corruption, Explorer hangings then.


I already ran 3x MemTest 86+ 4.0 on the first boot of the day (computer cold) with each RAM stick and with no error at all.
I launched tests with OCCT 3.1 and the processor succeed.


Today I ran the BSOD Dump & System File Collection App and a System Health Report : the results are zipped and attached.



If someone could help me, I'd be grateful.

 

[ttran]

Hi and welcome to SF!

Here are something you have to do:
First of all, please remove Kaspersky, they appear to be the reason that crash your system. If you need an alternative program to use while not having Kaspersky, I recommend to try Microsoft security essential, it is known for BSODs free.
Removal tool for Kaspersky Lab products
MSE==>http://www.microsoft.com/security_essentials

Update this driver please:

ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 10th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

BUGCHECK SUMMARY:

BugCheck 3B, {c0000005, fffff9600004aac6, fffff88008661ea0, 0}

Probably caused by : win32k.sys ( win32k+1aac6 )

Followup: MachineOwner
---------
BugCheck 1A, {41790, fffffa80016e9d50, ffff, 0}

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

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff80002ac401b, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KeRemoveQueueEx+15b )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 0, 0, 0}

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

Followup: MachineOwner
---------
PROCESS_NAME:  [B][COLOR=Red]avp.exe[/COLOR][/B] <----Kaspersky
BugCheck 24, {1904fb, fffff880070a8268, fffff880070a7ad0, fffff8800121ae3e}

Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupNtfsMcbEntry+7a )

Followup: MachineOwner
---------

Let us know if you need help

Tuan

 

[Zarakiel]

Thanks for your precise and rapid answer

I've done everything you told me, but actually I had a BSOD this morning, 30 minutes after the boot.

Could it be a hardware problem instead of an OS one ?


Another question : can you explain me how do you analyse the files that I sent you, so that I can do it myself instead of bother you with my crashes ?
What other tool can I use to replace Daemon Tools ?


Thanks a lot

 

[Tews]

Unfortunately, there were no .dmp files... Navigate tp c:/windows/minidump, zip up the .dmp files and attach them to your next post..

 

[Zarakiel]

Oops...

Here you can find the 2 Dump of this morning

 

[ttran]

Have you installed MSE?
Can you please perform system file check please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Check out this article:

KB 980932 "STOP 0x0000003B" Stop error on a computer that is running Windows 7 or Windows Server 2008 R2 when you use some IEEE 1394 devices

Stop code 3B with exception code c000005, which is memory access violation.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.496\080610-9812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a52000 PsLoadedModuleList = 0xfffff800`02c8fe50
Debug session time: Fri Aug  6 12:39:47.694 2010 (UTC + 7:00)
System Uptime: 0 days 0:33:31.099
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000fbbe6, fffff88005d809a0, 0}

Probably caused by : win32k.sys ( win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 )

Followup: MachineOwner
---------

Regard,

Tuan

 

[Zarakiel]

So, I installed Security Essentials, update and scan my system : nothing special was found.

The "SFC /SCANNOW" command say the system fixed some files but others can't be repaired...

I ran a MemTest86+ during the entire afternoon : 7 passes and no errors.


I still have Firefox crashing, explorer freezing and BSOD (zip attached).

Since my PC is new, I think I will bring it where I bought it and asked to replace the MoBo and RAM sticks

 

[ttran]

No, as memtestx86 report no error, It means your ram is fine as well as your mobo slots.
Since window can't fix some file, I would recommend to do http://www.sevenforums.com/tutorials/3413-repair-install.html

Let us know if you need more help

Tuan

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Lulubop]

I have almost the exact set up, and I'm experiencing similar problems.

 

[ttran]

I have almost the exact set up, and I'm experiencing similar problems.

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[Zarakiel]

So, the Driver Verifier made BSOD happen every 15 minutes with these messages :
CACHE_MANAGER
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
BAD_POOL_HEADER

...I desactivate it...


I tried to format my system drive and made a clean Windows install.
The first time, the Seven reinstall crashes during the files decompression part. The second time it went well, but the BSOD still happened.


I still have to try a Repair Install.

 

[ttran]

Please enable driver verifier:

Beyond that, please run Verifier with these settings:
[quote]
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
[code]Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users[/quote]