Suddenly random BSOD on Windows7

ClassicEnergy

New member
Joined
Dec 1, 2013
Posts
4
http://www.filedropper.com/documents

· OS - Windows 7
· x64
. Original Windows7
· Built the computer myself in november 2012
· 1 year
· 27/11/2012

· Core-i5 3570K
· Radeon HD6950 but I am currently using onboard Intel HD Graphics because while using the 6950 the system crashes immediately while loading desktop
:huh:
· Asrock Z77 Extreme4
. Patriot 8GB DDR3 1866Mhz
· Xigmatek 800W
 
Hi there,

just curious - is there a reason you already have Driver Verifier enabled? If you were already troubleshooting these BSODs somewhere else (that doesn't seem likely though, since there's only one MiniDump file), then it's OK, but if you don't know what it is and why it's enabled - please disable it at least for now, until (if) another BSOD occurs, by running the following command from elevated ("Run as Administrator") command prompt and rebooting your computer afterwards:

Code:
verifier /reset

In addition, there are many things (they might or might not be related to the BSOD) with your system I don't quite like:

  • There's no Service Pack 1 installed. You should get it, as well as all the updates, installed.
  • Daemon Tools by itself is known for causing many issues, but apart from it you also have Virtual Clone Drive too. Having two CD emulation drivers on same system usually asks for problems. Unless you need some specific feature only Daemon Tools provides, I would recommend you removing it and leaving Virtual Clone Drive only and updating it to the most recent version.
  • Are you using XFastRAM (RamDisk) provided by AsRock? If not, I would suggest removing it.
  • The following error in your system log - "The Superfetch service terminated with the following error. The system cannot find the file specified" looks suspicious. Whether you need this service or not, it's still a system service, that should be able to start, instead of failing with "File not found" type of error. That might be indication of some sort of corruption. It's possible that C:\windows\Prefetch folder is corrupted, so you can delete all files from it. In addition, could you please also run the following commands from elevated ("Run as Administrator") command prompt and paste their results here:
    Code:
    SFC /SCANNOW
    Code:
    CHKDSK C:
  • You do not seem to have any antivirus application installed. Could you please download Malware Bytes and do a full scan of C:\ drive to be sure you have no infections?
I will let you know if I found any more details after further investigation of the crash dump.
 
I will disable driver verifier as mentioned

I did not install service pack 1 because my system was running fine without but I will get to installing that

I un-installed daemon tools

No I am not using XFastRAM

I run SFC and CHKDSK and everything was fine

I should mention that even before with the Radeon graphics card the BSOD would specify something with win32k.sys.. I don't know if it has anything to do
 
If you are not using that RAM Disk, please search for "AsRock RAM Disk" in "Add/Remove Programs" list and remove it.

In addition, I see you have AsRock eXtreme Tuner installed. Have you done any overclocking? Maybe you can try launching the utility to see if everything is set on default values and no issues are reported.

Once you complete all the actions discussed, please do the following:

  1. Wait to see if you get another BSOD
  2. If you do, please compress C:\MEMORY.DMP file, upload it and share here
  3. Once the file is uploaded and we are analyzing it, enable Driver Verifier again (following these instructions)
  4. Wait for another BSOD to occur
  5. Once it does, please compress C:\WINDOWS\MEMORY.DMP file, upload it and share here
 
Hi,

The attached DMP file is of the PAGE_FAULT_IN_NONPAGED_AREA (50) bug check.

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

---------------------------------------------------------------------------

It's a verifier enabled dump and is failing to detect a driver in violation which likely indicates hardware issues - DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

You said you removed Daemon Tools above per Tomas' instructions, but after checking the modules list I still see its name but the .sys is not present. Double check to ensure it's gone - C:\Windows\System32\Drivers (look for dtsoftbus01.sys). If it's there, rename it to dtsoftbus01.old.

---------------------------------------------------------------------------

Let's also go ahead and run a Memtest for NO LESS than ~8 passes (several hours) to test the health of your RAM. If you get no errors with Memtest after at least 8 passes, move on to chkdsk and Seatools for testing your hard disk:

Chkdsk:
There are various ways to run Chkdsk~


Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
 
Thanks for all your help Patrick, TomasD. I finally got this sorted. I installed all sp1+updates did all the chkdsk and seagate checks. I decided to remove my Radeon vga and the BSOD stopped occuring. Now I am pretty sure my vga is faulty :(
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top