BSOD along with frozen windows 7 repeatedly!

Rahovart

Member
Joined
Nov 1, 2014
Posts
16
Hello!


For almost 2 weeks now I've been experiencing multiple crashes and BSOD on my PC. I reinstalled windows after trying all I could and after using it for a while it started crashing again.

Please I need help. Dont know what to do anymore.

Thank you!


Windows 7
x64
windows 7 x64
retail version
8 months (hardware)
I reinstalled windows recently

· CPU I7 4770k
· Video Card nvidia gtx 760
· MotherBoard MSI z87 g43 gaming
· Power Supply -
RAIDMAX HYBRID 2 RX-630SS 630W ATX12V V2.2/ EPS12V
Desktop
 

Attachments

Hi,

There are no crash dumps located in your app folder.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
 
Thanks.

CRITICAL_OBJECT_TERMINATION (f4)

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Code:
BugCheck F4, {[COLOR=#ff0000]3[/COLOR], [COLOR=#0000cd]fffffa800e5b7620[/COLOR], fffffa800e5b7900, fffff80002d90db0}

Code:
7: kd> !process [COLOR=#0000cd]fffffa800e5b7620 [/COLOR]3
GetPointerFromAddress: unable to read from fffff80002cbe000
PROCESS fffffa800e5b7620
    SessionId: none  Cid: 0254    Peb: 7fffffd7000  ParentCid: 0240
    DirBase: 3bb7cc000  ObjectTable: fffff8a000de2430  HandleCount: <Data Not Accessible>
    Image: csrss.exe

The critical process that terminated was the Client/Server Runtime Subsystem. Possibly a faulty hard drive, especially since crash dumps were having trouble being generated. Run Chkdsk/Seatools:

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 driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

-- Run all tests EXCEPT: Fix All and anything Advanced.

Regards,

Patrick
 
I am using 3 hardrives at the moment, should I run these test on all of them? or only the one with the OS on it??


Thanks
 
Hmm, this is strange...
I have analysed the five latest dump files. They all have a similar pattern of a null callstack with no exception error.
A Kernel dump file would be our best bet at this point.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

Code:
C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.
 
Well, the only thing I can really recommend is you remove the SSD from the picture and see if Windows works on a regular hard disk. If it does, your SSD is bad.
 
Ok, I'll reinstall windows in my regular hardrive and see if that fixes it.

Thanks a lot Patrick!I'll try it out
 
Have you at any point tried reinstalling Windows on the SSD first to be sure it's not a corruption?
 
I did, fresh reinstall and after a while it would crash again, I even tried with Windows 8 and the same thing happened
 

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

Back
Top