Windows 7 Ongoing BSOD errors

T

thespecialk

New Member
Joined
Apr 8, 2011
Messages
4
I'll try to streamline this explanation as much as possible.

I have an HP Pavilion all-in-one desktop that is just over 13 months old. Early last fall, it began having BSOD errors that were random, though infrequent. I did a few system restores shortly after they began, but it didn't fix the problem.

Over the course of a couple months, the problems intensified and I began attempting to square them away with HP tech support through the warranty. I've gone through numerous troubleshooting steps including updating drivers, diagnostics and a full system recovery (three times now in total). On the second attempt, I received a Code Purple error, which finally convinced HP to take in the machine for service. They re-tattooed the motherboard and fixed the Code Purple, but never fixed the original BSOD error (by this time I was pretty convinced it was a hard drive issue).

In any event, before these BSOD errors, I'll usually here a couple of clicks and a weezing sound as if the hard drive is sputtering. Usually within 30 seconds of that noise, I'll get the BSOD error. The computer will shut down and often it won't reboot for several hours after, showing a "operating system not found" message.

I've been fighting with HP to get the problem fixed. They kept having me do more troubleshooting even though I was convinced it was a hardware issue (but they couldn't come up with anything from diagnostics). Finally after the warranty expired, I called back but then they tried to pull the "out of warranty" card on me. After some gentle pleading (read: yelling) they took the machine back into the service center and replaced the motherboard. However, I just got it back and it's still acting up. I think it's the hard drive and they're going to take it back into service, but frankly I don't trust these folks to fix it.

So in the event someone here can make better sense of things than they can, I've attached the unique BCcodes I've received over the past few months and attached the crash dump files.

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

Extra information about the problem
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA80041E7550
BCP3: FFFFFA80041E7830
BCP4: FFFFF80002B865D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8005534060
BCP3: FFFFFA8005534340
BCP4: FFFFF80002B915D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: 1000007e
BCP1: FFFFFFFFC0000006
BCP2: FFFFF8000292668A
BCP3: FFFFF880009A9808
BCP4: FFFFF880009A9070
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: 7a
BCP1: 0000000000000020
BCP2: FFFFFFFFC000009D
BCP3: FFFFFA800419F078
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: 6b
BCP1: FFFFFFFFC000009D
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: 7a
BCP1: FFFFF6FC40007008
BCP2: FFFFFFFFC00000C0
BCP3: 0000000044A8F860
BCP4: FFFFF88000E01000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800537EB30
BCP3: FFFFFA800537EE10
BCP4: FFFFF80002D7D2D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

The latter one (F4) is the most common. It's happened the most frequent of the listed errors. These are the ones I've received since the drive was last re-imaged in January. There has been a total of about 30 crashes in these 3 months plus.

I believe I have attached the necessary information. Thanks in advance for all your help!
 

Attachments

  • 110408053116-81829.zip
    110408053116-81829.zip
    145.3 KB · Views: 272
  • Spd Slot No. 2.webp
    26.9 KB · Views: 581
  • CPU-Z.webp
    32.6 KB · Views: 492
  • Memory.webp
    20.7 KB · Views: 482
  • Spd.webp
    26.6 KB · Views: 541
Solution
RAM is set wrong,

currently: 600Mhz 6-6-6-18
rated: 800Mhz 6-6-6-18 1.8v



1. Set the memory right
800Mhz 6-6-6-18 1.8v


2. Check for your motherboard updates :
AtiPcie.sys Tue May 05 11:00:22 2009
Link Removed


3. Symantec is old, 2009, update it.



CRASH DUMPS

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\031811-67766-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite...
Sort by date Sort by votes
RAM is set wrong,

currently: 600Mhz 6-6-6-18
rated: 800Mhz 6-6-6-18 1.8v



1. Set the memory right
800Mhz 6-6-6-18 1.8v


2. Check for your motherboard updates :
AtiPcie.sys Tue May 05 11:00:22 2009
Link Removed


3. Symantec is old, 2009, update it.



CRASH DUMPS

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\031811-67766-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Fri Mar 18 13:35:59.786 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:18.548
Loading Kernel Symbols
...................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6B, {ffffffffc000009d, 2, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PsLocateSystemDlls+bd )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: ffffffffc000009d, Indicates the NT status code that caused the failure.
Arg2: 0000000000000002, (reserved)
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x6B

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ed311d to fffff80002a8d740

