BSOD, stuck or restart on idle

[djolegaf]

Hi everyone.
Since past couple of days I have started to have BSOD, spontan restart or computer stuck when it is on idle, mostly as soon as it finish some hard job (3D modeling, etc.). I have tried stress CPU with Prime95, RAM with memtest86+ and GPU with Furmark, and everything passed OK, with no BSOD, restart or any other problem. There is two types of BSOD: 0x00000a and 0x(few zeros)124. Computer is not overclocked. Thanks in advance for help!

 

[essenbe]

djolegaf, There is really not much to go on in your dump files

lmvm DKTLFSMF
start             end                 module name
fffff880`010f0000 fffff880`01112000   DKTLFSMF T (no symbols)           
    Loaded symbol image file: DKTLFSMF.sys
    Image path: \SystemRoot\system32\drivers\DKTLFSMF.sys
    Image name: DKTLFSMF.sys
    Timestamp:        [COLOR=red]Mon Jul 09 16:54:13 2012[/COLOR] (4FFB5305)
    CheckSum:         00026261
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This is a driver from Diskkeeper You can update the Driver from Product Updates and Patches | Diskeeper & Undelete

Also

[COLOR=red]MEMORY_MANAGEMENT[/COLOR] (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
 Parameter 2 contains the referenced virtual address.
Arg2: 0000f80000000070
Arg3: 0000000000000000
Arg4: 0000000000000000

I realize you said you ran Memtest86+, but did you run it for a full 8 passes? It takes 8 full passes to completely check you ram. If you didn't, please run it again for 8 full passes all at the same time.

Also, if you are overclocking anything, please set things back to default values until we get things straight.

Also, please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[djolegaf]

Hi, thanks for your quick response. I have run memtest 8 times, I stopped it on about half of 9th pass, and there is no errors. I have installed Diskeeper two days ago, when I already had problems with restarting, so I think that problem is not there. As I already said, nothing is OC, everything is on default state. I started system file checker for three times, and I get this message:

Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

I have to mention that I changed my motherboard a few weeks ago, and I did not go with fresh installing of windows, since in service told me that it is not necessary. My old chipset was A770E, so maybe there is a problem? I also changed GPU and PSU last week, so I don't think that problem is in this two components. However, both with old and new PSU, I have sometimes problem with starting computer. After BSOD it just stuck and there is only black screen, monitor is on standby, not even get POST screen, so I need to turn it off and start again. I changed BIOS with older version, but nothing changed. And on POST ''initializing USB controllers'' running very slow (20-30 sec. sometimes even more) every time when I start computer.
I think that is everything that I have to tell about my problem:sarc:. If I could remember anything else, I will let you know.

 

[Boozad]

You need to perform a clean install of Windows if you've changed the motherboard.

 

[djolegaf]

Yes, definitely I should, but in the meantime I need to figure out what is problem with my motherboard (black screen occasionally on power on, and long USB initializing).

 

[Boozad]

Probably drivers from your previous motherboard, that's why you need to perform the clean install before troubleshooting.

 

[djolegaf]

So, you say that drivers could be problem, even if my mobo don't even get to the POST screen?

 

[Boozad]

Yes. Or it could be down to the fact that you have a Lenovo PID on an ASUS retail motherboard meaning your installation is counterfeit.

[FONT=Courier New]Host Name:                 DJOLE-PC
  OS Name:                   Microsoft Windows 7 Ultimate 
  OS Version:                6.1.7601 Service Pack 1 Build 7601
  OS Manufacturer:           Microsoft Corporation
  OS Configuration:          Standalone Workstation
  OS Build Type:             Multiprocessor Free
  Registered Owner:          Djole
  Registered Organization:   
  Product ID:                [B][COLOR=Red]00426-OEM-8992662-00497 ----> Lenovo PID[/COLOR][/B]
  Original Install Date:     16.11.2013, 11:12:19
  System Boot Time:          3.7.2014, 22:46:10
  System Manufacturer:       System manufacturer
  System Model:              System Product Name
  System Type:               x64-based PC
  Processor(s):              1 Processor(s) Installed.
                             [01]: AMD64 Family 16 Model 10 Stepping 0 AuthenticAMD ~3000 Mhz
  BIOS Version:              American Megatrends Inc. 2103   , 18.6.2010[/FONT]

Counterfeit installations such as yours can contain heavily modified code that causes the installation to behave it unexpected ways. Analysing BSODs and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSODs far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them.

 

[essenbe]

djolegaf, you only had 3 dump files all dated 7/03, One dump file blamed Diskeeper, one blamed memory corruption and the other there was no information other than a generic 0X124 hardware problem. That is all the information I have to go on. The system file checker said you have corrupt system files. You changed motherboards without a clean install, and don't want to do a clean install. If you are going to continue not following our recommendations, I will no be able to help you. You are running drivers from the old motherboard on the new motherboard, which will not work, you do not want to Go with the dump file recommendation about diskkeeper, You do not want to do a clean install to get the correct drivers.

In addition to that you are running a cracked Operating system.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[djolegaf]

Ok, I get it. I will do clean, genuin installation of Windows as soon as possible, and I will inform you how does computer behave.
Thank you all for advices!