Solved Random BSOD

[samvel]

I have been having crashes randomly while using my own built machine with Windows 7 64bit Ptofessional.
. I have re-installed the drivers for my video card and display adapter, but the crashes continue. i run (who crashed) and got this
On Thu 08/03/2012 2:04:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003DFEE40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
I am in midle of my life time project(editing videos in Adobe CS5.5)
Any help would be greatly appreciated.
Attachinig files as prescribe.
Thank you.
Sam.

 

[Vir Gnarus]

Got some nasty I/O problems going on. You'll want to do a couple things before running some hardware tests. First, do an SFC Scan, followed by a CHKDSK (after SFC scan is done, in the recovery console you typed it in, type in chkdsk /r ).


Once you're done doing those two, now you can do some hardware tests. First, before you do so, if you have anything overclocked, reset everything to factory defaults. Now, run Memtest86+ for 7+ passes. Then, follow up with Prime95 on Torture Test with Large FFTs for about 9 hours. Any errors on either one of them shows hardware failure, with Memtest being most likely RAM and Prime95 being most likely CPU.

Upon closer inspection of a couple of your crashdumps, I found that there was a solitary bit getting lost in some of your CPU registers. There's a number of things that can cause this. Aside from overclocking, an overheating CPU can also generate this. Check temperatures with HWInfo with Sensors only option checked, and run two 30-minute log sessions: one during idle, and another during high load (like compressing a video file with Adobe). Send them to us for analysis. Note that a bad motherboard or power supply can also cause this problem. If you skimped out on getting a cheaper brand PSU that only gives you enough wattage for your system, then I wouldn't doubt putting blame on it (PSU price tiers determine reliability, not performance).

 

[samvel]

Thank you Vir for quick response.
Two thing; I have run memtest, and runing now Prime95 as you sugested.
I have been using this same machine for about 2 years and is was running with no problems, no crash ho bsod, and was using Adobe CS4.0. And since i reinstalled win 7 to be able to install Adobe 5.5 i star to have those BSOD crashes,
So my point is i doubt that the problems is caused by hardware,but rather by some drivers or so,but it is only my opinion you would know better.
I have run sfc/scannow many times before posting this thread.
i will atach here it may help you to find the problem.

 

[Vir Gnarus]

SFC did find some corrupt files, but was unable to repair them. There are a number of ways to resolve this, but pretty much the easiest is to do a repair install of Windows. Everything will be retained (programs & features). Only a couple of minor settings will be lost. The article explaining how to do this is located here.

There's a couple of BSODs that are pretty much hardware-related only. I would highly doubt a driver is at work here. It may merely be coincidence that after you reinstalled Windows 7 that these started popping up. The solitary bit lost in the CPU registers almost always is caused by hardware malfunctioning. The only exception is a very rare software bug, and while it makes software possible, it is very highly improbable. It still does not jive with the rest of the data that assumes hardware problems.

Go ahead and provide the HWInfo logs as previously instructed. In addition, run all basic tests with Seatools on your drives.

 

[writhziden]

If you would like to rule out possible software/driver conflicts, you do have some possible out of date drivers:

e1y60x64	fffff880`04224000	fffff880`0426d000	Mon Aug 18 15:45:05 2008 (48a9ed61)	00051f0f		e1y60x64.sys
iaStorV	fffff880`0106d000	fffff880`0118b000	Wed Apr 08 10:57:17 2009 (49dcd76d)	0006a88e		iaStorV.sys
dump_iaStorV	fffff880`02c8e000	fffff880`02dac000	Wed Apr 08 10:57:17 2009 (49dcd76d)	0006a88e		dump_iaStorV.sys

All are Intel related or Windows update related and can be updated with the Intel® Driver Update Utility


I would also recommend installing all Windows updates.

 

[samvel]

Thanks Writhziden,
It is realy frustrating, can not install Intel® Driver Update Utility,can not install SP1,
end subsequently no dotNetFx40_Full_x86_x64 and no SeaTools for Windows, nor HWinfo.
I am lost here,do not know what to do.
I run Prime 95 for about 10 hours no errors.chkdsk no errors.3 times sfc
Is any other way to check hardware failure,errors?
Thank you.

 

[samvel]

Forgot to mention never OC never altered any of components.
PSU Model is Antec 650w NP seems to be sufficient ?

 

[writhziden]

How do I reset Windows Update components? may help with Windows updates.

Given the SFC errors and not being able to install applications, I would agree with Vir Gnarus that you should do a repair install. There is a link in post #4 regarding how to do so.

 

[samvel]

Thanks, I will do eventualy repair install (i did before) bat i was thinking if it is indeed hardware malfunc. how to find which one it is ?

 

[writhziden]

The tests given by Vir Gnarus are a good start. How many passes did you run memtest86+? What were the results?

 

[samvel]

It is runing right now for about 2nd run
I will post the results after 7 runs.
Thank you

 

[samvel]

This is a first time that i am runing memtest,so i am not sure what to look and where to look as the results any help?

 

[writhziden]

Next to the number of passes is the errors number. If you see any red on the screen, that means errors have been found. If the screen has no red, the RAM is likely good. Also keep an eye on the errors count, though. It should remain at 0 if the RAM is not defective or damaged.

 

[samvel]

Here is some screen shots, can you analize this numbers please?
Looks like i have bad rams after all.
Thank you very mutch.

 

[writhziden]

Follow part 3 of the SevenForums Memtest86+ tutorial to determine which module/slot is bad.

 

[samvel]

Thanks, i will do that.

 

[writhziden]

Keep us updated on how the system responds to the RAM/slot testing. Make sure to Avoid Static Damage to Your PC. Best of luck.

 

[samvel]

It is end up that one memory stick has gone bad over 2 years,so i took it out and runing now with 2 sticks only in stead of 4.
Ordered two new ones (they are very inexpensive now),i will let the system run till tomorow and see if any crash or BSOD. i will post if any changes.
Thank you for your help it is very mutch appreciated.

 

[samvel]

Hi, is it possible to fix these files without doing clean repair?
I don not know if i even need them,last sfc came with this errors.
Mostly iscsi_init.CHM, and machine.config.comments of NetFx-MACHINE_CONFIG_OCM.
Thanks

 

[writhziden]

The best way to fix the errors is to replace the corrupted files using a Windows 7 install disc or to do a repair install. If you would like to attempt to replace the corrupted Windows files, see OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html and then once the files have been replaced, reboot your computer and run sfc /scannow to verify all corruptions have been repaired.