Random BSOD after start-up

I am writing with the problem of recurring BSOD, which happens randomly, almost always after the computer's start-up (ca. 2-5 mins). Important is the fact, that very often is not BSOD - computer also tends to freeze or it restarts without any BSOD (and this is worse case, because no dump file is created).
I submitted my problem some time ago (in this thread: http://windowsforum.com/threads/bsod-random-bsods-and-hangs-at-startup.92606/). Following the advices, I bought a new PSU. About month ago, I also formatted my disk completely (more precisely, I zeroed it). There had been no faults for few weeks, but now the problem has returned...
Of course I am attaching the zip file with logs W7F Diagnostic Tool, screens from CPU-Z and HTML file from PassMark RAMMon.
Thank you in advance for any help.



Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff800041fcff0, 0, 0, fffff80002a864fc}

Probably caused by : hardware ( nt!KiInterruptHandler+29 )

Followup: MachineOwner
out of the three dump files sent the earliest blamed Norton AV, the second blamed an NTFS or HDD issue and the above as you can see is pointing to hardware.

SYMEVENT64x86.SYS Sat Jul 27 03:26:58 2013: Norton/Symantec. This app is infamous amongst debugging circles for causing issues.. Please use the tool found here and remove Norton: (you can always re-install later if Norton isn't the culprit)

Run MSE in the meantime as this is super stable:

If the bsod continues after removing Norton then try checking your C drive with a chkdsk:

Rt64win7.sys Fri Jun 10 07:33:15 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:

Post any new dump files.


Again there were one BSOD and one restart without BSOD. Unfortunately, I have no dump file, because I had wrong settings... I have already followed instructions from this topic: http://windowsforum.com/threads/where-are-dump-files-dmp-saved-after-crash.39784/ so I hope that next time new dump files will be created. Now, only the MEMORY.DMP was created but it's too big to attach it here (over 400 MB).

I think that Norton just cannot be the reason - last time, when I had the same problems, I didn't have Norton - there was Microsoft Security Essentials installed on my computer.

I'll try checking C drive and updating Realtek driver.

I have one more question - you wrote that there is a hardware issue. Is there any way to get to know which part of hardware is problematic?


Windows Forum Admin
Staff member
Premium Supporter
Not straight off unless the issue is mentioned specifically. We can only test at this stage and go from there. If you really feel that Norton isn't the issue then leave it for now and just do the other stuff mentioned. You can always go back to it.


I have checked disk with chkdsk. And there are results:

 874257407 KB total disk space.
  79661744 KB in 126202 files.
     81224 KB in 31362 indexes.
         0 KB in bad sectors.
    345279 KB in use by the system.
     65536 KB occupied by the log file.
794169160 KB available on disk.

      4096 bytes in each allocation unit.
218564351 total allocation units on disk.
198542290 allocation units available on disk.
Moreover, I've updated Realtek Gigabit Ethernet.

Could be there some more information about restarts without BSOD or freezes e.g. in event logs?


Windows Forum Admin
Staff member
Premium Supporter
It's always worth a look.. :) Find command prompt in the start menu, right click on it, choose properties then run as admin. Type:
sfc /scannow
Press enter and await results. This will check for and hopefully fix corrupt system files.

I made sfc /scannow and there were no errors. Till now I had no BSOD nor any other problem. I'll write when there will be something new.

Hi, unfortunately my computer suddenly restarted again... And there was no BSOD, so I have no dump file. Is it possible to find information about this event in some other way so you could look at it somehow?


Windows Forum Admin
Staff member
Premium Supporter
Are you sure it was a bsod? Check the event log and see what that say's.

As I have written, there was NO BSOD, that's why I have no dump file.
Could you guide me how to check the event log?


Windows Forum Admin
Staff member
Premium Supporter
Oh right..ok. Open the control panel, click System and Security then look under Admin Tools. What actually happened, were you doing something in particular?

Hi, today my computer restarted 2 times and there was one BSOD (as I can't attach it here (there is an error and information that server can't process this file because it is too large) you can find dump file there: https://dl.dropboxusercontent.com/u/74280466/093014-23868-01.dmp). And again I had the same problems: after the second restart I can't turn my computer on - I press the start button, I can hear the fans' noise but the monitor remains switched off (it is supposed to switch on automatically when the computer starts) - it doesn't receive any signal.

When computer restarts or when there is BSOD, I do nothing special - this time I was checking my mail. But earlier all this happened also when noone was doing anything - there was no program on etc.

I looked into the event log, there was information that there were 3 critical errors in the last hour. All these errors have Event-ID 41 and the source "Kernel-Power" and there is some data in XML:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<TimeCreated SystemTime="2014-09-30T08:49:39.791223300Z" />
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Security UserID="S-1-5-18" />
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
Moreover, I have some other (not critical) errors:
80: SideBySide
877: Application Popup
1001: Dhcp-Client
1001: BugCheck
1005: BugCheck
6008: EventLog
36888: Schannel


Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff80002c20730, fffff80002c20710, fffff80002c20730}

