Solved BSODs in Win7 64-bit; mainly SYSTEM_SERVICE_EXCEPTION (3b)

[jelson]

Just moved... and starting getting lots of BSODs. (Windows 7 Ultimate 64-bit, custom build)

Have done the following:

1. Reseated RAM, cards & connectors to motherboard
2. Ran memtest overnight ===> 7 passes without error
3. Ran "chkdsk" on all partitions ===> no errors found
4. Ran "sfc /VERIFYONLY" ===> "did not find any integrity violations"
5. Pulled 1 stick of RAM and then switched with the other ===> getting BSODs with either stick
6. Scanned machine with Malwarebytes AntiMalware 2 ===> no detections
7. Started running Driver Verifier:Special Pool, Pool Tracking, Force IRQL checking, Deadlock Detection, Security Checks, Miscellaneous Checks & ALL boxes where "Microsoft" IS NOT the Provider
   -----> Upon Reboot, immediate Verifier BSOD on Zemana Antilogger ===> removed Antilogger from startup & unchecked it in Verifier
8. Reset BIOS to default Asus "Optimized" values ===> diminished BSOD frequency
9. Visually inspected motherboard for swollen capacitors ===> none noticed
10. Replaced old Corsair TX-650W PSU with Seasonic G-650W PSU ===> still getting BSODs
11. Ran SFDiagnostic Tool ===> folder not created on desktop but on another drive;
    --> checked registry value for Current_User Desktop ===> correct: %USERPROFILE%\Desktop
    --> in command prompt: "cd \%USERPROFILE%\Desktop" ===> correct: user's Desktop (on C: drive)

Notes:

• Driver Verifier is still running ===> no Verifier BSODs except for mentioned ones with Antilogger.
• Most of the time, the BSOD occurs in a Sandboxie session: watching Netflix in sandboxed Firefox (because that's what I've been doing most of the time.)
• Last summer, experienced some BSODs which seemed to go away after uninstalling Asus AI Suite 2 and upgrading nvidia driver.

Unsure what to try next. Short of replacing hardware, considering a fresh install of Windows

 

[Thedoctor44]

Sandboxie appears to be causing some problems.
Please remove it for the time being.
Then see if the problem persists.

Unable to load image SbieDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SbieDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SbieDrv.sys
Probably caused by : [COLOR="Red"]SbieDrv.sys[/COLOR] ( SbieDrv+136cc )

 

[jelson]

Sandboxie appears to be causing some problems.
Please remove it for the time being.
Then see if the problem persists.

Thanks for the advice!

Disabled Sandboxie's startup entry and set its driver to "Disabled" in Services.

Have a lot of photo work to do today, let's see what happens.

 

[jelson]

After disabling Sandboxie, BSODs persisted. Mostly while in Firefox 28.0 (Also, Firefox was also crashing a lot without causing a BSOD)

However, the system was stable while I spent many hours working in Lightroom 3, Photoshop CS5 and Word 2010 (as long as I wasn't running Firefox)

Since Driver Verifier had been, but analysis of the dumps never showed a Verifier BSOD, I decided to disable Driver Verifier yesterday

Decided to do a clean install of nVidia driver 320.49 (graphics driver & PhysX only)

But I'm still getting some BSODs.

So I've imaged the system drive. After I finish up pending work in the next day or two, I'm planning on restoring a system image from earlier image.

Here's the report with dumps that occurred after a clean reinstall of nvidia drivers

 

[Thedoctor44]

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Can you also switch your dump files to Kernel Memory Dumps by following these instructions.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Afterwards upload the dump file created in C:/Windows/memory.dmp to a program like OneDrive then post the link here.

 

[jelson]

Thanx Thedoctor44

1st, ran the drives' "Short self-test" and "Long self-test" in Hard Drive Sentinel Pro (continuously monitors drive health)
PASSED

Then booted SeaTools:

Ran Short and Long Tests on both the SSD and the data drive ==> PASSED

Changed pagefile size min to RAM size + 100 MB & max to RAM size + 200 MB

no BSODs yet. (Samsung Magician had previously set pagefile size very low: 200 MB - 1000 MB)

Prior to the testing, while in Firefox... got a "notification" that nvidia driver 320.49 had stopped responding and then restarted itself.

Had experienced a couple of display freeze-ups that I had to wait out.

SO...
1). reseated GTX 550 Ti and RAM again.
2). I did a clean install of an earlier nvidia driver: 306.49

