Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while in Windows, randomly


01 Nov 2013   #1

Windows 7 Ultimate x64
 
 
BSOD while in Windows, randomly

Hey guys I really need some help

First, system specs are as follows (nothing is overclocked, and I constantly monitor my system temperatures so nothing overheats)

CPU: Intel Core i5 4670k
MB: Gigabyte Z87X-UD3H
GPU: MSI nVidia GTX 770 Gaming
RAM: 16GB (4x4) Corsair Vengeance CMZ16GX3M4A1600C9
SSD: OCZ Vector 256GB
PSU: Seasonic M12D 850W
OS: Windows 7 Ultimate x64 SP1 with all Windows Updates installed

Additional hardware, probably not important

Sound card: ASUS Xonar DGX
Keyboard: Logitech G510
Monitor: LG W2453TQ

Now let me tell you how the BSOD's started happening. I was updating graphics drivers for the GTX 770, and was foolish enough thinking that I might use the GeForce Experience to update the drivers automatically. Sure enough it updated them, but something went wrong in the process and it no longer detected my monitor. Had to go into safe mode, uninstall the drivers, and completely deleted them and all nVidia software.

After that I installed 331.40(the version that worked great before) and called it a day. But then the first BSOD happened right as I was about to shut down the PC. Right-clicked on Steam in tray to close and that's when it happened the first time.

1st BSOD was PAGE_FAULT_IN_NON-PAGED_AREA 0x00000050

2nd time was IRQL_NOT_LESS_OR_EQUAL 0x0000000A; this one happened when the computer was idle for about an hour and 20 minutes IIRC.

3rd time it was again PAGE_FAULT_IN_NON-PAGED_AREA 0x00000050; browsing the web with Firefox.

4th and 5th time it was MEMORY_MANAGEMENT 0x0000001a; doing just random stuff in Windows.

I've played a couple of games these past few days since installing the graphics driver again, including Battlefield 4, and never once did it BSOD during a game.

You're probably thinking it's RAM, and I'm inclined to agree with you especially after having updated all drivers just today, only to have a BSOD happen again, but the timing is just odd. The time span from installing the new graphics driver to the first BSOD was maybe 5-6 hours. Is it just my luck or?

Thanks if you managed this far, I uploaded the dump files as per your requirements and hope that you more knowledgeable ones can shed some light on this.

Summary (tl;dr)

- updated nVidia drivers to 331.65 through nVidia GeForce Experience, during the process my monitor couldn't be detected any longer so I reverted back to 331.40(which worked fine since I installed them)
- tried playing BF4 with both driver versions(played on TV via HDMI with new drivers), no BSOD's occurred during gaming
- BSOD's started occuring, explained in detail above
- checked all 4 modules of RAM with Memtest86+, no errors, waited 7 passes to complete(took 17h30m)
- number of BSOD occurences thus far: 6


1. PAGE_FAULT_IN_NON-PAGED_AREA 0x00000050
2. IRQL_NOT_LESS_OR_EQUAL 0x0000000A
3. PAGE_FAULT_IN_NON-PAGED_AREA 0x00000050
4. MEMORY_MANAGEMENT 0x0000001a
5. MEMORY_MANAGEMENT 0x0000001a
6. 0x00000019 (not sure about the code, I wasn't here when it happened)

/summary over

EDIT1: Currently doing memtest86+, left it overnight and it just started its 7th pass, 15 hours and counting. No errors.

EDIT2: Done Memtest all the way, took 17 and a half hours to test all 16GB of RAM and they're, at least according to Memtest, OK. Link to image

Got another BSOD approx. 1 hour and 15 minutes later. This time it was 0x00000019. Reuploading new diagnostic files.



Attached Files
File Type: zip SF_01-11-2013.zip (844.7 KB, 5 views)
File Type: zip SF_02_11_2013.zip (890.1 KB, 2 views)
My System SpecsSystem Spec
.

03 Nov 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
  • Double click to open it.
  • Click this button only:
  • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
I would suggest you to run memtest with MemTest86 V4.3.5. For 8 passes at least. The reason behind that version is version 5 fails to determine issues on some new hardware.

If memtest comes free from errors, 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   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   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   Tip


Let us know the results, with the subsequent crash dumps, if any.
Code:
BugCheck 19, {3, fffffa800c9d7b60, 70fffffa800c9d5b, fffffa800c9d5b61}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Followup: Pool_corruption
-------------------------------------------------------------------
BugCheck 1A, {403, fffff680015b5cd0, 8e900001284de867, fffff680015b58d0}

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

Followup: MachineOwner
-------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, 2afba, 2afbc10055f75}

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

