Solved Random Crashes Home-build

[toranaboy]

Memtest86 run 42 passes without failure. Assistance required with identifying the source of random crashes on my home build Core i3. I have uploaded an SF Diagnostic results file and a Speccy output.

I would be grateful for any pointers.

Thanks in advance.


Jimmy

 

[Arc]

Bugcheck codes are as always, D1 and 1A. The failing modules are ASMedia SATA drivers and intel HD geaphics driver.

Update the Intel HD Graphics Driver, either from our forum link, http://www.sevenforums.com/graphic-...-graphics-driver-windows-7-a.html#post2166304, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Install ASMedia SATA3 Driver ver:1340 dated 10/25/2012 from ASRock > Products > Motherboard > B75 Pro3-M > Download.

Let us know the results.
_________________________________________________________________________

[COLOR=Red]BugCheck D1[/COLOR], {1, 2, 8, 1}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
-------------------------------------------------------------------------------
[COLOR=Red]BugCheck 1A[/COLOR], {41790, fffffa80025bf0f0, ffff, 0}

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

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

 

[toranaboy]

Further trouble after driver update

Hi Arc,
I know you won't be offended if I say that I was hoping never to contact you again But here I am I have upgraded my younger son's pc: Motherboard, RAM, CPU. When it crashed I pulled out the display adapter to exclude it as the culprit. I have followed your advice and updated the drivers you referred to. I have checked them again before uploading the crash info herewith. It's taking a while because I don't live at the site of the installation his mother's place, but it isn't far away.

You might recall that I gave up on my own machine and tossed the mobo in the end. I haven't had any trouble with it since (apart from UEFI BIOS weirdness about which I will not speak). After all, it's basically a different computer.

Thank you for your kind attention to my woes.

Jim

 

[Arc]

(apart from UEFI BIOS weirdness about which I will not speak)

Lol ... been there, done that

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

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

This time it is another different bugcheck code .... BugCheck BE; ATTEMPTED_WRITE_TO_READONLY_MEMORY. But it is not displaying any more hint about the issue, other than some storage malfunction. Hope you have updated the Asmedia AHCI driver properly.

Now Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest results no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[toranaboy]

After a looo-ong delay I can say I am confident that having changed operating systems (!!) and cooling solutions it must be a hardware snafu. The cpu was certainly o/heating according to the linux reporting Fixed that. Heaven knows what will happen next. Windows 7 will not have been responsible nosiree And now my windows 7 box is freezing on me. Dear me. It's a never-ending battle.

Hope you're wel Arc.

ttfn

 

[Arc]

Thanks mate, I am fine, hope the same for you too

And, frankly speaking, I would have been very happy if I could come to know that your issue is really over!

 

[toranaboy]

Life may one day be over, but never one's issues Thanks again.