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: Random lockups and BSODs

05 Oct 2010   #11
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Some folks have found that uninstalling Catalyst worked for them. Maybe the latest version works better with Win 7.
[quote]
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Error code 74, BAD_SYSTEM_CONFIG_INFO. Usual causes - System hive corruption, Missing registry keys/values
[/code]

Have you used a registry cleaner or any third party tuneup utility program?

I had not seen this driver showing up before: ASACPI.sys Sun Mar 27 22:30:36 2005.
Quote:
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
While this driver is a big problem, I think you have other things going on. Try running SFC /SCANNOW:

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Your next step will be to do a repair install. Carefully read and follow this tutorial. You may opt to do a clean install. If you do, back up your data.

Repair Install

Clean Install Windows 7

Update that driver first and then try SFC. Let us know if you need help.

Code:
Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50
Debug session time: Sun Oct  3 17:58:47.455 2010 (GMT-4)
System Uptime: 0 days 1:50:50.218
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff85, 1, fffff80002b7a890, 0}


Could not read faulting driver name
Probably caused by : hardware ( nt!AlpcpExposeAttributes+140 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffff85, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002b7a890, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab30e0
 ffffffffffffff85 

FAULTING_IP: 
nt!AlpcpExposeAttributes+140
fffff800`02b7a890 004885          add     byte ptr [rax-7Bh],cl

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800747f870 -- (.trap 0xfffff8800747f870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80054afa60
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b7a890 rsp=fffff8800747fa00 rbp=fffffa80054afa60
 r8=0000000000000020  r9=00000000032aff00 r10=0000000000000000
r11=00000000032afd68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!AlpcpExposeAttributes+0x140:
fffff800`02b7a890 004885          add     byte ptr [rax-7Bh],cl ds:fd40:ffffffff`ffffff85=??
Resetting default scope

MISALIGNED_IP: 
nt!AlpcpExposeAttributes+140
fffff800`02b7a890 004885          add     byte ptr [rax-7Bh],cl

LAST_CONTROL_TRANSFER:  from fffff800028fbf14 to fffff8000287b740

STACK_TEXT:  
fffff880`0747f708 fffff800`028fbf14 : 00000000`00000050 ffffffff`ffffff85 00000000`00000001 fffff880`0747f870 : nt!KeBugCheckEx
fffff880`0747f710 fffff800`0287982e : 00000000`00000001 fffff8a0`0b3d0d00 00000001`00000000 fffff880`009e8180 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`0747f870 fffff800`02b7a890 : 00000000`032afd00 fffffa80`00000010 fffffa80`0478ab01 00000000`032afd00 : nt!KiPageFault+0x16e
fffff880`0747fa00 fffff800`02b7bbe2 : 00000000`00000000 00000000`0001bf01 00000000`032afd40 00000000`00000001 : nt!AlpcpExposeAttributes+0x140
fffff880`0747fa60 fffff800`02b7d006 : fffffa80`054afa60 00000000`00010000 00000000`00010000 fffffa80`054afa60 : nt!AlpcpReceiveMessage+0x3ef
fffff880`0747fb00 fffff800`0287a993 : fffffa80`05c96b60 fffff880`0747fca0 00000000`032afc98 00000000`032afd88 : nt!NtAlpcSendWaitReceivePort+0x1e6
fffff880`0747fbb0 00000000`772205aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`032afc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772205aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!AlpcpExposeAttributes+140
fffff800`02b7a890 004885          add     byte ptr [rax-7Bh],cl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!AlpcpExposeAttributes+140

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50
Debug session time: Mon Oct  4 17:10:33.097 2010 (GMT-4)
System Uptime: 0 days 0:00:09.470
Loading Kernel Symbols
...............................................................
...............
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 74, {2, fffff88003b87b20, 5, ffffffffc000014c}

Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )

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

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

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: fffff88003b87b20, (reserved)
Arg3: 0000000000000005, (reserved)
Arg4: ffffffffc000014c, usually the NT status code.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x74

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d03cda to fffff80002885740

STACK_TEXT:  
fffff880`03b87a68 fffff800`02d03cda : 00000000`00000074 00000000`00000002 fffff880`03b87b20 00000000`00000005 : nt!KeBugCheckEx
fffff880`03b87a70 fffff800`02b29c06 : 00000000`01d23e1b fffffa80`04efeb60 00000000`00000080 fffffa80`03af49e0 : nt!CmpLoadHiveThread+0x23a
fffff880`03b87d40 fffff800`02863c26 : fffff800`029ffe80 fffffa80`04efeb60 fffffa80`04f00060 fffff880`01014bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`03b87d80 00000000`00000000 : fffff880`03b88000 fffff880`03b82000 fffff880`03b86ea0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpLoadHiveThread+23a
fffff800`02d03cda cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!CmpLoadHiveThread+23a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

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

3: kd> lmtsmn
start             end                 module name
fffff880`00f57000 fffff880`00fae000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02b6a000 fffff880`02bf4000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03db0000 fffff880`03dc5000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00ff4000 fffff880`00fff000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e9a000 fffff880`00ea3000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d6a000 fffff880`00d94000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04604000 fffff880`04dbf000   atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010 (4C75C7AA)
fffff880`03c00000 fffff880`03c4a000   atikmpag atikmpag.sys Wed Aug 25 21:20:56 2010 (4C75C178)
fffff880`01452000 fffff880`0145a000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:22 2009 (4A005486)
fffff880`02abe000 fffff880`02ac5000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03d79000 fffff880`03d8a000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02a8b000 fffff880`02ab5000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`011a6000 fffff880`011d6000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d0c000 fffff880`00d6a000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`012a5000 fffff880`01318000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01216000 fffff880`01224000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03d5b000 fffff880`03d79000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03d4c000 fffff880`03d5b000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01200000 fffff880`01216000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01224000 fffff880`0122d000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`013f3000 fffff880`013ff000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`011d6000 fffff880`011e9000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`00de0000 fffff880`00df4000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00d94000 fffff880`00de0000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01329000 fffff880`01333000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`013b9000 fffff880`013f3000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02df1000 fffff800`02e3a000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`015f1000 fffff880`015fa000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bc7000 fffff800`00bd1000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`0128b000 fffff880`012a5000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015b4000 fffff880`015df000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00ceb000 fffff880`00cf8000   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`02b23000 fffff880`02b2e000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb7000 fffff880`00fc1000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0122d000 fffff880`0128b000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03d41000 fffff880`03d4c000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015df000 fffff880`015f1000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01462000 fffff880`01554000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02a74000 fffff880`02a83000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02a00000 fffff880`02a45000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01554000 fffff880`015b4000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02b2e000 fffff880`02b3f000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03d35000 fffff880`03d41000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02815000 fffff800`02df1000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01003000 fffff880`011a6000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02ab5000 fffff880`02abe000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02a4e000 fffff880`02a74000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e0d000 fffff880`00e22000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00fc1000 fffff880`00ff4000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e93000 fffff880`00e9a000   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`01318000 fffff880`01329000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00cf8000 fffff880`00d0c000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`03ce4000 fffff880`03d35000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02b08000 fffff880`02b11000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02b11000 fffff880`02b1a000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02b1a000 fffff880`02b23000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0137f000 fffff880`013b9000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0144a000 fffff880`01452000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`02b5d000 fffff880`02b6a000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02b3f000 fffff880`02b5d000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03cd0000 fffff880`03ce4000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03d8a000 fffff880`03db0000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`00e00000 fffff880`00e0d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02ac5000 fffff880`02ad3000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02ad3000 fffff880`02af8000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e22000 fffff880`00e37000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e37000 fffff880`00e93000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01333000 fffff880`0137f000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03cb5000 fffff880`03cd0000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02af8000 fffff880`02b08000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ea4000 fffff880`00f48000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f48000 fffff880`00f57000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02a45000 fffff880`02a4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`00fae000 fffff880`00fb7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)





My System SpecsSystem Spec
.
05 Oct 2010   #12
jonesmark

Win7 64-bit
 
 

Ok thanks - I will update the ASACPI.sys driver and run SFC this evening, I'll let you know how I get on.

