Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: blue screen blues


26 Aug 2011   #1

Windows 7 Home Premium 64 bit
 
 
blue screen blues

Hi There

I have a Compaq Presario CQ61 Notebook PC
it has an Intel Celeron CPU 900 @ 2.20 GHZ 2.19 GHz
2gb of installed memory

I have the Windows 7 Home Premium 64 bit that came with it. Service Pack 1.
I got it brand new in about March 2010.

Just the last couple of days have seen a sudden outbreak of blue screen blues. I get this message:

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

Additional information about the problem:
BCCode: 7a
BCP1: FFFFF6FC40008F60
BCP2: FFFFFFFFC0000185
BCP3: 0000000025D8F860
BCP4: FFFFF880011ECCD0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082611-41231-01.dmp
C:\Users\Ned\AppData\Local\Temp\WER-2124172-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


My System SpecsSystem Spec
.

26 Aug 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by YorkshireNed View Post
Hi There

I have a Compaq Presario CQ61 Notebook PC
it has an Intel Celeron CPU 900 @ 2.20 GHZ 2.19 GHz
2gb of installed memory

I have the Windows 7 Home Premium 64 bit that came with it. Service Pack 1.
I got it brand new in about March 2010.

Just the last couple of days have seen a sudden outbreak of blue screen blues. I get this message:

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

Additional information about the problem:
BCCode: 7a
BCP1: FFFFF6FC40008F60
BCP2: FFFFFFFFC0000185
BCP3: 0000000025D8F860
BCP4: FFFFF880011ECCD0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082611-41231-01.dmp
C:\Users\Ned\AppData\Local\Temp\WER-2124172-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


Memory corruption caused by a disk hardware error


BugCheck 7A, {fffff6fc40008f60, ffffffffc0000185, 25d8f860, fffff880011eccd0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff80002f10278
Probably caused by : memory_corruption



KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.
Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or xC0000185 ,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40008f60, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)


Since it appears to be a disk error I would run chkdsk first.

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

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.


B- 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"


C-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.





Second since there was memory corruption I would run these two tests


1-Memtest.


*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+

2-Driver verifier


Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
Reply

 blue screen blues




Thread Tools



Similar help and support threads for2: blue screen blues
Thread Forum
Blue Screen Error but no actual blue screen pops up BSOD Help and Support
Solved Blues screen 0x0000008e BSOD Help and Support
External HDD causes blues screen of death Hardware & Devices
Blues Screen Can't Figure it out BSOD Help and Support
Blue Screen Blues... BSOD Help and Support
2 640g blacks on R0, 2 500g blues or 2 640g blues? Hardware & Devices
Blue Screen Blues BSOD Help and Support

Our Sites

Site Links

About Us

Find 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:27 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33