... have experienced a Service Exception BSOD since then but that was prior to changing the pagefile size.

As soon as I get a BSOD with large pagefile, I'll let you know.

Begining to suspect the problem is related to the GPU, video drivers and/or instability in system-build

Going to look around for an old nvidia card to slap in to test for GPU problem and also try restoring system to an earlier image.

Again, thanks for the "clue-pons"

 

[Thedoctor44]

No problem
Any more issues let me know.

 

[jelson]

System is a lot more stable now... but something's still amiss.

on Sunday night, got 2 BSODs while watching Netflix in Firefox (only 2 BSODs during the course of watching 3 films.)

• 051814-8767-01 --> KMODE_EXCEPTION_NOT_HANDLED (1e)
• 051914-9110-01 --> PAGE_FAULT_IN_NONPAGED_AREA (50)

2 more on Monday night:
1st while again watching Netflix in Firefox
2nd while running sfc /VERIFY ONLY... Firefox was minimized (Netflix movie paused)

• 051914-8814-01 --> IRQL_NOT_LESS_OR_EQUAL (a)
• 051914-9531-01 --> NTFS_FILE_SYSTEM (24)

After Reboot, without Firefox running, reran sfc /VERIFY ONLY ==> no errors

Attaching the reports (includes text output of Windows Debugger & BlueScreenView for both minidumps and full memory dumps.)

Also have uploaded the 4 full memory dumps (individually zipped up) and will PM the links to Thedoctor44.

 

[Thedoctor44]

[COLOR="Red"]Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xae000[/COLOR]

fffff880`11092000 fffff880`11d86000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Tue Oct 02 19:21:13 2012[/COLOR] (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your display driver is out of date.
Please update it form the Nvidia website.
Alternatively you can follow these instructions.

http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html?filter

 

[jelson]

Thanks. And just to be sure, followed the procedures in the link above and installed 335.23

I'll give it a workout today and report if problems still occur

 

[jelson]

another BSOD, but only 1 so far: 052114-9001-0 PAGE_FAULT_IN_NONPAGED_AREA (50)

• uninstall and then clean install of latest nVidia driver (335.23)
• uninstall and then reinstall latest version:
  • Silverlight
  • Flash Player
  • Firefox

1. BSOD while watching Netflix in Firefox (after ~30 min, after reboot was able to watch the rest)

Report attached as usual and link to full memory dump (052114-9001-0) to Thedoctor44

P.S. ran FurMark 1.13 (15 min Benchmark) without any problem

 

[Thedoctor44]

The dump file you linked to on your google drive is way too large.
A Complete Memory Dump is massive.
I can try and download it but it'll take a while.

EDIT: The dump file was corrupt.
Bad RAM can cause this.

In the meantime I suggest memtest86.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Can you also change your dump file setting to Kernel Memory Dump.
Follow these instructions.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[jelson]

True... the full dump weighs in @ 8 GB and have been zipping down to 1 - 2 GB

No problem, changed to Kernel Memory Dump

I'll start the memtest now. 8+ passes is going to take awhile. Let you know tomorrow. Thanks for the help.

 

[jelson]

Ran memtest for 30 hrs, 13½ passes completed without any errors.

 

[jelson]

[lots of good advice]

I thought I should post an update.

Short version: it was the RAM.

Interesting note (might be handy since a lot of G.Skill DDR3 and AMD CPUs are bought by enthusiasts):

• I stumbled on a sticky at the G.Skill forum addressing the problem experienced if you have 1600 MHz DDR3 with AMD Phenom II CPUs.
• Have to set the timings and DRAM Voltage manually and most of the time boost the CPU-NB voltage by +0.10V
• This is due to the Phenom II CPUs internally be designed to support up to 1333 MHz DDR3; auto settings tend to result in slight system instability.

Here's the link: AMD CPU + G.Skill DDR3-1600 - G.SKILL TECH FORUM

Long story short:

1. Following the advice of G.Skill tech support resulted in much less frequent BSODs (again varying stop codes.)
2. BUT about 2 weeks ago, my machine wouldn't boot.
3. Tried 1 stick at a time and found that 1 would boot and the other wouldn't.
4. Bought a used Micron 4GB 1600 MHz stick and it booted right up and has been running totally stable for 2 full weeks (~ 120-150 hrs) at 1600 MHz with its specified timings set manually

Thanks again for all your help Thedoctor44; currently have sent in a RMA request to G.Skill