BSOD in Windows 7 graphical interface, safe mode too

Page 1 of 5 123 ... LastLast

  1. Posts : 23
    Windows 7 Home Premium 64bit
       #1

    BSOD in Windows 7 graphical interface, safe mode too


    Hello!

    I am new to this forum(posting any way). I have read some earlier posts the last couple of days.

    I help a client with a computer that BSODs at the windows graphical interface right after it has started which takes quite a long time, also in safe mode.

    This makes it impossible to collect the minidump-file to post here basically.

    First he could not display labels and one couldn't even read the text on task manager. He BSOD'd if he pressed Start. The Stop is 0x000000050(can't remember the number of zeros). After running the "repair"-option after pressing F8 at the start of the computer, we were able to see the start button and labels etc, also the text on the task manager. This stop mentioned win32k.sys.

    but now instead he BSOD'd with another stop code: 0x00000003b. I have tried to run "pkgmgr /ip /m:[location]" to install a hotfix I found for this error(KB2359223), but it doesn't seem to install this package for some reason.

    His computer is a Samsung NP-R580H laptop. He says he can run 64-bit IE so I assume his win 7 home must be 64 bit.

    After the Stop 3b, we can some times see the error 0x00000019, bad_pool_header, but not always.

    I have wanted to rename his win32k.sys from the command-prompt, but it says I'm not allowed to do that(not permitted) and I didn't want to give him "full rights" of the whole System32-folder, which I believe would let him change the name of this file so it could be replaced? I have done this on XP, but not from the command prompt.

    His computer takes 15 mins to start.

    "sfc /scannow" have said there were errors that it could not repair. Have run it 3 times today and 1 time before(that time with no errors strangely).

    Would appreciate help...
      My Computer


  2. Posts : 8,476
    Windows® 8 Pro (64-bit)
       #2

    1. Boot to System Recovery Options

    2. Then run Start-up Repair.

    Let us know if you're then able to boot to desktop.
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #3

    Computerhelper said:
    Hello!


    I have wanted to rename his win32k.sys from the command-prompt, but it says I'm not allowed to do that(not permitted) and I didn't want to give him "full rights" of the whole System32-folder, which I believe would let him change the name of this file so it could be replaced? I have done this on XP, but not from the command prompt.

    His computer takes 15 mins to start.

    "sfc /scannow" have said there were errors that it could not repair. Have run it 3 times today and 1 time before(that time with no errors strangely).

    Would appreciate help...
    So it starts after a late, and as and when it starts, it BSODs?
    Try SFC /SCANNOW : Run in Command Prompt at Boot at first.

    If failed, boot to System Recovery Options as Dinesh suggested. Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

    start msconfig


    It will open the system configuration window, with the "general" tab selected. Click the "startup" tab. Click "Disable all" > Apply > OK.

    Then try to boot again normally. Is it failing still?

    If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc and collect it in a USB stick, use the usb stick in another computer and upload it. It is necessary.


      My Computer

  4.    #4

    In addition to performing the steps requested and reporting back results, continue working through Troubleshooting Steps for Windows 7

    If Win7 becomes unstable then use these same steps for Troubleshooting Windows 7 Failure to Start.

    I would rescue any files needed using Step 9, run the hardware tests, then start at Step 1.
    Last edited by gregrocker; 08 Feb 2013 at 14:28.
      My Computer


  5. Posts : 23
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    BSOD'd again....


    I need a clarification. Which tab did you mean in "msconfig"? There is no option to "disable all" under the general tab, but one can do that under services and "startup"(2 other tabs).

    Hm, I was sitting there looking at the different services in msconfig when I BSOD'd again... The page fault BSOD(0x50)... msconfig is graphical after all... win32k.sys was mentioned.

    I did run the "Startup repair and it actually wrote that it could not repair this computer automatically. I scanned the files it showed about the repair attempt and I saw it wrote: "Root cause found: Unspecified changes to system configuration might have caused the problem"; "Error code = 0x490, "System files integrity check and repair".
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS (Source: Carrona.org)

    I told you to go to this location: Startup tab> Disable all.

    And follow Troubleshooting Windows 7 Failure to Start. as gregrocker suggested.
      My Computer


  7. Posts : 23
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Further clarification: I can startup without a problem(except for the sluggishness). It's that I BSOD directly once it's in graphical mode(normal or safe), that is the problem. This also happens without doing anything on the computer.

    Can either of you answer my 2 previous questions in my first post about 1) how to rename the win32k.sys from the command prompt? and 2) why the pkgmgr would not install that hotfix I had found with the command I posted before?

    I will try to enable logging soon enough and upload that file. Again though, it's not the startup that fails, it's right after.

    I will try to disable his Avast and also try to run sfc /scannow again.

    Tomorrow I will try to download win 7 home premium and try to make a windows repair.

    Right now I have restarted windows using msconfig's option to only have the basic stuff(2nd option on the general tab). I did not know one could have msconfig on at the command prompt, cool!
      My Computer


  8. Posts : 8,476
    Windows® 8 Pro (64-bit)
       #8

    On the recovery options, open command prompt and type chkdsk C: /r and press Enter.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    Win32k is not a problem. When the crash itself cannot find any specific cause of the crash, it says that it is caused by win32k. You shouldnot rename or anything to win32k. Doing it will never help you.

    Have you tried to switch the graphics from the Graphics card to the onboard graphics?

    And, follow Troubleshooting Windows 7 Failure to Start. as gregrocker suggested. It should recover the error 0x490.
      My Computer

  10.    #10

    Computerhelper said:

    Right now I have restarted windows using msconfig's option to only have the basic stuff(2nd option on the general tab). I did not know one could have msconfig on at the command prompt, cool!
    Uncheck everything in Startup tab, and then in Services tab after Hiding All MS services.

    Only after determining if this has helped should you then add back your AV to see if it remains stable. Nothing else is needed to start with Win7. This is not XP.

    If this is still the bloated Samsung preinstall larded with sponsored bloatware and duplicate utilities that smother Win7, then I would Clean Reinstall - Factory OEM Windows 7 to get native Win7 performance. At the minimum I'd Clean Up Factory Bloatware
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:15.
Find Us