Random BSOD with PC in idle state: Bug Check 124

Hello aduckfan, welcome to Seven Forums, I will try to help you with your problem. You have 3 dump files, all showing a stop error of 0X124. That is a general hardware error and is very difficult to find out what piece of hardware it is. If you have made and hardware or software changes to your computer recently, please let me know. The error indicates either a piece of hardware is failing/failed or a driver is making it act in unexpected ways so the operating system thinks it is/has failed. Only the dump file from today gives any clues. However, while looking at the dump files I noticed a lot of references to the file system and what would be the Hard drive.

What the dump file did blame for the crash was

Code:

BHDrvx64
start             end                 module name
fffff880`05254000 fffff880`053db000   BHDrvx64 T (no symbols)           
    Loaded symbol image file: BHDrvx64.sys
    Image path: BHDrvx64.sys
    Image name: BHDrvx64.sys
    Timestamp:        Tue Sep 23 21:12:51 2014 (542228A3)
    CheckSum:         0018E7EA
    ImageSize:        00187000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Symantec Heuristics Driver

Code:

SYMNETS
start             end                 module name
fffff880`054cc000 fffff880`05562000   SYMNETS  T (no symbols)           
    Loaded symbol image file: SYMNETS.SYS
    Image path: SYMNETS.SYS
    Image name: SYMNETS.SYS
    Timestamp:        Thu Feb 13 05:25:14 2014 (52FCAB9A)
    CheckSum:         00098278
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Symantec/ Norton NIS/ N360 driver

Code:

tdrpm273
start             end                 module name
fffff880`01e4b000 fffff880`01f82000   tdrpm273 T (no symbols)           
    Loaded symbol image file: tdrpm273.sys
    Image path: tdrpm273.sys
    Image name: tdrpm273.sys
    Timestamp:        Tue Aug 10 04:54:18 2010 (4C6121CA)
    CheckSum:         0013510D
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is the Acronis Try&Decide Volume Filter Driver

and

Code:

nvlddmkm
start             end                 module name
fffff880`0f69b000 fffff880`10329000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Graphics driver.

I would suggest you remove Norton from your system, as it was blamed twice and is also known to cause BSODs. this will help you do it. https://support.norton.com/sp/en/us/...rProfile_en_us
And replacing it with Microsoft Security essentials for the time being at least until we find the cause of your problems. Microsoft Security Essentials - Microsoft Windows

I would seriously consider removing Acronis also. removal https://kb.acronis.com/content/34876

Please also run Seatools, Seagate's diagnostic test. Please run the long and short tests.

SeaTools for DOS and Windows - How to Use

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.

Let us know the results of these tests and if you see any improved results.

Norton is a known cause of BSODs, so removing it is a good idea. Some people can use it with no problems, many it gives them fits, bit needs the uninstall utility to completely remove it and there will be bits and pieces still left over. The same with Acronis. That's why I shy away from those two programs, they seem to try to 'take over' the computer, I personally do not like that. I only asked for the Seatools because in the dump files, as you look at them I kept seeing references to the NTFS file system and I/O issues. Never were any of those blamed for a crash, but I would be concerned if they were on my computer.

Me either, I can't read them. I'll have to ask for some help here. Have tou had any more BSOSs? If so, please run Blue Screen of Death (BSOD) Posting Instructions and upload the results with your next post.

Just for your information, if you make a new post in this thread, I will be notified, if you edit a previous post I will not be notified, so please always make a new post.

No problems. I have asked for someone to look at the CBS logs. I wouldn't be too concerned about your SSD. If a BSOD could kill one, mine would be dead and buried a long time ago. I've lost count, but I believe I have 13 SSDs now; albeit in about 5 computers, soon to be 6 I hope. But in overclocking, a BSOD is an 'occupational Hazard'.

I totally agree with essenbe.
If BSOD killed ssd's I would have a few dead ones laying around.

While one is figuring out the best over clock for their system you must just get use to BSOD now and again. In a way BSOD are useful when over clocking. It will let you know that the last thing you changed in your over clocking was a no no.

The CBS log is 'interesting'
The SFC scan summary shows the following...

Code:

 Line 3771: 2014-12-04 05:21:12, Info                  CSI    00000366 [SR] Repairing 3 components
 Line 3772: 2014-12-04 05:21:12, Info                  CSI    00000367 [SR] Beginning Verify and Repair transaction
 Line 3775: 2014-12-04 05:21:12, Info                  CSI    00000369 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"micross.ttf" from store
 Line 3778: 2014-12-04 05:21:12, Info                  CSI    0000036b [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:18{9}]"times.ttf" from store
 Line 3781: 2014-12-04 05:21:12, Info                  CSI    0000036d [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:20{10}]"timesi.ttf" from store
 Line 3784: 2014-12-04 05:21:12, Info                  CSI    0000036f [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"timesbi.ttf" from store
 Line 3787: 2014-12-04 05:21:12, Info                  CSI    00000371 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"timesbd.ttf" from store
 Line 3790: 2014-12-04 05:21:12, Info                  CSI    00000373 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"segoeui.ttf" from store
 Line 3793: 2014-12-04 05:21:12, Info                  CSI    00000375 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuib.ttf" from store
 Line 3796: 2014-12-04 05:21:12, Info                  CSI    00000377 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuii.ttf" from store
 Line 3799: 2014-12-04 05:21:12, Info                  CSI    00000379 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuiz.ttf" from store
 Line 3817: 2014-12-04 05:21:12, Info                  CSI    0000037b [SR] Repair complete

These are all system fonts, so it begs the question of why these files should have got corrupted in the first place.

There is one error that doesn't get trapped by the usual SFC extraction ...

Code:

2014-12-04 05:21:12, Info                  CSI    00000361 [SR] Committing transaction
2014-12-04 05:21:12, Info                  CSI    00000362 Creating NT transaction (seq 2), objectname [6]"(null)"
2014-12-04 05:21:12, Info                  CSI    00000363 Created NT transaction (seq 2) result 0x00000000, handle @0xbb8
2014-12-04 05:21:12, Error                 CSI    00000364 (F) STATUS_CANNOT_DELETE #7041045# from RtlRunPrimitiveOperationsFromCallbacksAgainstSil(...)[gle=0xd0000121]
2014-12-04 05:21:12, Info                  CSI    00000365 [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation.

This should have been corrected on the reboot - but second run of SFC /SCANNOW will double-check that, so please do it and see if you get the expected 'no integrity violations found' message. If not, please post the new CBS.log file.