Random BSOD, sometimes when playing video

[pilau]

First crash. It happened when I was trying to download CCleaner (from the official website). The whole file was downloaded just before the BSOD was triggered.

It is notable that after restarting, the NOD32 antivirus startup scan was taking a lot longer than normal, utilizing max CPU, even though I deleted the downloaded CCleaner part-file upon logging in.

What steps I should take now, after having a BSOD with driver verifier?

Thank you very much in advance, Tom

 

[writhziden]

Upload the new crash report and we can take a look to see if the crash was due to Verifier and a driver conflict.

 

[pilau]

Attached here are two crashes' worth of dump files. Cheers.

 

[writhziden]

Both related to your network, I believe. uTorrent and firefox were blamed, and given your network crashes previous, I am beginning to conclude you have a network driver issue. Try uninstalling your network adapter drivers through device manager (make sure to tick the box to delete driver software for the device if prompted after hitting uninstall). If you need help with this, here are the steps.

To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

 

[pilau]

Would you advise uninstalling the adapter in Windows, disabling it in the BIOS and then installing a PCI network adapter? Because I have great quality Intel Pro NICs from my job. Or is it the wrong direction to solve this problem?

 

[writhziden]

Try the method I described in my previous post first. If you continue to have problems, you can try the PCI network adapter after uninstalling the other in Windows and disabling it in the BIOS.

 

[pilau]

Okay thank you very much. I really appreciate the time you put into helping me. Cheers.

 

[pilau]

By the way, please have a look at this page by Intel. It says over there that Windows 7 already contains the latest driver for my network interface:
Network Connectivity — A guide to Intel® PRO/100 Network Adapter drivers

 

[writhziden]

By the way, please have a look at this page by Intel. It says over there that Windows 7 already contains the latest driver for my network interface:
Network Connectivity — A guide to Intel® PRO/100 Network Adapter drivers

I understand that you probably have the latest driver already. Even if you have the latest driver already, sometimes drivers get corrupted and need to be installed again to repair the corrupted files. The steps outlined in my previous post guarantee the corrupted files are removed and replaced with working versions.

 

[pilau]

Okay, followed your steps exactly. Of course after restarting Windows automatically installed the Microsoft supplied version of driver - which is the exact same version as of the latest Intel-supplied driver.

I then updated the driver with the one I got from Intel's website. And luckily Windows accepted it.

Now we'll see. I haven't disabled Driver verifier, by the way. Should I keep it running? Or does it removes itself from starting with windows after restarting/updating drivers?

 

[writhziden]

Sorry, forgot you had Verifier running still. Disable it to see if the system remains stable running normally.

 

[pilau]

I will, and then we'll see how everything goes. Cheers.

 

[writhziden]

Best wishes it is stable!

 

[pilau]

Hahha, Murphy is not on our side Guess what happened today? Lol...

Here's the dump file. Do you need anything else?

 

[writhziden]

Loading Dump File [F:\Kingston\BSODDmpFiles\pilau\020512-19859-01\020512-19859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83009000 PsLoadedModuleList = 0x83149230
Debug session time: Sat Feb  4 22:59:21.544 2012 (GMT-7)
System Uptime: 0 days 9:09:16.435
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 864d1024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 1040080f, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
80dca8ac 8341afcd 00000124 00000000 864d1024 nt!KeBugCheckEx+0x1e
80dca8e8 830ccfc4 864d6c31 864d1024 8305ea60 hal!HalBugCheckSystem+0xab
80dca918 8341b27f 864d1ea8 83428e40 00000000 nt!WheaReportHwError+0x230
80dcaa2c 8341b371 864d1ea8 864d1ef8 00000002 hal!HalpMcaReportError+0x3b
80dcaa50 8341b48d 00000000 864d1ef8 00000000 hal!HalpMceHandler+0x8b
80dcaa70 8341b5d6 00000000 864d1ea8 80dcab90 hal!HalpMceHandlerWithRendezvous+0x4b
80dcaa80 834115f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
80dcab90 8340e261 00000000 80dc5750 00000000 hal!HalpMcaExceptionHandler+0x87
80dcab90 00000000 00000000 80dc5750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS

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

This is a hardware stop. See http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html.

 

[pilau]

So this BSOD was in essence different than all the rest?

 

[writhziden]

Yes. This crash points toward hardware problems. It could be drivers, BIOS issues, conflicts, or faulty hardware. That link provides more in depth information about how to determine which it is.

Do the following general hardware diagnostics:

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Check temperatures at idle before doing the following tests and during stress using the following tests.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

 

[pilau]

Yes, I read the link. And will perform all your recommended actions ASAP.

How are the earlier errors different from the last one? If this one pointed to a general hardware issue, did the other point to a software problem? I'm just curious and trying to understand.

 

[writhziden]

The others pointed more toward drivers, but drivers are what interface between the OS and the hardware, so it could have been a hardware problem all along.

 

[pilau]

I had a hunch it was the HW all along. I had experience with these blue screens before in another PC and it was the RAM that was throwing the system off.

How can one learn to identify those BSODs?