Random BSOD's again, this time instantly when I started Skyrim.

ePeen said:

Was this BSOD experienced after enabling Driver Verifier? If it was, attach the dump file for that BSOD.

To answer your question, in theory Driver Verifier should cause a system to BSOD much more frequently than it regularly would because regularly the faulting driver is not being stressed or accessed at the time, it's a very random process. For example, if your culprit happens to be a program that runs off of start up on the system tray, like a mounting program, or a mouse driver control panel, etc... when Windows loads, it should in theory right there force the BSOD and show the culprit, which it has done for me and others I have helped diagnose in the past plenty of times.

However, some can go a day or so without Driver Verifier forcing a BSOD as it depends on the driver fault itself.

No it wasn't when Driver Verifier was enabled. After my next reboot however, it will be enabled. We will see then.

Alrighty :)

ePeen said:

Alrighty :)

My computer got a BSOD while I were in school, and it did not write a minidump. However it did say in the bluescreen that the cause was "SmartDefragDriver.sys"

It's a defrag program I have installed. So I guess this is the cause then?

Could possibly be, yes. Uninstall it and see.

I don't know anymore. It happened again but it wasn't a BSOD, the screen turned pink (PSOD lol). I immediately suspected hardware failure this time. I checked, and it did write a dump, so I analysed it. The dump also said hardware but I'm not sure anymore. Can a driver cause hardware to crash?

I had played FSX, but it crashed. Then I just watched a youtube video and within seconds, BOOM, pink screen.

May I see the latest dump?

ePeen said:

May I see the latest dump?

Here you go.

Latest dump is a 124 hardware bugcheck.

**Stop all overclocking and return to stock clocks if you're overclocking.

Memtest:

Read the following to test your memory for errors.

Dump for reference:

Code:

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


Loading Dump File [C:\Users\Icarus\Downloads\040712-37830-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a7650
Debug session time: Fri Apr  6 23:54:48.672 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:10.296
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800544b8f8, 0, 0}

Probably caused by : hardware

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

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: 0000000000000000, Machine Check Exception
Arg2: fffffa800544b8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a86f0 fffff800`03324cb9 : fffffa80`0544b8d0 fffffa80`03b7ab60 00000000`00000010 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`03205687 : fffffa80`0544b8d0 fffff800`0327f2b8 fffffa80`03b7ab60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`0316ca35 : fffff800`032e0ac0 00000000`00000001 fffffa80`054d01e0 fffffa80`03b7ab60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`030e9471 : fffff880`011bbe00 fffff800`0316ca10 fffffa80`03b7ab00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`03379f7a : 00000000`00000000 fffffa80`03b7ab60 00000000`00000080 fffffa80`03b67040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`030d09c6 : fffff880`02f63180 fffffa80`03b7ab60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`02e97410 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

I am currently overclocking, and will return to standard clocks then... Thank you.

Will the memtest take long?

EDIT: I'm confused... I installed the Memtest on my 256MB USB stick I had lying around. An error came up saying it won't be able to boot but everything else says it WILL boot...

Don't know. They provide a USB key installer that does everything for you, so there shouldn't be an issue.