EDIT: Note I haven't used a registry cleaner or any third party tuneup utility program.
My System SpecsSystem Spec
05 Oct 2010   #13
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I hope that solves the problem. The error code 74 concerns me. I will be looking for your update. I am glad to know that you have not used a registry cleaner nor a tuneup utility.
My System SpecsSystem Spec
.

05 Oct 2010   #14
jonesmark

Win7 64-bit
 
 

Hi. I updated the ASACPI.sys driver and run SFC. SFC completed and it said that it found corrupt files and successfully repaired them. I ran the

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

command to pull all the "[SR]" log entries from the CBS.log file into a new log file, which is attached.

It contains a *lot* of files that were found to be corrupt and it repaired them. Any idea how so many files could have become corrupted ?

Thanks again !
My System SpecsSystem Spec
05 Oct 2010   #15
CarlTR6

Windows 7 Ultimate 32 bit
 
 

That is a lot of files; but the good thing is SFC repaired them. A lot of things can cause file corruption from an unexpected power loss to a failing hard drive. You can test your drive using Check Disk.
Quote:
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).

Copy/paste the results into your next post.
Glad you got ASACPI.sys updated. Let's see how your system does now with ASACPI.sys updated and the files repaired.
My System SpecsSystem Spec
06 Oct 2010   #16
jonesmark

Win7 64-bit
 
 

Hi there. I left my PC running all yesterday and last night whilst it was patching and updating LOTRO - since this takes a long time I left it overnight. This morning when I looked at all, the PC seemed to be still running (had power, fans going round, motheboard LEDs on ok EXCEPT for the HDD LED which was not flashing) but the monitor was showing a blank screen as though it had no signal, and the PC wouldn't wake up by pressing keys or moving the mouse.

I hit the case reset switch and booted into Win 7 safe mode ok, which it did, and told me that Windowns had suffered another BSOD (it also created file 100610-30232-01.dmp).

I've run the Windows_NT6_BSOD_v3.03_jcgriff2_ application and the Perfmon report, the results of these are zipped up and attached as usual.

I also ran SFC/ SCANNOW, it completed 100% and said that Windows Resource Protection did not find any integrity violations.

EDIT:
- Note I've not checked my HDDs yet, maybe that's something to do next ?

- For RAM since I have 2x2GB sticks, I was maybe going pull 1 of my RAM sticks out and put the remaining 1 in another empty motherboard slot, test, and then try with the other stick in on its own, and then test.

- I have 2 HDDs in my PC, an older 128GB drive with Win on it, and a newer 1TB drive for games, music, photos etc. If it's maybe a failing HDD, I was going to take the old 128GB drive out and do a clean install of Win 7 on the newer 1TB drive.

Please let me know your thoughts/ advice, and thanks again !
My System SpecsSystem Spec
06 Oct 2010   #17
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote:
Error code 74, BAD_SYSTEM_CONFIG_INFO. Usual causes: System hive corruption, Missing registry keys/values.
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt. This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present. (i.e. somebody used regedt32 to delete something
that they shouldn't have) Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.

Error code D1, BAD_SYSTEM_CONFIG_INFO. Usually caused by a driver.
Code:
Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50
Debug session time: Mon Oct  4 17:10:33.097 2010 (GMT-4)
System Uptime: 0 days 0:00:09.470
Loading Kernel Symbols
...............................................................
...............
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 74, {2, fffff88003b87b20, 5, ffffffffc000014c}

Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )

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

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

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: fffff88003b87b20, (reserved)
Arg3: 0000000000000005, (reserved)
Arg4: ffffffffc000014c, usually the NT status code.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x74

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d03cda to fffff80002885740

STACK_TEXT:  
fffff880`03b87a68 fffff800`02d03cda : 00000000`00000074 00000000`00000002 fffff880`03b87b20 00000000`00000005 : nt!KeBugCheckEx
fffff880`03b87a70 fffff800`02b29c06 : 00000000`01d23e1b fffffa80`04efeb60 00000000`00000080 fffffa80`03af49e0 : nt!CmpLoadHiveThread+0x23a
fffff880`03b87d40 fffff800`02863c26 : fffff800`029ffe80 fffffa80`04efeb60 fffffa80`04f00060 fffff880`01014bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`03b87d80 00000000`00000000 : fffff880`03b88000 fffff880`03b82000 fffff880`03b86ea0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpLoadHiveThread+23a
fffff800`02d03cda cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!CmpLoadHiveThread+23a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

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

Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
...Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
......Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff80000c9b6e0, 2, 0, fffff880016e777b}

