executable file's failure to initiate itself in a proper functioning status.
Which Edition of Windows do you have? Win. XP of any kind of Edition is most likely to bring up this unfortunate problem.
Note: A PC, in time, will react to negligence of use(been put away for too long and HDD might have deteroriated to the point that there are too many bad sectors that are affecting the O.S. sectors of it). Even reformatting such HDD will not help. Happened on a single core machine of mine with Vista SP2 on it. Had very good drivers onto it before archiving the machine in a damp basement at my parents' place for over a year. Both my mother's XP machine and mine had to be sent to the electronics recycling depot because of these unrepairable system errors.
Also, Windows has this notorious need to be patched every month of every year. It is a bad kernel programming on their part but, the continuous updating and upgrading of both the users apps and device drivers do not help, either.
If it is not the registry corrupting itself over time, the sectors on the HDD going bad/corrupted, its their O.S. itself that loses its own installation image and integrity.
Hey guys ive been experiencing these two blue screens.
I have updated my drivers, downgraded done a clean install of drives etc...
I also ran my pc in safe mode for sometime to determine the source being hardware or software and its obviously software since it didn't occur in safe mode.
I also go the following information using whocrashed program for the SYSTEM SERVICE error:
crash dump file: C:\Windows\Minidump\040812-18891-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ADE41F, 0xFFFFF8800A1250D0, 0x0)
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.