Probably caused by : memory_corruption

Followup: memory_corruption
apologies about the upload situation. We had a major security issue over the weekend and we are still getting the house back in order. Hopefully it will be rectified soon.
Now although the above say's memory corruption it's doubtful that it means your RAM is bad. The actual process which caused the above came from an Nvidia driver namely:
Apparently this driver has been known to cause issues and it might be worth you reading this link:

Please check your GPU by running this test:

I see your running an Nvidia 9800GT could you post the make and model of your PSU please including age.

Going through your event log errors:

80: SideBySide:
Possibly Adobe?
There are many programs that can generate this type of error. Any suggestions found on support forum or software developers sites should be verified that they apply to your application (though comments for other applications may provide additional clues in solving this). The first step in troubleshooting this would be to check for updates for the application specified in the event.

A common application causing this problem is Adobe Designer (C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe). From an Adobe Support Forum: "For Vista 64 bit users this error seems to be caused by a wrong manifest embedded in the FormDesigner application. It references the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first."

A similar comment (almost identical but with more details), that apparently, if followed, can fix the problem: "This error is caused by a wrong manifest embedded in the FormDesigner application. If you open the application in Visual Studio and extract the manifest you will see two references to the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first. To test just try removing the processor-agnostic reference from the manifest and resave the app in Visual Studio. When you rerun the app the errors are gone.

IMO this should be fixed by Adobe - and obviously since the FormDesigner app is 32-bit the reference should be restricted to 32-bit."
x 15

877: Application Popup:
There was error [DATABASE OPEN FAILED] processing the driver database.
http://www.eventid.net/display-eventid-877-source-Application Popup-eventno-1992-phase-1.htm

1001: Dhcp-Client:
Your computer was not assigned an address from the network (by the DHCP server) for the network adapter with MAC address %1. The following error occurred:
%2. Your computer will continue to try to obtain an address on its own from the DHCP server.

1001: BugCheck:
The computer has rebooted from a bugcheck.

1005: BugCheck:
Unable to produce a minidump file from the full dump file.

6008: EventLog:
This event is written during startup following an unexpected restart or shutdown. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer's reset button or unplugs the power cord.

If the Persistent Time Stamp group policy setting is either enabled or not configured, system information is written to the data section of this event. This information includes a timestamp that indicates the computer's uptime in seconds before the unexpected shutdown occurred.

User Action
One or more of the following actions might help to determine the cause of the unexpected shutdown:

  • Check the system event log for other events that occurred around the same time as the unexpected shutdown.
  • Find out whether the computer's reset button was pressed, the power cord was unplugged, or a general power failure occurred.
  • Configure Windows to perform a memory dump of system failures and submit that data to Microsoft for debugging through Windows Error Reporting. For more information about Windows Error Reporting, see Help and Support.
36888: Schannel:
Possibly Outlook? or another app which is used to access the net like STEAM or Origin

Although the above doesn't carry a solution for each Event ID I did try and include as much info so you could at least know what needs looking at (although some are simply reports and don't need a follow up).

Post back if I can help further.


It is getting worse and worse... There were some restarts (still critical error, ID 41) and one BSOD again (you can find dump file here: https://dl.dropboxusercontent.com/u/74280466/093014-29187-01.dmp). And again I have been unable to run my computer for a long time - a monitor couldn't turn on, because there was no signal - I had to turn it off and turn it on many times.

I made a test of GPU by running the test you recommended (over 100 iterations) - there were no errors...

Regarding my PSU - I have Be quiet! Pure Power L8-CM-530W BN181. It is one year old.

Thank you for your help.


Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002bbba9b, fffff880033a8418, fffff880033a7c70}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
It does sound like your GPU could be at fault. Try stress testing using this app:
Also is it possible for you to try the card in a different machine? Perhaps a friend will help?

So we can eliminate them from the issue please test your RAM.

Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight, if possible try and run for 12hrs (some errors won't appear until the 12th hour) unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Hi, I made GPU test with FurMark, the results are below:

I need some time to make RAM tests (since it will last 12 hours), I'll write when I'll have results.
Thank you for your help!


Windows Forum Admin
Staff member
Premium Supporter
I'll await your next reply..

Hi, I made RAM tests, I've run them for over 13 hours. There were no errors. What could I do now?


Windows Forum Admin
Staff member
Premium Supporter
Well Norton is always worth a try plus you can always re-install it later. Just make sure you use the removal tool specified above.

You could also try running one stick of RAM only. If the machine bsod's then change slots and test again. If you find a slot which doesn't bsod then you know a slot is bad.

Last edited:
I'm 100% sure it's not Norton. As I wrote previously, there was exactly the same problem when Norton was not installed and I had Microsoft Security Essentials. Moreover, my problems occur also before Windows start.

I can try with RAM, but what about GPU? You said that you considered this as a main reason.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.