2057 bluescreen on boot

Page 1 of 2 12 LastLast

  1. Posts : 22
    Win 7 Ult. 32bit
       #1

    2057 bluescreen on boot


    Hi guys
    Love the forum. You guys seem to be the main peps to come see, about this kind of thing.
    Thanks in advance for any help you can provide btw.

    Anyways, been getting intermittent blue screen errors on boot. Have to run a repair/restore every time the problems occur.

    Been getting this error on successful return to windows


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 6b
    BCP1: 00000000
    BCP2: 00000000
    BCP3: 00000000
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\090110-38719-01.dmp
    C:\Users\Asiyreh\AppData\Local\Temp\WER-72509-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    Problems seem to occur when anything is hanging in the background before shutdown and most frequently when I’m using Windows Live movie maker.

    The windows version is Win 7 32bit – Ult
    The original Os was Win Vista home – OEM
    The systems a Hp 6735s laptop it’s about 2 years old maybe more...
    The Win 7 partitions fairly new – maybe 2-3 months old.


    Thanks guys you’re the best.
      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #2

    Hi Asiyreh, welcome to the forum. I am sorry to hear you are having problems. Can you upload the actual mini dump file to us? Please read the following tutorial:

    https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
      My Computer


  3. Posts : 22
    Win 7 Ult. 32bit
    Thread Starter
       #3

    Thanks for the response Carl.

    Ok guys please don’t hate me, I’m probably being stupid, but I thought I’d actually followed those instructions.
    I noticed the directions last night, which told me to download a lil program/applet. Run that, which outputs a folder of data.

    Run another health report thingee, save the file as a Html Doc.

    Zip the two of them up together and attach them to the post.

    Which I did.... I think...up there ^

    Please don’t beat, I’m just a lil n00bee
      My Computer


  4. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #4

    We won't beat you; maybe rough you up a little! . Just kidding. I think the problem may have been with rar. Usually when you crash during the boot process it is a hardware issue. I looked at your five most recent dumps. The latest dump is error code 124 which is definitely a hardware issue. The next five are nearly identical and all error code 6B.

    Error code 6B, PROCESS1_INITIALIZATION_FAILED. Usual causes are Hard drive, Cables, Missing boot files, Disabled drive.

    Error code 124- [2-Int] Stop 0x124 - what it means and what to try


    First check your hard drive's cable connections. Make sure they are secure.

    Next -
    Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

    Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

    Copy/paste the results into your next post.


    You also have some older drivers on your system. Update these drivers, preferably from the manufactures' websites.
    AtiPcie.sys Tue May 05 11:00:16 2009
    hpdskflt.sys Wed Jul 08 14:40:00 2009
    nvraid.sys Wed May 20 02:43:36 2009


    Because hard drive is mentioned in the causes, start by updating nvraid.sys.

    How To Find Drivers:

    - I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.


    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page:
    Drivers and Downloads


    If you need help with the drivers, please post and ask. Once you have updated the drivers, reboot and run your computer. If you get another BSOD up load it and enable Driver Verifier.

    Driver Verifier - Enable and Disable

    Upload any dumps generated by Driver Verifier.

    Last edited by CarlTR6; 02 Sep 2010 at 22:47.
      My Computer


  5. Posts : 22
    Win 7 Ult. 32bit
    Thread Starter
       #5



    Dude...

    Ammmm ok. Thanks Carl.

    *Shuffles feet nerverously.

    So what do I do again now?

    Lol just kidding
    Ammm K, amhhamm, right... I give it a go.
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #6

    If you need help or further guidance, don't be afraid to ask. We won't hit you (too hard) :) Seriously, anything that you don't understand, just ask.
      My Computer


  7. Posts : 22
    Win 7 Ult. 32bit
    Thread Starter
       #7

    Lol thanks Carl for the help, and not hitting me, well at least not too hard.

    I'm just uploading the results of this chkdsk incase my system bombs out and I lose it.

    Checking file system on C:
    The type of the file system is NTFS.

    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 5)...
    81152 file records processed. File verification completed.
    56 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    109204 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
    81152 file SDs/SIDs processed. Cleaning up 525 unused index entries from index $SII of file 0x9.
    Cleaning up 525 unused index entries from index $SDH of file 0x9.
    Cleaning up 525 unused security descriptors.
    Security descriptor verification completed.
    14027 data files processed. CHKDSK is verifying Usn Journal...
    33613944 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    81136 files processed. File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    18270974 free clusters processed. Free space verification is complete.
    Windows has checked the file system and found no problems.

    96634879 KB total disk space.
    23329356 KB in 59153 files.
    38192 KB in 14028 indexes.
    0 KB in bad sectors.
    183431 KB in use by the system.
    65536 KB occupied by the log file.
    73083900 KB available on disk.

    4096 bytes in each allocation unit.
    24158719 total allocation units on disk.
    18270975 allocation units available on disk.

    Internal Info:
    00 3d 01 00 e8 1d 01 00 94 0f 02 00 00 00 00 00 .=..............
    95 01 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
    b0 f1 0a 00 50 01 0a 00 50 01 0a 00 00 00 0a 00 ....P...P.......

    Windows has finished checking your disk.
    Please wait while your computer restarts.
    I've been doing some "research" (fumbling around in the dark lol) into the drivers you've mentioned accidentally downloaded some driver finder program. Says it have updates for my graphics and the ATA drive.

    Nvidia however says that their driver for my laptop is a taylored version provided by Hp. True facts. However pretty sure I have the latest.

    Also can't really check the HDD cables as this is a laptop. But my vista partition is working fine.


    Need to sleep now again thank for the help Carl. I'll keep working away with those driver updates
      My Computer


  8. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #8

    It is true that laptop manufactures tailor the drivers for the laptop. You should get those drivers from from the laptop manufacturer when possible. Your check disk turned out fine. The hard drive is like not the problem. I believe there is an update for the nvraid driver.

    hpdskflt.sys is an HP driver - belonging to product Hewlett-Packard Corporation Mobile Data Protection System. It is a disk filter driver. You will have to update this one from HP.

    Go ahead and enable Driver Verifier. Let's see if it reveals a faulty driver.
      My Computer


  9. Posts : 22
    Win 7 Ult. 32bit
    Thread Starter
       #9

    Hmm enabled Driver Verifer using the options provided in the tutorial. Asked me to click finish and reboot to enable the verifer.


    Ok so did that, rebooted, doesn't seem to have done anything, apart from the fact that everythings reaaallllllllyyyyy slooooooowwwwwww and I can't access the task manager.

    Is it supposed to do anything? Or is there something else I need to do to get the driver report?

    Sorry guys this all new to me. Apoligies for being a big n00bee.
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    Just use you computer normally while driver verifier runs. If it finds a faulty driver, it will cause a BSOD and, hopefully, the dump will pinpoint the driver. After you have run Driver Verifier for about 36 hours, you can disable it.
      My Computer


 
Page 1 of 2 12 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 06:34.
Find Us