It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
General discussion (archive)Daily BSOD(56 posts)(56 posts)
(56 posts)
Pages:
1
2
3
4
This is my favourite topic
Posted October 21, 2012
I don't even is this the right one:
2012-10-20 14:19:25, Info CSI 0000001f Repair results created: POQ 5 starts: 0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\76036386c5aecd015a020000cc170814._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms" 1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\97516386c5aecd015b020000cc170814.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms" 2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\d3f26a86c5aecd015c020000cc170814.$$_system32_21f9a9c4a2f8b 514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms" 3: Move File: Source = [l:240{120}]"\SystemRoot\WinSxS\Temp\PendingRenames\37dd6b86c5aecd015d020000cc170814.$$_system32_logfiles_ait_ 5b4995189d2e6c55.cdf-ms", Destination = [l:152{76}]"\SystemRoot\WinSxS\FileMaps\$$_system32_logfiles_ait_5b4995189d2e6c55.cdf-ms" 4: Move File: Source = [l:258{129}]"\SystemRoot\WinSxS\Temp\PendingRenames\47046c86c5aecd015e020000cc170814.programdata_microsoft_win dows_ait_140a03828e6ffe97.cdf-ms", Destination = [l:170{85}]"\SystemRoot\WinSxS\FileMaps\programdata_microsoft_windows_ait_140a03828e6ffe97.cdf-ms" 5: Move File: Source = [l:246{123}]"\SystemRoot\WinSxS\Temp\PendingRenames\d7687486c5aecd015f020000cc170814.$$_diagnostics_system_aud io_9d2751b7c84ca0f1.cdf-ms", Destination = [l:158{79}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_audio_9d2751b7c84ca0f1.cdf-ms" 6: Move File: Source = [l:258{129}]"\SystemRoot\WinSxS\Temp\PendingRenames\e78f7486c5aecd0160020000cc170814.$$_diagnostics_system_aud io_en-us_9fb258d76056760d.cdf-ms", Destination = [l:170{85}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_audio_en-us_9fb258d76056760d.cdf-ms" 7: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\3a537586c5aecd0161020000cc170814.$$_diagnostics_system_aer o_8b2c42561936b3f0.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_s 2012-10-20 14:19:25, Info CSI ystem_aero_8b2c42561936b3f0.cdf-ms" 8: Move File: Source = [l:256{128}]"\SystemRoot\WinSxS\Temp\PendingRenames\4b7a7586c5aecd0162020000cc170814.$$_diagnostics_system_aer o_en-us_1a668ac520a43d24.cdf-ms", Destination = [l:168{84}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_aero_en-us_1a668ac520a43d24.cdf-ms" 9: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\1d7b7e86c5aecd0163020000cc170814.$$_system32_manifeststore _7d35b12f9be4c20e.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms" 10: Move File: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\fde78286c5aecd0164020000cc170814.$$_help_windows_en-us_b59 4929e73669c5e.cdf-ms", Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_help_windows_en-us_b594929e73669c5e.cdf-ms" 11: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\0e0f8386c5aecd0165020000cc170814.$$_help_help_en-us_91e6e7 979a9bf9c6.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms" 12: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\acdf8686c5aecd0166020000cc170814.$$_apppatch_1143992cbbbeb cab.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_1143992cbbbebcab.cdf-ms" 13: Move File: Source = [l:236{118}]"\SystemRoot\WinSxS\Temp\PendingRenames\acdf8686c5aecd0167020000cc170814.$$_apppatch_apppatch64_e3 9bab3b20714e20.cdf-ms", Destination = [l:148{74}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_apppatch64_e39bab3b20714e20.cdf-ms"
Wow, GOG really needs a preview button for your messages.
Post edited October 21, 2012 by Profanity
Posted October 21, 2012
If I'm not mistaken it replaced corrupted files in Windows. If it keeps restarting, it's hardware. Did you check PSU power on that site to rule out that it's too weak for your computer?

Meh, forum is broken beyond repair. I really hope it will get complete overhaul.
Post edited October 21, 2012 by IronStar
Posted October 21, 2012
avatar
Nirth: If you have corrupted files try this application: HDD Regenerator The trial can only do so much but it couldn't hurt, at least you will get more information.
avatar
Profanity: Doesn't disk check with an option to look for bad sectors do the same?
Compared to the trial, maybe but their algorithm is quite sophisticated so it's possible even that is a better choice. Their professional version can actually repair damaged bad sectors sometimes.
Posted October 21, 2012
avatar
IronStar: If I'm not mistaken it replaced corrupted files in Windows. If it keeps restarting, it's hardware. Did you check PSU power on that site to rule out that it's too weak for your computer? Meh, forum is broken beyond repair. I really hope it will get complete overhaul.
When I saw how much info I'll have to put, I decided to leave that for the evening and go have a play of mass effect. Anyway, I don't believe it's the power supply, simply because it happens ONLY once a day and after that it can work for as many hours as I want without a single problem and without any slowdowns. If the power supply was the problem, I don't think I'd be getting off that easy.
Posted October 21, 2012
What does the BSOD message say? Which exact processes and files are causing it?
Posted October 21, 2012
avatar
Elenarie: What does the BSOD message say? Which exact processes and files are causing it?
avatar
Profanity: ...It doesn't help that the errors displayed by the BSOD keep shuffling and changing every day. I have tried checking the disk and repairing bad sectors, and it fixes the issue for around two days, but then it starts it's tune again....
Posted October 21, 2012
Well, I can't really know if this was really fixed by everything I've tried today, so I'll report back tomorrow.

Thanks everyone for helping out and time will tell how fucked am I.
Posted October 26, 2012
Daily BSODs are still at it, but this time the error is staying the same: 0x0000024.
Posted October 26, 2012
I had a similar issue for some time. In my case it had something to do with my power unit not strong enough for my graphics card.

Try switching components if possible.
Posted October 26, 2012
Copying from here: http://www.geekstogo.com/forum/topic/43519-windows-xp-blue-screen-of-death-stop-codes/ (WinXP but I expect the codes are the same for Win7)


Stop 0x00000024 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

• Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.

• Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity

Method 1:

1. In the Run dialog box, in the Open box type:
cmd

2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f

Method 2:

1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.

If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

• Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.


Also http://msdn.microsoft.com/en-us/library/windows/hardware/ff557433%28v=vs.85%29.aspx
Post edited October 26, 2012 by jamsatle
Posted October 26, 2012
avatar
wpegg: I'd point the finger squarly at bad RAM. I had this when I was trying to run two pairs of RAM that was recommended at 2 different voltages. Make sure you're running at the right voltage, and run a memtest..
avatar
Fenixp: That would lead to completely random BSODs instead of 'within one hour' tho, wouldn't it? RAM sticks were my first guess as well, but the one hour rule kind of confuses me...
It could be explained by the following scenario:

1. There's a "loose connection" in a RAM block.
2. The RAM is filled in a specific order.
3. The loose connection is only present in a cool state. When the RAM block heats up, the expansion seals the connection.

This would mean that when the machine is first cold booted, you'd get an error as soon as the faulty memory location is hit. If the address is high enough to not be hit by the OS itself, it will only be hit after a while after boot, provided something is done on the machine. After an hour, the RAM has heated up enough to seal the connection, and you won't experience the problem anymore.
Posted October 27, 2012
avatar
Fenixp: That would lead to completely random BSODs instead of 'within one hour' tho, wouldn't it? RAM sticks were my first guess as well, but the one hour rule kind of confuses me...
avatar
Wishbone: It could be explained by the following scenario:

1. There's a "loose connection" in a RAM block.
2. The RAM is filled in a specific order.
3. The loose connection is only present in a cool state. When the RAM block heats up, the expansion seals the connection.

This would mean that when the machine is first cold booted, you'd get an error as soon as the faulty memory location is hit. If the address is high enough to not be hit by the OS itself, it will only be hit after a while after boot, provided something is done on the machine. After an hour, the RAM has heated up enough to seal the connection, and you won't experience the problem anymore.
Tried switching ram spots into previously unused ones. Didn't help much, still got BSOD. 0x000003b one.
Posted October 27, 2012
Hmm..this one is related to faulty GFX card driver.

I don't know what to think anymore. Faulty motherboard?
Posted October 27, 2012
avatar
Profanity: It doesn't help that the errors displayed by the BSOD keep shuffling and changing every day. I have tried checking the disk and repairing bad sectors, and it fixes the issue for around two days, but then it starts it's tune again.

What the fuck? Has anyone had anything similar going around?
From this alone i would immediately run a SMART check on your hard drive, it sounds like you have something going on with it.

download a program called Defraggler once you get it installed launch it and click the "health" tab at the bottom with an image of a pill on it. check the numbers and see if there are any warnings...

If you need a boot CD there is always Hiren's Boot CD, has every diagnostic utility you'll need for all your hardware, including Defraggler :)
Post edited October 27, 2012 by Starkrun
Posted October 29, 2012
Did a little test on a suspicion I had and it seems like it doesn't bluescreen if I don't turn on steam (I mean, it doesn't insta bluescreen with Steam, but it still does quick enough)... Very inconvenient.
Pages:
1
2
3
4
This is my favourite topic
Community
General discussion (archive)Daily BSOD(56 posts)(56 posts)
(56 posts)