Followup: MachineOwner
---------
My System SpecsSystem Spec
04 Nov 2013   #3

Windows 7 Ultimate x64
 
 

Hey Arc thanks for the reply!

To update on the current situation, I think its fixed now. /knocks on wood

What I did, after last updating the thread on Saturday I pulled out 2 modules of RAM from the PC, and it occurred to me it might be a good idea to scan for viruses/malware. I scanned with Malwarebytes, SuperAntiSpyware and NOD32 and guess what? Malwarebytes found my PC was almost choked on it

Here's the Malwarebytes log for references:
Code:
Malwarebytes Anti-Malware 1.75.0.1300
www.malwarebytes.org

Database version: v2013.11.02.08

Windows 7 Service Pack 1 x64 NTFS
Internet Explorer 10.0.9200.16721
TemplarLord :: TERROR [administrator]

02.11.2013 19:07:20
mbam-log-2013-11-02 (19-07-20).txt

Scan type: Full scan (C:\|)
Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM
Scan options disabled: P2P
Objects scanned: 322955
Time elapsed: 9 minute(s), 22 second(s)

Memory Processes Detected: 0
(No malicious items detected)

Memory Modules Detected: 0
(No malicious items detected)

Registry Keys Detected: 1
HKLM\SOFTWARE\{6791A2F3-FC80-475C-A002-C014AF797E9C} (PUP.Optional.OptimzerPro.A) -> Quarantined and deleted successfully.

Registry Values Detected: 0
(No malicious items detected)

Registry Data Items Detected: 0
(No malicious items detected)

Folders Detected: 0
(No malicious items detected)

Files Detected: 4
C:\Users\TemplarLord\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\Q89D326J\bi_downloader[1].exe (PUP.Optional.Somoto.A) -> Quarantined and deleted successfully.
C:\Users\TemplarLord\AppData\Local\Temp\nsc9B68.tmp (PUP.Optional.Somoto.A) -> Quarantined and deleted successfully.
C:\Users\TemplarLord\AppData\Local\Temp\nshB213.tmp (PUP.Optional.Somoto.A) -> Quarantined and deleted successfully.
C:\Users\TemplarLord\AppData\Local\Temp\OptimizerPro.exe (PUP.Optional.OptimizerPro.A) -> Quarantined and deleted successfully.

(end)
Failed to mention this, I just recently got the new motherboard and the 4670k(2 weeks ago), reinstalled Windows 7 from scratch then and everything was working great until the nVidia driver update. So I'm guessing OptimizerPro was sitting dormant since installing either:

Daemon Tools Lite
KMPlayer

I don't think any other software I have would install this, and since I'm very careful not to install anything I don't need on this machine(I have a separate Windows machine for testing purposes ) I bet one of those 2 did it.

Upon removing said malware, I rebooted the PC and it automatically initiated a chkdsk on drive C: which found a bunch of errors and fixed them. PC rebooted again, but was unable to start, going into Startup Repair automatically where it was able to fix Windows (without using System Restore). Upon entering Windows I purged System Restore files, and again scanned the PC with everything I got.

The end result was, since removing the malware I left the PC on overnight again doing AIDA64 benchmarks and leaving everything open(Firefox, Chrome, music player etc.), it survived until the morning when I ended the benchmark and I've used the PC with no BSOD's for the whole day, uptime was more then 24 hours yesterday evening when I shut it down. Booted it up again today on Monday and it's still working okay after 11 hours+ of uptime. Hope it stays that way

Was it the RAM modules that I removed or was it solely the work of malware? Can't say, though I'm leaning on malware. Will try popping in RAM again this week and will let you know the results.
My System SpecsSystem Spec
.


05 Nov 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Well done! Very well done!!!!

In my best guess (as the RAM is not tested to declare as bad) it is the bunch of malware that was causing the issues.

Now observe the situation for some more time. If you see that the issue is really fixed, mark this thread as solver. Otherwise, if any issue persist, we are here to assist you.
My System SpecsSystem Spec
Reply

 BSOD while in Windows, randomly




Thread Tools



Similar help and support threads for2: BSOD while in Windows, randomly
Thread Forum
BSOD randomly windows 7 64 BSOD Help and Support
BSOD Randomly on a new PC Windows 7 pro 64-bit BSOD Help and Support
Windows 7 - BSOD occurring randomly BSOD Help and Support
windows crashing randomly no bsod? BSOD Help and Support
Windows keeps rebooting randomly, no BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:34 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33