Random BSOD extremly often and bios freeze after bsod

mesologgi · 18 Mar 2012

First of all sorry for my bad english. Everyday that i use the pc i have a blue screen. If i use games mostly dota 2 it crashes sooner. The funny thing is after bsod i try to start the pc again but computer freezes at windows logo. Then i have to power off and wait ~ 20 minutes because if i start it sooner it freezes and will never go to windows startup repair. If i wait i will use startup repair and the pc will start until it crash again 10min to even hours its random. I also noticed if after bsod i immediately try to open bios the pc freezes after 2 seconds and cant do nothing. I am pretty sure after the freeze on bios that its a motherboard problem. I cant stand it anymore (happens for months but the last weeks extremely often)so enlighten me whats the problem and if i change something ( maybe buy a new motherboard) the pc will be running smooth again. Parts are old 5 years old motherboard + cpu . Ram and gpu are 2.5 years old.
Windows 7 Amd athlon 64 x2 4200+ Amd 5770 Asus m2n sli deluxe 2x2 gb crucial balistics 4 gb ddr 2
Hd i have used 2 with the same bsod

JMH · 18 Mar 2012

1.Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

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 12th 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 before).

2. Please run the System Update Readiness Tool (SURT) and then update to SP-1

32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

zigzag3143 · 18 Mar 2012

In addition to JMH's suggestions please update these drivers. There are many, many ancient drivers. Including your storage driver, mobo driver, I/O driver,raid driver, etc.

Code:

ASACPI.sys    3/27/2005 10:30:36 PM        
seehcri.sys    1/9/2008 4:41:35 AM       
nvm62x64.sys    10/17/2008 5:01:06 PM       
mcdbus.sys    2/24/2009 6:34:07 AM              
lirsgt.sys    5/17/2009 9:06:57 AM        
atksgt.sys    5/17/2009 9:36:34 AM        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        
amdxata.sys    5/19/2009 1:56:59 PM       
nvraid.sys    5/20/2009 2:39:40 AM        
nvstor.sys    5/20/2009 2:45:37 AM          
AsUpIO.sys    7/5/2009 10:21:38 PM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Jonathan_King · 18 Mar 2012

I'd suspect the problem is with hardware from the looks of the dumps. Only one software cause jumps out at me, and that is Kaspersky. I see you're running an old version:

Code:

kl1.sys         Wed Jun 09 09:34:19 2010 (4C0F985B)
kl2.sys         Wed Jun 09 09:24:47 2010 (4C0F961F)
klif.sys        Fri Oct 01 03:28:56 2010 (4CA58DB8)
klim6.sys       Thu Apr 22 11:07:24 2010 (4BD0662C)
klmouflt.sys    Mon Nov 02 11:26:06 2009 (4AEF081E)

Please update Kaspersky to the latest version; if that's not possible, remove the program entirely and try using the free version of Avast instead.

It's also likely your old network adapter drivers are causing some of the crashes. Install the latest nForce package from here: Drivers - Download NVIDIA Drivers

Code:

nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)

A BIOS update would also be a good idea; download and flash the latest one from here: http://www.asus.com/Motherboards/AMD...luxe/#download

Code:

BiosReleaseDate = 09/19/2007

Most likely, though, RAM is the biggest problem. Run the "Blend" Prime95 test, and also run Memtest86. Here are a couple of tutorials to get you going:

Hardware - Stress Test With Prime95

RAM - Test with Memtest86+

I don't see any evidence of your video card causing and problems, just FYI.

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Mar 17 18:09:41.973 2012 (UTC - 4:00)
System Uptime: 0 days 2:46:08.002
*** ERROR: Module load completed but symbols could not be loaded for tunnel.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_tunnel+b344
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Mar 17 11:51:04.472 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:01.376
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Mar 16 10:56:54.540 2012 (UTC - 4:00)
System Uptime: 0 days 1:43:37.444
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Mar 16 08:30:42.326 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:12.355
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ACPI.sys - 
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Mar 15 17:18:06.164 2012 (UTC - 4:00)
System Uptime: 0 days 0:49:26.068
Probably caused by : win32k.sys ( win32k+2294f8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+2294f8
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Mar 14 19:10:46.973 2012 (UTC - 4:00)
System Uptime: 0 days 1:20:07.002
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+377c9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  LogonUI.exe
FAILURE_BUCKET_ID:  X64_0x3B_klif+377c9
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Mar 14 16:39:58.707 2012 (UTC - 4:00)
System Uptime: 0 days 7:41:09.736
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  steam.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Mar 13 09:41:46.429 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:21.458
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Mar 13 07:44:27.053 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:05.082
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Mar  7 09:57:00.294 2012 (UTC - 4:00)
System Uptime: 0 days 0:35:11.323
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339c8 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339c8
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Mar  7 08:25:40.867 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:21.895
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  chrome.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Mar  5 16:33:28.105 2012 (UTC - 4:00)
System Uptime: 0 days 1:27:31.134
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dllhost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+121
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Mar  5 05:03:23.418 2012 (UTC - 4:00)
System Uptime: 0 days 1:16:02.279
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
BiosReleaseDate = 09/19/2007
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zigzag3143 · 18 Mar 2012

JK

Kaspersky not present in 3/17 or 3/18 crashes. Suspect it have already been removed.

Asacpi.sys (2005) present in most recent crash.

Jonathan_King · 18 Mar 2012

Ah, my bad, you're right. Thank you.

@ mesologgi: Carry on with the rest of the instructions, including the network adapter update. The most critical parts are the BIOS update and the RAM check, however.

zigzag3143 · 18 Mar 2012

Thanks for the backup.

mesologgi · 19 Mar 2012

Thanks all for responding. I updated latest nvidia drivers but the baod continyous. I had also removed kaspersky.
10 minutes ago i downloaded latest bios and succesfully upgraded bios but now cant log in windows
Cause i have bluescreen saying stop 0x0000000D1
nvstor.sys
I know system is old but i want to give it to my little brother because i will buy a new soon
And i want it to run with no problems. after this bsod cant run memtest.
How can i pass this bsod and boot the pc ?

zigzag3143 · 19 Mar 2012

mesologgi said:

Thanks all for responding. I updated latest nvidia drivers but the baod continyous. I had also removed kaspersky.
10 minutes ago i downloaded latest bios and succesfully upgraded bios but now cant log in windows
Cause i have bluescreen saying stop 0x0000000D1
nvstor.sys
I know system is old but i want to give it to my little brother because i will buy a new soon
And i want it to run with no problems. after this bsod cant run memtest.
How can i pass this bsod and boot the pc ?

Nvstor is you HD controller driver.

Can you boot into safe mode, or boot from the win 7 dvd?

mesologgi · 19 Mar 2012

Ok some update. I tried entering
Bios to load defaults because of blue screen but it freeze at entering setup
So i thought the hard drive had some problem so i disconnected it but bios froze again.
Then i disconnected 1 ram stick and no problem and now pc enters windows repair mode without blue screen so i think its ok

Does that mean that ram stick was the cause of bsod and needs replacement ? I ll also run the memory test tomorrow.