New
#11
Preliminary results:
SMART Scan: Passed
Short DST: Passed
Short Generic: Pass
Preliminary results:
SMART Scan: Passed
Short DST: Passed
Short Generic: Pass
Just got back to an message re the long time taken by the long scan (due to large HD size etc).
It looks like the test has finished, but incomplete (no abort option).
The test is not finished. It will be finished only when the blue bar is complete.
Long generic takes a long time. The windows version takes longer time if it detects any bad sectors etc.
I will suggest you to leave the program on running for a few more hours.
OK, the long test finished (passed). The error doesn't occur EVERY time, but it does still happen a lot (a recent resume from a very short sleep resulted in BSOD)
In that case, dont let the disc to go to sleep.
Follow Power Plan Settings - Change .... when you are on step 5 (B), set the Hard Disc sleep time to zero, it will convert to never automatically when you save the settings.
Is this just guesswork?
You do understand that I'm choosing to send my laptop to sleep (when going between rooms and power supplies, when saving power etc), and that this is a feature I would like to continue to use, albeit withhout having to restart from fatal errors {almost} every time, on almost all virtual builds on the same hard drive of the same laptop running the same OS..
Happy to try this, but don't see how it'll affect the issue at hand.
Monitoring...
OK, so I changed the advanced power settings, as advised, but the OS fell over at the first resume from sleep.
Does anyone know how to interpret a memory stack dump? I've installed the debugging app but don't know what I'm looking at.
Back to driver / software candidates for system instability ...
I have a hotfix folder, on my old build (that I'm currently using, that does NOT appear to fall over when resuming from sleep). I'm wondering if one of these is the key (or even if it's reg-related - lots of things were tried over time to resolve various erroneous events
ie
"L:\!ARCHIVE\OS\Fixes\windows6.1-KB976932-X64.exe"
and
Reluctant to run willy-nilly after I burned my self last time!
Here's the list of installed updates on the good OS
I had thought, "if I put SP1 on then maybe that'll fix it"... but then read users having the issue since installing Service Pack 1...
I've ended up turning on windows update as well as installing service pack 1 on almost all builds.. but that hasn't fixed this BSOD.
I think it's Intel / NVIDIA (graphics) and am considering installing Intel RAID drivers as advised here...
Hypothesis: If PC is OK in safe mode, it's "driver related" (driver is not loaded, malfunction not manifested / error not exhibited)...
ERGO (love that word :) if I uninstall the NVIDIA device driver, and have no issue, it's NVIDIA
Similarly for Intel and the device drivers for the graphics card that's also running in the XPS.. and then perhaps back to Intel and NVIDIA...
NB: I had followed the steps excruciatingly outlined, re installing the exact versions of the device drivers in the exact order, to avoid conflicts... Now I'm not sure which drivers are the latest, vs which are the version "recommended by the manufacturer" (Dell).
Lots of variables.
Will update when I decide what I'm gonna try next! (Have lots of builds I can test, and easy to clone them - VHD is very cool... but I fear that THAT is actually the cause!!)
OK, recently inspired by my uncle resolving his BSODs by combofixing, I'm having another stab at this...
A lot of chatter re dick corruption and sfc/chkdsk-fixing. I don't think this is the cause of my issues, cause I am using the same physical disk, but each OS is a VHD on that disk. The only VHD-OS I'm currently certain isn't affected by these is my oldest VHD. It has Service Pack 1, and Windows Updates prompts me for important updates (I install almost all).
The new kids on the block, all clean, free of erroneous installs and over-inflated registry hives, are slim and trim, and responsive... but not reliable (yet!) re "resume from sleep".
So I've just installed Intel's RAID driver, and after two necessary restarts, the software is installed.
It said it had updated the driver, but the drivers don't look new.
I also don't know if it's possible/necessary to update the VHD driver that's in use.
Q1 Is there some software which tells you which drivers should be updated?
Performing sleep (with Intel RAID running) on "CRASH1"
Just snapped the above, noticed the VHD path for C: differs, will compare to others to see if that's a factor.