Hello, I've had my home built computer for a little over a week now. It's been great! But, I've noticed something really strange. When it goes into sleep and I wake it up, it sometimes restarts randomly. And I get a notification that says the hard drive stopped momentarily. First, I thought it was a Hard Drive problem, so I scanned it, and it came out just fine! Then, today, I left it alone for more than 30 mins., it went into sleep, I came back around an hour later, pressed the power button, and it says it shut down unexpectedly and that there was a blue screen error. What could this be? Should I just disable sleep? Thanks for your help!
If you have a BSOd report, please post and you will receive help
http://www.sevenforums.com/crashes-d...tructions.html
http://www.sevenforums.com/crashes-d...tructions.html
Great! I've attached the files! I really appreciate it!
Windows 7 64-Bit
Original OS
Retail Version
Age of Hardware: 1 Week, 1 Day
OS Installed: 1 Week, 1 Day
Windows 7 64-Bit
Original OS
Retail Version
Age of Hardware: 1 Week, 1 Day
OS Installed: 1 Week, 1 Day
You have provided me with 2 dump reports. They show two different possible causes, but are not mutually exclusive.
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION: The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
Suggested Solution:
Download memtest86 and test RAM http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://hcidesign.com/memtest/manual.html
Scan with your Anti Virus
SFC /scannow
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Test your hard drive at the manufacturers website.
Reseat graphics card to make sure that it is properly set.
Make sure that all cables are tight and properly attached.
Any changes to the MB should be restored to the original.
A driver problem was not indicated and in addition all of your drivers are up to date.
After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
Please remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION: The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
Code:
icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp4_Windows7_BSOD_jcgriff2[1].zip\Windows7_BSOD_jcgriff2\081310-22542-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50 Debug session time: Sat Aug 14 00:09:44.059 2010 (GMT-4) System Uptime: 0 days 0:53:49.166 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {20, ffffffffc000009d, fffffa8004f73078, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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 0xC0000185, 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000009d, error status (normally i/o status code) Arg3: fffffa8004f73078, current process (virtual address for lock type 3, or PTE) Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x7a_c000009d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from fffff80002ef83fc to fffff80002ec0740 STACK_TEXT: fffff880`03108828 fffff800`02ef83fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`04f73078 : nt!KeBugCheckEx fffff880`03108830 fffff800`02eaa637 : fffffa80`04f73010 00000000`c000009d 00000000`00000000 fffffa80`04f730a8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0 fffff880`031088f0 fffff800`02e9d0c7 : fffffa80`039f2040 fffffa80`039f2090 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57 fffff880`03108920 fffff800`02ec7b9d : fffffa80`039f2040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`031089a0 fffff800`02ec3d4b : 00000103`055c0c01 00000000`00000000 fffffa80`00000000 fffff880`03108a50 : nt!KiCommitThreadWait+0x3dd fffff880`03108a30 fffff800`02e5aabf : fffffa80`00000002 fffff880`03108d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271 fffff880`03108ce0 fffff800`03164c06 : fffffa80`039f2040 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf fffff880`03108d40 fffff800`02e9ec26 : fffff880`02d63180 fffffa80`039f2040 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03108d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4c5e0 fffff800`02ef83fc cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c5e0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0 BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0 Followup: MachineOwner --------- 2: kd> lmtsmn start end module name fffff880`03e00000 fffff880`03e3e000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00eac000 fffff880`00f03000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03ca4000 fffff880`03d2e000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03c77000 fffff880`03c8d000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`03f7c000 fffff880`03f91000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00e58000 fffff880`00e63000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`05fc5000 fffff880`05fd0000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e23000 fffff880`00e4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04673000 fffff880`04ca9000 atikmdag atikmdag.sys Tue Nov 24 22:44:50 2009 (4B0CA832) fffff880`02ae1000 fffff880`02ae8000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03f45000 fffff880`03f56000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`044fd000 fffff880`0451b000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`006d0000 fffff960`006f7000 cdd cdd.dll unavailable (00000000) fffff880`02a81000 fffff880`02aab000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d30000 fffff880`00df0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`00e63000 fffff880`00e93000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cd2000 fffff880`00d30000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01137000 fffff880`011aa000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`03e88000 fffff880`03e98000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`064ad000 fffff880`064bb000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03ea4000 fffff880`03f27000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03f27000 fffff880`03f45000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03c68000 fffff880`03c77000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01224000 fffff880`0123a000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`043b8000 fffff880`043da000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`064bb000 fffff880`064c7000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`064d2000 fffff880`064e5000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`064c7000 fffff880`064d2000 dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`064a1000 fffff880`064ad000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04ca9000 fffff880`04d9d000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04d9d000 fffff880`04de3000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`05f8f000 fffff880`05fc5000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`04de3000 fffff880`04df0000 fdc fdc.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`010c5000 fffff880`010d9000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`04328000 fffff880`04333000 flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`01079000 fffff880`010c5000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`0103a000 fffff880`01074000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`015ae000 fffff880`015f8000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`05f76000 fffff880`05f7f000 gdrv gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175) fffff800`02e07000 fffff800`02e50000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`04600000 fffff880`04624000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05feb000 fffff880`05ff7000 hiber_dumpata hiber_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05e0b000 fffff880`05e1e000 hiber_dumpfve hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`05e00000 fffff880`05e0b000 hiber_msahci hiber_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`06470000 fffff880`06489000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06489000 fffff880`06491080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`06462000 fffff880`06470000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`04435000 fffff880`044fd000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0121b000 fffff880`01224000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03e5b000 fffff880`03e79000 i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`03e79000 fffff880`03e88000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff800`00baa000 fffff800`00bb4000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04279000 fffff880`042bc000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013e4000 fffff880`013fe000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01583000 fffff880`015ae000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`043da000 fffff880`043df200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`06537000 fffff880`0654c000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`064f3000 fffff880`06516000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00cb1000 fffff880`00cbe000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`064e5000 fffff880`064f3000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`03c8d000 fffff880`03c9c000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06494000 fffff880`064a1000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02aab000 fffff880`02ad8000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`05f7f000 fffff880`05f8f000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`0451b000 fffff880`04533000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`04533000 fffff880`04560000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`04560000 fffff880`045ae000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`045ae000 fffff880`045d1000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`00e4d000 fffff880`00e58000 msahci msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`02b46000 fffff880`02b51000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f0c000 fffff880`00f16000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`010d9000 fffff880`01137000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03c5d000 fffff880`03c68000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01418000 fffff880`0142a000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01431000 fffff880`01523000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03e98000 fffff880`03ea4000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`02bb1000 fffff880`02be0000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04333000 fffff880`04348000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03da2000 fffff880`03db1000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03d2e000 fffff880`03d73000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01523000 fffff880`01583000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02b51000 fffff880`02b62000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03c51000 fffff880`03c5d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02e50000 fffff800`0342c000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01241000 fffff880`013e4000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02ad8000 fffff880`02ae1000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`03d7c000 fffff880`03da2000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`03e3e000 fffff880`03e5b000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00f56000 fffff880`00f6b000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f16000 fffff880`00f49000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00fdc000 fffff880`00fe3000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fe3000 fffff880`00ff3000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01200000 fffff880`01211000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`05e1e000 fffff880`05ec4000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`0437b000 fffff880`043b8000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cbe000 fffff880`00cd2000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`02b8d000 fffff880`02bb1000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`02be0000 fffff880`02bfb000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`02a00000 fffff880`02a21000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`02a21000 fffff880`02a3b000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03c00000 fffff880`03c51000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`03ff0000 fffff880`03ffb000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`02b2b000 fffff880`02b34000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b34000 fffff880`02b3d000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b3d000 fffff880`02b46000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01000000 fffff880`0103a000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`0654c000 fffff880`06564000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04624000 fffff880`04656000 Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) fffff880`04348000 fffff880`0437a700 RtHDMIVX RtHDMIVX.sys Wed Dec 02 01:33:25 2009 (4B160A35) fffff880`06244000 fffff880`06461300 RTKVHD64 RTKVHD64.sys Tue Dec 08 05:20:05 2009 (4B1E2855) fffff880`05ec4000 fffff880`05ecf000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`04df0000 fffff880`04dfc000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03db1000 fffff880`03dce000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`01410000 fffff880`01418000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`06564000 fffff880`065fa000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`05f0e000 fffff880`05f76000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`05ecf000 fffff880`05efc000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`04dfc000 fffff880`04dfd480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01601000 fffff880`017fe000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`05efc000 fffff880`05f0e000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02b80000 fffff880`02b8d000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02b62000 fffff880`02b80000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03de9000 fffff880`03dfd000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00520000 fffff960`0052a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`03f56000 fffff880`03f7c000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`042bc000 fffff880`042ce000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`06492000 fffff880`06493f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04661000 fffff880`04672000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`042ce000 fffff880`04328000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`04656000 fffff880`04661000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03f9a000 fffff880`03ff0000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00f49000 fffff880`00f56000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02ae8000 fffff880`02af6000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02af6000 fffff880`02b1b000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`01400000 fffff880`01410000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00f6b000 fffff880`00f80000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00f80000 fffff880`00fdc000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`011aa000 fffff880`011f6000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03dce000 fffff880`03de9000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02b1b000 fffff880`02b2b000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00c00000 fffff880`00ca4000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00df0000 fffff880`00dff000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03d73000 fffff880`03d7c000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00060000 fffff960`0036f000 win32k win32k.sys unavailable (00000000) fffff880`03f91000 fffff880`03f9a000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00f03000 fffff880`00f0c000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06516000 fffff880`06537000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`04200000 fffff880`04271000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04200000 fffff880`04271000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04400000 fffff880`04431000 WUDFRd.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`05fd0000 fffff880`05feb000 USBSTOR.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04200000 fffff880`04271000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00e93000 fffff880`00ea1000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00ff3000 fffff880`00fff000 dump_pciidex Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00ea1000 fffff880`00eac000 dump_msahci. Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`02a6e000 fffff880`02a81000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Download memtest86 and test RAM http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://hcidesign.com/memtest/manual.html
Scan with your Anti Virus
SFC /scannow
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Test your hard drive at the manufacturers website.
Reseat graphics card to make sure that it is properly set.
Make sure that all cables are tight and properly attached.
Any changes to the MB should be restored to the original.
A driver problem was not indicated and in addition all of your drivers are up to date.
After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
Please remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.
Thanks so much! I am running malwarebytes right now. I ran my antivirus software earlier and nothing came up. Could it possibly be the drivers I installed for my motherboard?
Just got this result:
Quote:
Malwarebytes' Anti-Malware 1.46
Malwarebytes
Database version: 4455
Windows 6.1.7600
Internet Explorer 8.0.7600.16385
8/20/2010 6:50:41 PM
mbam-log-2010-08-20 (18-50-41).txt
Scan type: Quick scan
Objects scanned: 127011
Time elapsed: 3 minute(s), 9 second(s)
Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0
Memory Processes Infected:
(No malicious items detected)
Memory Modules Infected:
(No malicious items detected)
Registry Keys Infected:
(No malicious items detected)
Registry Values Infected:
(No malicious items detected)
Registry Data Items Infected:
(No malicious items detected)
Folders Infected:
(No malicious items detected)
Files Infected:
(No malicious items detected)
Malwarebytes
Database version: 4455
Windows 6.1.7600
Internet Explorer 8.0.7600.16385
8/20/2010 6:50:41 PM
mbam-log-2010-08-20 (18-50-41).txt
Scan type: Quick scan
Objects scanned: 127011
Time elapsed: 3 minute(s), 9 second(s)
Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0
Memory Processes Infected:
(No malicious items detected)
Memory Modules Infected:
(No malicious items detected)
Registry Keys Infected:
(No malicious items detected)
Registry Values Infected:
(No malicious items detected)
Registry Data Items Infected:
(No malicious items detected)
Folders Infected:
(No malicious items detected)
Files Infected:
(No malicious items detected)
Where should I start to fix the issue?
Not done. I will remove line one notice when done. We will get this fixed. Refresh page to watch progress.
Thanks so much! I am relieved!
Thanks! I will try to run some of these tests in the next couple of hours and post back maybe tomorrow.
What I suggest is that you start with the test of your hard drive, then test. Take another suggestion, then test, again. As soon as the BSOD stops, the computer is fixed. Take your time.
It is possible that the sleep issue and BSOD are not related.
If after all suggestions are taken and another BSOD just repost.
Good luck.
It is possible that the sleep issue and BSOD are not related.
If after all suggestions are taken and another BSOD just repost.
Good luck.
Hard Drive test appears to be fine! I did the longer test too. I am in the middle of testing the RAM. I wouldn't be at all surprised if it is the BIOS in my motherboard. Maybe I should check and see if there's an update. I could also call Gigabyte on Monday.
Run that memtest for at least 6 passes up to 10. It is my policy not to suggest BIOS until all else has failed, due to possible problems if not done correctly. If it is your feeling that it is BIOS go for it. You seem to be rather knowledgable in this area.
Thanks! I had to cancel the memtest86+ because it's getting late. But, will retry the test tomorrow morning. I am REALLY hoping it's not a bad motherboard. I think it may also be an outdated driver. I was on Gigabyte's website and noticed a bunch of updated drivers. Maybe I should install some of those...
No need to guess.
Follow all my steps and if you get another BSOD we will analyze it, again.
Follow all my steps and if you get another BSOD we will analyze it, again.
I didn't have much time to retest the RAM today. So, I went ahead and updated the drivers, disabled Hybrid Sleep mode, and restored the BIOS to its original settings. I left it alone for 30 mins for it to go to sleep, came back, turned it on, and it came up just fine. It's extremely strange... Also, in the BIOS I noticed that wake computer from mouse and keyboard are disabled. Should they be enabled? Well... I guess the problem could be worse.
The only bad consequce of enabling them is that sometimes the computer will wake before its time. I have mine disabled intentionally. Give it a try, its free. See how it works for you.
Great! Thanks! I am going to test it out without Hybrid Sleep Mode for a while, and if that doesn't work, I'll try enabling them. I'll also try calling Gigabyte on Monday. I looked at the Changelog for the BIOS updates, and there isn't a correction for it, so I'll leave that alone for now.
Also, when restarting my computer, the Hard Drive to spins down and right after it displays the options, it presents a screen that says scanning drives, then I hear it spin up and it boots. Is that normal? THANKS FOR ALL OF YOUR HELP!
Also, when restarting my computer, the Hard Drive to spins down and right after it displays the options, it presents a screen that says scanning drives, then I hear it spin up and it boots. Is that normal? THANKS FOR ALL OF YOUR HELP!
Should not be scanning
Do this
Run a disc clean up
Error check
Defrag
Then go to the website of your HD mfg and test the drive. If ok dont worry.
Dont know how to do, just post. Its easy.
Suggestions for Proper Maintenance
Do this
Run a disc clean up
Error check
Defrag
Then go to the website of your HD mfg and test the drive. If ok dont worry.
Dont know how to do, just post. Its easy.
Suggestions for Proper Maintenance
I noticed it scanning after I ran the Hard Drive test last night. I will scan it once more using the quicker way. I will also install and run Auslogics Disc Defrag. Should I try using Registry Defrag as well? And, I'll go the the manufacturers website and attempt to run the test.
Dont touch the registry, for now. Reg cleaner and defrag etc are the doorway to trouble. The built in defrag is good enough. It just does not entertain you with pretty graphics as it works.
Okay. I'll run the Hard Drive check now! Thanks! Also, it only appears to run the scan on restart. But, not when powering on. Still, today is the fine time I've noticed the scan on restart.
Did Defrag and Tests. Everything passed. The ROM Loader appears to still be scanning the drives at restart though.
Test Option: QUICK TEST Model Number: WDC WD5001AALS-00J7B0 SMART Status: PASS Test Result: PASS Test Time: 19:31:40, August 21, 2010
Test Option: QUICK TEST Model Number: WDC WD5001AALS-00J7B0 SMART Status: PASS Test Result: PASS Test Time: 19:31:40, August 21, 2010
From our forum
http://www.vistax64.com/tutorials/67...sk-chkdsk.html
When I login to cmd as admin and run that command I receive a message saying that the drive, the path, or the file name is not valid.
Type cmd in search, run as administrator, then see how it works. If not try without run as administrator. It should work. If not I will check carefully for typos
Without an admin, it tells me I need admin. But, as admin, it gives me the error message: The drive, the path, or the file name is not valid.
Try in safe mode.
I have reposted my prior post to read thus:
Use Method 3
Check Disk - chkdsk - Vista Forums
The command is the same for 7
Use Method 3
Check Disk - chkdsk - Vista Forums
The command is the same for 7
I ran the command to reset and check all drives. It seems as it's coming from the AHCI, which is detecting/scanning the two drives - the Hard Drive and the DVD-RW Drive. Is there a way to disable in the BIOS? Should I disable it? The long (3-5 Second) gap only occurs during restarts, but not during power up.
No, I would not try to disable in BIOS. The final result could be the loss of the ability to boot. 15 Second delay v. the potential loss of the ability to boot, leave it the way it is. .
I think that I would try this instead
I think that I would try this instead
It's still continuing to pause during restart even with the check disk reset. I'll probably just leave it alone. If it were during regular startup it'd be somewhat annoying, but if it's just during restart it's not a really big deal. I'll post back if I get the BSOD error or restart/shutdown after sleep. Thanks once again!
I am glad that I could help with the BSOD. Any questions just post. I will try to help.
Is it necessary for me to delete the chkdsk registry entry, since it doesn't work?
I do not think that it causes any problems. The computer is working, I would leave it.
I agree! Thanks once again!
Tonight I once again left it alone for 30 minutes for it to go to sleep, came back, turned it on and it's fine. Maybe disabling the Hybrid Sleep Mode helped, or the driver updates helped.
There is one thing though that I think is unrelated. When I was using the computer tonight I had three tabs open in Firefox, I went to YouTube, and it crashed so badly I ended up having to hold down the power button to force it off. It seems fine now though. I immediately looked in my notifications and nothing came up out of the ordinary.
There is one thing though that I think is unrelated. When I was using the computer tonight I had three tabs open in Firefox, I went to YouTube, and it crashed so badly I ended up having to hold down the power button to force it off. It seems fine now though. I immediately looked in my notifications and nothing came up out of the ordinary.
A crash can be caused by many reasons. There is no one that can give you a definitive answer to why did it crash. I can give you a list of reasons, but that is not going to help
It appears to be fine now! Sometimes crashes happen. I once had the original iMac that would crash every 5 minutes! That was bad...
You can try other browsers.
You can go to tools, internet options, advanced, reset. This removes all add-ons. Put them back one at a time after using for a while. Maybe, find the cause.
You can go to tools, internet options, advanced, reset. This removes all add-ons. Put them back one at a time after using for a while. Maybe, find the cause.
That's true! I imported the Firefox profile from my old computer. And, that always runs sort of sluggish since I have quite a bit of add-ons. I'll keep my eye on it.
Không có nhận xét nào:
Đăng nhận xét