BSOD Blue Screen of Death - system crash: KERNEL DATA INPAGE ERROR, STOP ; win32k.sys

Discussion in 'other software & services' started by PROROOTECT, Sep 14, 2009.

Thread Status:
Not open for further replies.
  1. PROROOTECT

    PROROOTECT Registered Member

    Joined:
    May 5, 2008
    Posts:
    1,102
    Location:
    HERE ...Fort Lee, NJ
    I have PC tower with WindowsXP SP2, Intel Core2 CPU, 1.0 GB RAM.

    I only pressed the icon for IE7 ... I immediately had the BSOD with message:

    KERNEL_DATA_INPAGE_ERROR : STOP : 0x0000007A , win32k.sys

    And during the attempt of recovery with my CD:

    'Error 7 No hard drive !!!' ... and: 'HDD=NO-HD:' , Backup=NO_BACKUP:' messages.

    I did press 'Exit' button to exit from this failed recovery process.

    My SOLUTION: I put in the right place: the CPUFAN (CPU FAN) contactor! ... little, white ... That's all.

    """"""""""""""""""""""""""

    Immediately after, I noted this:

    * No problem of dust in my PC,
    * CPU temperature from Core Temp v0.99.5 : 35 and 33 Celsius degrees for my two Cores,
    * Event's Viewer: nothing,
    * explorer.exe Working Set: 16.81 MB, it's OK,
    * PC is well defragmented (with Smart Defrag v1.03 - iobit): Fragmentation before: 0.43%. fragmented file count: 262. It's OK,
    * IE Temporary Internet Files: 80 KB only,
    * With new version of MBAM: congratulations - the scan completed successfully: nothing,
    * RootRepeal scan: nothing.

    Yes, my BSOD today: successfully not present.

    """"""""""""""""""""""

    Google for: to avoid BSODs happening:

    *Avoid the PC heating.
    * This is the processor that heats too: buy thermal paste (1$ ?), remove the old and call the new without smudging.
    * Exit and return to their places the memory chips.
    * Remove the dust.


    PROROOTECT


    ... no worry about this ...
     
  2. Sully

    Sully Registered Member

    Joined:
    Dec 23, 2005
    Posts:
    3,719
    Re: BSOD Blue Screen of Death - system crash: KERNEL DATA INPAGE ERROR, STOP ; win32k

    Always do a memory scan with recurring problems. Bad memory boots many times, but when the bad area of memory is finally 'touched' things will happen that make you think your OS is gone bad. Memtest86 is what I use. So many times I have found a bad module of ram, removed it to find the problems are gone. And these days, many modules have lifetime warranty.

    Sul.
     
  3. HAN

    HAN Registered Member

    Joined:
    Feb 24, 2005
    Posts:
    2,080
    Location:
    USA
  4. Franklin

    Franklin Registered Member

    Joined:
    May 12, 2005
    Posts:
    2,517
    Location:
    West Aussie
    If it's cpu heat related isn't it instant off with no bsod?
     
  5. BlueZannetti

    BlueZannetti Administrator

    Joined:
    Oct 19, 2003
    Posts:
    6,590
    Generally not unless it's via an extreme overclock.

    My own experience is that things could work without problem on a winter day, but fail after a few hours use as summer rolled around. Problem in my case was a failed fan and it always went south via BSOD.

    Blue
     
  6. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,049
    I only had one issue along these lines. When I first got my AMD machine it must have been jostled in shipping, and at one point a heard a strange snap type noise. Didn't think much about it until the machine suddenly turned itself off.

    No BSOD, it just shut itself off.

    Pete
     
  7. Az7

    Az7 Registered Member

    Joined:
    Sep 14, 2005
    Posts:
    139
    I think the Stop 0x7A error (BSOD) = Virtual Memory error (Pagefile.sys)
    caused by : problems in storage subsystem :-
    * controllers (bad settings and configurations, ..)
    * cables ([power/data] old, defective, ..)
    * hard disks (bad sectors, ..)
    etc..
     
  8. PROROOTECT

    PROROOTECT Registered Member

    Joined:
    May 5, 2008
    Posts:
    1,102
    Location:
    HERE ...Fort Lee, NJ
    Thank you all,

    I have NOT overclocked my processor.

    My processor is Intel Core Duo E 6300 (Conroe); his frequency: 1595,7 MHz, and voltage VID: 1.325 V.

    My fan cable contactor was pressed halfway, then surely he had a bad contact somewhere; and the day was hot ...

    Good link: 'How to solde Windows system crashes in minutes' : http://www.networkworld.com/news/2005/041105-windows-crash.html

    .. and for Vista fans ( :argh: ): http://news.softpedia.com/news/Vista-SP2-Perpetual-Black-Screens-of-Death-0xc0000034-121528.shtml


    PROROOTECT
     
Loading...
Thread Status:
Not open for further replies.