Windows 7 Blue Screen on Compaq Presario Desktop

Topic

New Reply

My computer is a desktop compaq presario running windows 7 64 bit. is only 7 months old. Recently I noticed it would say recovered from serious error and then when I checked the details, this is what it said:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 1
BCP1: 000000007742FDCA
BCP2: 0000000000000000
BCP3: 000000000000FFFC
BCP4: FFFFF88008227CA0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:WindowsMinidump71810-21231-01.dmp
C:UsersJenniferAppDataLocalTempWER-52884-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

I don’t know if it means my hard drive is already going on me or have others had this similar problem and what could be the fix? I have done various scans for errors/viruses etc and it never finds anything wrong. I’m puzzled. Hopefully I can figure this out before my 1 year warranty is up.

Reply | Quote

Replies

My computer is a desktop compaq presario running windows 7 64 bit. is only 7 months old. Recently I noticed it would say recovered from serious error and then when I checked the details, this is what it said:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 1
BCP1: 000000007742FDCA
BCP2: 0000000000000000
BCP3: 000000000000FFFC
BCP4: FFFFF88008227CA0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:WindowsMinidump71810-21231-01.dmp
C:UsersJenniferAppDataLocalTempWER-52884-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

I don’t know if it means my hard drive is already going on me or have others had this similar problem and what could be the fix? I have done various scans for errors/viruses etc and it never finds anything wrong. I’m puzzled. Hopefully I can figure this out before my 1 year warranty is up.

jandjjobst,
Hello,
I just want to give you a link ..as i have had similar “unexpected Shutdowns” “Blue Screens” also and a tool was recommended that will help identify the problem “BlueScreenView” http://www.nirsoft.net/utils/blue_screen_view.html download and run …and when and if your “OS” throws another “Blue Screen” at least you will have a “tool” to help identify the cause . My problem was solved by running “chkdsk C:/r” … found “corrupt attribute record” and fixed the problem. Regards Fred

Reply | Quote

jandjjobst,
Hello,
I just want to give you a link ..as i have had similar “unexpected Shutdowns” “Blue Screens” also and a tool was recommended that will help identify the problem “BlueScreenView” http://www.nirsoft.n…creen_view.html download and run …and when and if your “OS” throws another “Blue Screen” at least you will have a “tool” to help identify the cause . My problem was solved by running “chkdskr” … found “corrupt attribute record” and fixed the problem. Regards Fred

Fred, hello

Do I have to run from my System Repair DVD to get to the command prompt to run chkdsk r? It does not seem to run from a command prompt from within Windows even with Administrator privledges. Thanks. Ted

Reply | Quote

Fred, hello

Do I have to run from my System Repair DVD to get to the command prompt to run chkdsk /r? It does not seem to run from a command prompt from within Windows even with Administrator privledges. Thanks. Ted

Ted ,
Hello… Sorry my bad for not fully explaining and showing the wrong command ( ) . to run “chkdsk/r” you have to specify which drive letter you want to check ex. chkdsk C:/r.Also as you have stated you must run chkdsk as an administrator. and it will then run when you restart your “OS” For an explanation of the options run chkdsk/? Regards Fred

Reply | Quote

Files that help describe the problem:
C:WindowsMinidump71810-21231-01.dmp

Please navigate to: C:WindowsMinidump folder and select a few of the most recent .dmp files then Right Click > Send To > Compressed (zipped) folder

Then upload the file to thread

”chkdsk/r” you have to specify which drive letter you want to check

Be aware that the /r switch is quite comprehensive. In the fact that it can take several hours for it to complete opposed to the more common place /f switch used for quick checks of the file system integrity.

Reply | Quote

Be aware that the /r switch is quite comprehensive. In the fact that it can take several hours for it to complete opposed to the more common place /f switch used for quick checks of the file system integrity.

Josh,
Hello… Yes i was just thinking the exact same …and was about to post that warning…. beat me to it Regards fred

Reply | Quote

Thanks I will try that. It seems to happen about once a week. Will keep you posted and welcome any other comments.

Reply | Quote