Probably caused by : tcpip.sys ( tcpip!ConvertFieldToAddr+2b )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff80000c9b6e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016e777b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aaf0e0
 fffff80000c9b6e0 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!ConvertFieldToAddr+2b
fffff880`016e777b 833800          cmp     dword ptr [rax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9b200 -- (.trap 0xfffff80000b9b200)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80000c9b6e0 rbx=0000000000000000 rcx=000000000000000d
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016e777b rsp=fffff80000b9b390 rbp=0000000000000000
 r8=fffff80000b9b6e0  r9=000000000000c082 r10=0000000000000000
r11=00000000000000ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
tcpip!ConvertFieldToAddr+0x2b:
fffff880`016e777b 833800          cmp     dword ptr [rax],0 ds:fffff800`00c9b6e0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002878469 to fffff80002878f00

STACK_TEXT:  
fffff800`00b9b0b8 fffff800`02878469 : 00000000`0000000a fffff800`00c9b6e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9b0c0 fffff800`028770e0 : 00000001`00000001 00000000`0000000d 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9b200 fffff880`016e777b : 00000000`00000000 00000000`00000000 ffff0080`01cf30c1 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9b390 fffff880`01700c1d : fffff800`00b9b6c8 fffff800`00b9b6e0 fffff800`00b9b850 fffff800`00b9b6d0 : tcpip!ConvertFieldToAddr+0x2b
fffff800`00b9b3d0 fffff880`01700fbd : fffff800`00b9b820 00000000`00000000 00000000`00005000 fffff880`0588009a : tcpip!IndicateDropAudit+0x12d
fffff800`00b9b620 fffff880`016915dc : fffffa80`05113ae0 00000000`00000006 fffffa80`04f221a0 fffff880`01495a39 : tcpip!ShimIndicateDiscardNoClassify+0x5d
fffff800`00b9b670 fffff880`01632339 : fffffa80`04aac000 fffffa80`04ab0f00 00000000`00000014 fffff880`01494fbf : tcpip! ?? ::FNODOBFM::`string'+0xe597
fffff800`00b9ba40 fffff880`0163241d : fffffa80`04ab0f00 fffff800`00b9bce8 fffffa80`04aac000 fffff880`058800a2 : tcpip!InetInspectRespondDatagram+0x149
fffff800`00b9bbd0 fffff880`0167c4b0 : 00000000`00000000 fffffa80`04aac000 fffffa80`04949538 fffffa80`04949538 : tcpip!TcpDiscardReceive+0x6d
fffff800`00b9bc20 fffff880`0167bc17 : fffff880`058800a2 fffffa80`04aac000 00000000`00000000 fffff880`0165f300 : tcpip!TcpMatchReceive+0x5e0
fffff800`00b9bd70 fffff880`0165e3c7 : fffffa80`04aac000 fffffa80`04ab5e30 fffffa80`04ab5000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177
fffff800`00b9be20 fffff880`0165e499 : fffff800`00b9bfa0 fffff880`0176e9a0 fffff800`00b9bfb0 fffffa80`049217b0 : tcpip!IppDeliverListToProtocol+0x97
fffff800`00b9bee0 fffff880`0165e990 : fffffa80`04aac000 fffffa80`049e1860 00000000`00000000 fffff800`00b9bfa0 : tcpip!IppProcessDeliverList+0x59
fffff800`00b9bf50 fffff880`0165d821 : 00000000`0201a8c0 fffffa80`04aac000 fffff880`0176e9a0 00000000`05304301 : tcpip!IppReceiveHeaderBatch+0x231
fffff800`00b9c030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x651


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!ConvertFieldToAddr+2b
fffff880`016e777b 833800          cmp     dword ptr [rax],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!ConvertFieldToAddr+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc26e

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!ConvertFieldToAddr+2b

BUCKET_ID:  X64_0xD1_tcpip!ConvertFieldToAddr+2b

Followup: MachineOwner
---------
The dump showing the D1 error code corrupted. It blames tcpip.sys which is a Microsoft Driver. Usually when tcpip is blamed, the real cause is a third party antivirus or firewall program, an outdated network adapter driver, or a bad network adapter card.

You are running Windows Firewall which should not be a problem. Are you running Windows Defender or are you running Microsoft Security Essentials? If you are running Defender, download an install MSE. MSE will disable defender.

That said, the error code 74 troubles me. You posted earlier that you have not used a registry cleaner nor a tuneup utility. Have you edited the registry using regedit or any registry editor? The error code 74 dump implies there is something wrong with your registry.

At this point, I suggest a repair install: Repair Install
or a clean install: Clean Install Windows 7

Read these tutorials carefully and back up your data to another drive before attempting either method. If you have any questions, please post back. Let us know what you decide to do. If you would like, I can get another member of the team to take a look at this thread for a second opinion. That will certainly not hurt my feelings. Two or more sets of eyes are always better than one.
My System SpecsSystem Spec
06 Oct 2010   #18
jonesmark

Win7 64-bit
 
 

Hi there, thanks for the response.

I'm not using any antivirus at the moment.
I've not edited or changed the registry in anyway.

If it's easy, could you maybe ask another member of the team to have a look at this thread and the logs ? I trust you completely, so please don't think I mean anything bad by asking this, but I do like your suggestion of getting a second opinion, just to understand if there are any other things I should try or do

After that, I can try a repair install or a full install, no problem.

Do you think this could maybe be due to failing hardware, such as a HDD or motherboard ? Note the LAN port I am using is built into my motherboard, its not a separate card.

Thank you again !
My System SpecsSystem Spec
06 Oct 2010   #19
CarlTR6

Windows 7 Ultimate 32 bit
 
 

That does not insult me at all. I ask for help from other team members frequently. We all want to help the OP as best we can. I have asked for help and that help will come.
My System SpecsSystem Spec
06 Oct 2010   #20
jonesmark

Win7 64-bit
 
 

Thank you !
My System SpecsSystem Spec
Reply

 Random lockups and BSODs




Thread Tools




Similar help and support threads
Thread Forum
BSODs and random lockups
Been getting BSODs and lockups at random past few months, usually only once a day at max, though today I've locked up twice and figured time to try and get to the bottom of it. It seems like this happened after a driver update for my graphic card a few months ago (v320 or something like that,...
BSOD Help and Support
Random Restarts, Lockups, and BSODs
(Well then, as I was beginning to type this, my computer locked up once, then after rebooting I tried again and it randomly restarted on me, my luck, right?) Hello. I have been experiencing lockups, restarts, and BSODs as of recent. My computer is 2-3 years old, and most of my information is...
BSOD Help and Support
Battlefield 3 BSODs / Freezes / Lockups
Having a hell of a time with this game. I've updated DirectX and my ATI video drivers...the most common BSOD seems to be related to dxgmms1.sys‎. I get 1-2 locks a day playing and a BSOD every couple of days. System specs: Intel i5 2500k ASRock P67 Extreme6 mobo 8GB G.Skill RipJaws X RAM...
BSOD Help and Support
Lockups and BSODs during games - Win 7 x64
Good day, I've been having problems with my PC lately, and I can't seem to solve it. When I'm running applications, just having it run idle on the desktop or web browsing, there is no issue. However, when playing games, the computer will occasionally and randomly lock up. In some games the...
BSOD Help and Support
BSODs, Lockups, Random reboots
This is a pretty new system. I had it built by a long-standing local PC shop with a very good rep, mostly because I didn't want to hassle with the typical issues of putting a new system together. And here I am having trouble.... System is Win 7 Home Premium, 64bit. The OS is original was...
BSOD Help and Support
Random Lockups...HARD lockups
Ok, so I built a friend a Core i7 920 based system. here are the specifics: Core i7 920 ASUS P6T Motherboard 6GB OCZ DDR3 Memory Corsair 750W PSU 300GB Velociraptor Wstern Digital HDD PNY GTX 285 Video Card
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 20:41.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App