STACK_TEXT:  
fffff880`009a99f8 fffff800`02ed311d : 00000000`0000006b ffffffff`c000009d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a9a00 fffff800`02fbcb3d : fffff800`00814130 00000000`00000002 00000000`00000000 fffff800`02c07e80 : nt!PsLocateSystemDlls+0xbd
fffff880`009a9a40 fffff800`02fbfcec : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`00814130 : nt!IoInitSystem+0x85d
fffff880`009a9b40 fffff800`02f10219 : 00000000`00000000 fffffa80`036c91c0 00000000`00000080 fffffa80`036c9740 : nt!Phase1InitializationDiscard+0x129c
fffff880`009a9d10 fffff800`02d307c6 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02a6bc19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02a6bc26 : fffff800`02c07e80 fffffa80`036c91c0 fffff800`02c15c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PsLocateSystemDlls+bd
fffff800`02ed311d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PsLocateSystemDlls+bd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x6B_nt!PsLocateSystemDlls+bd

BUCKET_ID:  X64_0x6B_nt!PsLocateSystemDlls+bd

Followup: MachineOwner
---------



DRIVERS

Code: 
start             end                 module name
fffff880`00f4b000 fffff880`00fa2000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00d9f000 fffff880`00db3000   amdsata  amdsata.sys  Fri Feb 05 21:03:55 2010 (4B6CCE0B)
fffff880`01092000 fffff880`0109d000   amdxata  amdxata.sys  Fri Feb 05 21:03:57 2010 (4B6CCE0D)
fffff880`00e8d000 fffff880`00e96000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d75000 fffff880`00d9f000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`017f3000 fffff880`017fb000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:22 2009 (4A005486)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01400000 fffff880`01430000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d17000 fffff880`00d75000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01488000 fffff880`014fb000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01430000 fffff880`0143e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`015d6000 fffff880`015ec000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01448000 fffff880`0145c000   dump_amdsata dump_amdsata.sys Fri Feb 05 21:03:55 2010 (4B6CCE0B)
fffff880`0143e000 fffff880`01448000   dump_diskdump dump_diskdump.sys Mon Jul 12 23:32:05 2010 (4C3BDE35)
fffff880`0145c000 fffff880`0146f000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`010e9000 fffff880`010fd000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0109d000 fffff880`010e9000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0150c000 fffff880`01516000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0159c000 fffff880`015d6000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02ffa000 fffff800`03043000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`017ea000 fffff880`017f3000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bd2000 fffff800`00bdc000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`013e2000 fffff880`013fc000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00cf6000 fffff880`00d03000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00cd0000 fffff880`00cea000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fab000 fffff880`00fb5000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01164000 fffff880`011c2000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`017d8000 fffff880`017ea000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01686000 fffff880`01778000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01778000 fffff880`017d8000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02a1d000 fffff800`02ffa000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`0123f000 fffff880`013e2000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00fb5000 fffff880`00fe8000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00cc0000 fffff880`00cd0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`014fb000 fffff880`0150c000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00d03000 fffff880`00d17000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01562000 fffff880`0159c000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01675000 fffff880`0167d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01030000 fffff880`01092000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`010fd000 fffff880`01164000   SYMEFA64 SYMEFA64.SYS Tue Jun 23 17:52:39 2009 (4A414EA7)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`00fe8000 fffff880`00ff5000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00e15000 fffff880`00e2a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01516000 fffff880`01562000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e98000 fffff880`00f3c000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f3c000 fffff880`00f4b000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fa2000 fffff880`00fab000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
 
Upvote 0 Downvote
Solution
I greatly appreciate the assistance. If I may indulge you, two brief follow-ups:

1. I have entered the BIOS setup utility and don't see anywhere the adjust the DRAM frequency. Where can this be done? Where memory is listed on the main tab, the frequency settings aren't listed and to the extent memory settings are shown, there is no way to access them (they're grayed out). Am I looking in the wrong place or what should I be looking for specifically?

2. Regarding the driver: I have located my chipset from the AMD page you linked, using their search function. Will I be able to run that driver installation normally from Windows?
 
Upvote 0 Downvote
I am still trying to learn how to read dump files. Since cybercore is experienced in this type of thing, I have a couple of questions. I have not been able to get the drivers list you show using WinDBG, but I did see some things that make me wonder.

On one dump file it seems to refer to memory corruption. Is that RAM or possibly memory on a page file on the hard drive?

It also seems to indicate something about volmgrx. Is this related to a hard drive or controller problem?
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
Ultimate Guide to Troubleshooting Windows Unexpected Restarts & BSOD Errors
Replies
0
Views
268
ChatGPT
  • Featured
  • Article Article
How to Fix and Prevent Unexpected Windows Restarts and BSOD Errors
Replies
0
Views
310
ChatGPT
  • Featured
  • Article Article
Critical BIOS Update for ASUS Laptops Fixes Windows 11 BSOD Errors
Replies
1
Views
676
ChatGPT
  • Solved
Windows 10 Recurring BSOD Errors After Windows 10 Upgrade: Seeking Help with Minidump Analysis
2
Replies
31
Views
13K
kemical
  • Question Question
Windows 10 BSOD Errors I've tried everything please help
Replies
1
Views
2K
Neemobeer