My computer is a desktop compaq presario running windows 7 64 bit. is only 7 months old.

Other than the fact that my own Presario is eight months old, I have the same computer you do. However, I’ve never had a Blue Screen of Death. I don’t know if that helps you any.

Reply | Quote

Ok, my computer finally blue screened again and I used the blue screen program to tell me what went wrong. It said the cause was a kernel. Specifically ntoskrnl.exe in the windowssystem32 file path. Now what do I do about it??? How do I fix it?? Im not really sure how to use the bluescreen program or what to do from here.

Also it says in the bluescreen program under Bug string check:APC_INDEX_MISMATCH

Reply | Quote

Here are some related info it showed in the program:

PSHED.dll fffff880`00cbd000 fffff880`00cd1000 0x00014000 13/07/2009 7:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:Windowssystem32PSHED.dll
ntoskrnl.exe ntoskrnl.exe+6fb69 fffff800`02a12000 fffff800`02fee000 0x005dc000 27/02/2010 1:55:23 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation C:Windowssystem32ntoskrnl.exe
Afc.sys fffff880`03d9a000 fffff880`03da3000 0x00009000 11/07/2006 11:48:20 PM Arcsoft(R) ASPI Shell Arcsoft(R) ASPI Shell 1, 0, 0, 2 Arcsoft, Inc. C:Windowssystem32driversAfc.sys
ATMFD.DLL fffff960`00910000 fffff960`00971000 0x00061000 Adobe Type Manager Windows NT OpenType/Type 1 Font Driver 5.1 Build 228 Adobe Systems Incorporated C:Windowssystem32ATMFD.DLL

Reply | Quote

Hi jandjjobst ,

The kernel error can be caused by hardware or software issues as this article from MS indicates . The article lays out steps to take in troubleshooting the problem.

Your hard drive is one possible source of the problem, as well as your system memory. You could run the Windows 7 built in memory check utility. Type memory in the Start menu search box and press enter. You will need to reboot for the memory test to begin. You could also download Memtest86+ to run a lengthy memory check.

Your hard disk manufacturer has free utility downloads to thoroughly check the health of your hard disk. If you have imaging software, it would be best to create a backup image of your disk in case it is about to die. You could use Windows Backup to do a quick image backup without having to buy or download anything at this time.

Another Windows 7 tool you can use is the Reliability Monitor . Type reliability in the Start menu search box and press enter to view reliability history . This tool provides a graphic display of Windows 7 stability over time. It displays application failures, Windows failures, miscellaneous failures, warnings, and information. Click on any of the red failure icons for info identifying the failures (it may provide the specific source of the failure, as well as the date and time it occurred).

Reply | Quote

Please navigate to: C:WindowsMinidump folder and select a few of the most recent .dmp files then Right Click > Send To > Compressed (zipped) folder

Then upload the file to thread

Here are some related info it showed in the program:

PSHED.dll fffff880`00cbd000 fffff880`00cd1000 0x00014000 13/07/2009 7:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:Windowssystem32PSHED.dll
ntoskrnl.exe ntoskrnl.exe+6fb69 fffff800`02a12000 fffff800`02fee000 0x005dc000 27/02/2010 1:55:23 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation C:Windowssystem32ntoskrnl.exe
Afc.sys fffff880`03d9a000 fffff880`03da3000 0x00009000 11/07/2006 11:48:20 PM Arcsoft(R) ASPI Shell Arcsoft(R) ASPI Shell 1, 0, 0, 2 Arcsoft, Inc. C:Windowssystem32driversAfc.sys
ATMFD.DLL fffff960`00910000 fffff960`00971000 0x00061000 Adobe Type Manager Windows NT OpenType/Type 1 Font Driver 5.1 Build 228 Adobe Systems Incorporated C:Windowssystem32ATMFD.DLL

To troubleshoot the issue the logical step is to provide crash logs in full via upload please. If you need assistance doing this please ask

From the limited information available in the above quotation it appears it could be a driver issue with Afc.sys which is a 3rd party driver to Windows 7.

Reply | Quote