1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PC Shuts down on its own

Discussion in 'Hardware' started by mirack, Jan 18, 2009.

  1. mirack

    mirack Private E-2

    Everynow and then randomly my pc freezes and essentially shuts down, whatever screen I am on it is still there but when I push the power button it reboots.
    I checked the temp, and it is running around 55, 1 out of 10 I will get the blue screen but it goes away before I can read anything? What info do I need to provide?

    Intel D946GZIS mobo
    2gb Kingston Ram
    Pentium D processor 3.0*2
    500g wd hdd.
    Also I get no error and it boots back up as if I shut it down.
  2. Petaluma

    Petaluma First Sergeant

    You can read this and learn how to get and debug a minidump of the system when you get the dreaded BSOD.

    Please read and follow all the directions before doing this. As there are many steps that rely upon each others info.
  3. mirack

    mirack Private E-2

    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\Mini011609-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16386.x86fre.vista_rtm.061101-2205
    Machine Name:
    Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
    Debug session time: Fri Jan 16 18:14:04.505 2009 (GMT-4)
    System Uptime: 0 days 1:57:10.407
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 19, {22, fda6d000, 21, 0}

    Probably caused by : win32k.sys ( win32k!FreeObject+2b )

    Followup: MachineOwner

    1: kd> !analyze -v at the kd>
    * *
    * Bugcheck Analysis *
    * *

    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arg1: 00000022,
    Arg2: fda6d000
    Arg3: 00000021
    Arg4: 00000000

    Debugging Details:

    BUGCHECK_STR: 0x19_22

    POOL_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
    Unable to read MiSystemVaType memory at 81911780



    PROCESS_NAME: iexplore.exe


    LAST_CONTROL_TRANSFER: from 8187447e to 818d85c9

    92783a30 8187447e 00000019 00000022 fda6d000 nt!KeBugCheckEx+0x1e
    92783a70 818e7cae 00a6d000 92783abc 92783aa0 nt!ExpFindAndRemoveTagBigPages+0x180
    92783ae0 8d8e264e fda6d000 00000000 92783b58 nt!ExFreePoolWithTag+0x145
    92783af0 8d8bffae fda6d000 00000005 ffa8a048 win32k!FreeObject+0x2b
    92783b58 8d8c0038 00000000 cd050b58 92783b7c win32k!SURFACE::bDeleteSurface+0x1dc
    92783b68 8d8c010a 00000000 cd050b58 fda6d000 win32k!SURFREF::bDeleteSurface+0x12
    92783b7c 8d85775a cd050b58 ff4bc008 92783bac win32k!bDeleteSurface+0x20
    92783b8c 8d823a27 fda6d010 00000000 ffa8a008 win32k!vSpDeleteSurface+0x1c
    92783bac 8d900730 ffa8a008 ffa8a008 00000000 win32k!vSpDeleteSprite+0xb1
    92783bd4 8d89c518 fe9c05e0 00000000 00000000 win32k!GdiSetPointerShape+0x65
    92783c1c 8d898e7c fe9c05e0 00000000 00000000 win32k!EngSetPointerShape+0x20a
    92783cb8 8d898dc0 ffa8a008 00000000 00000000 win32k!vSetPointer+0x67
    92783cf4 8d899444 855e4998 00000000 00000000 win32k!GreSetPointer+0x71
    92783d18 8d8d8016 00000000 00000000 fec4d0c0 win32k!SetPointer+0xea
    92783d34 8d89a0d3 00000042 92783d54 8d8d8c8b win32k!zzzUpdateCursorImage+0x17f
    92783d40 8d8d8c8b 00000000 00000000 026df44c win32k!zzzShowCursor+0x4c
    92783d54 8188c96a 00000000 00000042 026df44c win32k!NtUserCallOneParam+0x21
    92783d54 77850f34 00000000 00000042 026df44c nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    026df44c 00000000 00000000 00000000 00000000 0x77850f34


    8d8e264e 5d pop ebp


    SYMBOL_NAME: win32k!FreeObject+2b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys


    FAILURE_BUCKET_ID: 0x19_22_win32k!FreeObject+2b

    BUCKET_ID: 0x19_22_win32k!FreeObject+2b

    Followup: MachineOwner

    This is what I got so is win32k the problem?
  4. Petaluma

    Petaluma First Sergeant

    Not the problem but it is an indicator of what might be going on.
    It could be hardware related
    Any new parts installed recently? memorycpu,mobo etc?

    You can run a check on your memory with Memtest available here at MG's(read instructions)

    Of course before beginning make sure to backup all your info now. Better safe than sorry.
    Post back when you get a clean bill of health on the memory....
  5. Ginge7289

    Ginge7289 Private E-2

    Possibly a power supply porblem.

    If you have added any hardware that could cause it, how old is the comp? I see your running vista so leads be to believe you have a new comp unless you upgraded.
  6. jonote

    jonote Private E-2

    best thing to do if you can't read the blue screen of death is hit f8- then in the advanced start up options menu select "disable automatic restart on system failure"- this stops the pc from rebooting from bsod errors- then you can read error message - you won't find the answer there but you may get a few clues - you may have to boot into safe mode if its buggy device drivers - or last known good config
  7. jonote

    jonote Private E-2

    I think thats a registry problem - if "last known good config" doesn't work then you may have to rebuild your registry in the recovery console

    boot from your windows cd rom and select repair installation to get to the recovery console -on enter press 1 or 2 to select which os you want to restore then it will ask you for the administrators password - you are then in the recovery console - you'll see the prompt


    just type

    delete c:windows\system32\config\system
    delete c:windows\system32\config\software
    delete c:windows\system32\config\sam
    delete c:windows\system32\config\security
    delete c:windows\system32\config\default

    copy c:windows\repair\system c:\windows\system32\config\system
    copy c:windows\repair\software c:\windows\system32\config\software
    copy c:windows\repair\sam c:\windows\system32\config\sam
    copy c:windows\repair\security c:\windows\system32\config\security
    copy c:windows\repair\default c:\windows\system32\config\default

    hope thats helpful
  8. mirack

    mirack Private E-2

    Memory is good, pc less then 6 months old. Recently added a sound card and reformatted twice since this started and yet it persists. I am going to go with whoever said PSU, or CPU. Both of which I am replacing anyways. After that I will see I guess.
  9. aidan80

    aidan80 Private First Class

    Is your machine overclocked at all, how is the memory timings are they at where they should be? Overclocked or mismatched memory or memory running at the wrong timings will cause problems. PSU is another possible cause but I'd check the BIOS check all the settings before pulling other items out. I assume you've ran Memtest? Do you have a multimeter or a PSU tester before pulling it? Drivers updated, is things stable in safe mode?

    I'd also try removing that sound card and see how things run, try with one stick of RAM then try the other, if you have another PSU try that.. but try one thing per time. You'll of course want to figure out who or what is causing it. Changing too much or everything at the same time may make it go away only to crop up again later.

    Last known good configuration is great but each time to get into windows without a problem.. that becomes your last known good configuration!

    I'd start by assuming it's a software problem until you've either established it's hardware or you run out of things to try software wise.. e.g. drivers, updates, BIOS settings etc then move to hardware troubleshooting.. e.g. remove items, change things around, test PSU.. etc

Share This Page

MajorGeeks.Com Menu

MajorGeeks.Com \ All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ NEW! PC Games \ System Tools \ Macintosh \ Demonews.Com \ Top Downloads

MajorGeeks.Com \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds