BSOD:1000007e

[strutsi]

Hi all

I got a computer recently with Windows 7 Ultimate. I'm having a lot of BSODs especially when I'm playing or when I leave my computer to idle for a long while, and I don't know what to do. When computer has restarted it shows following error message:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1035

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002888745
BCP3: FFFFF88006EDD718
BCP4: FFFFF88006EDCF80
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102510-17986-01.dmp
C:\Users\xxxx\AppData\Local\Temp\WER-21120210-0.sysdata.xml

My computer specs are:

Asus
P5K PRO, P35, S775, DDR2, ATX
Corsair
2048MB XMS2, CL5 800MHz DDR2, 240-pin DIMM
Asus
GeForce 8800GT, 512MB, PCIE, 2xDVI, TV-OUT
Intel
Core 2 Quad Q6600, S775 Quad Core, 2.40GHz, 8MB, 1066MHz

Thank you for any help with my problem

 

[CarlTR6]

Hi, strutsi; and welcome to the forums. I looked at five of your dumps and you have five different error codes. This usually indicates a hardware or hardware related problem.

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

Error code 4E, PFN_LIST_CORRUPT. Usual causes: Device driver, ?memory.

The dump with the 4E error code blamed memory corruption and indicated Avast as the cause. Usually Avast works fine with with Win 7. For troubleshooting, I suggest you uninstall Avast using this tool: Tool[FONT=&quot]. Download and install Microsoft Security Essentials in its place. You can reinstall Avast after you get your system stable and try it again.

I do find an almost guaranteed BSOD maker loaded on your system.
[/FONT]

ASACPI.sys Sun Mar 27 22:30:36 2005
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).

I suggest that you run Check Disk since you received an error code 24.

[FONT=&quot]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) . [/FONT]

Copy/paste the results into your next post. Let us know how your system is doing.

 

[strutsi]

Hi again and thanks for helping out

I did what you said and ran the checkdisk, but I think that it didnt finish, cause I heard that my computer restarted and when I checked ewentviewer it didnt have any log from checkdisk. Then my computer blue-screened again and when I got back to Windows I ran chkdsk again, but this time it didnt need to boot my comp. It also went lot faster than the first time (3 steps instead of 5) and a log appeared in the eventviewer.

I ran the check only to my Windows -HDD cause I only have it and 1Tb external hard drive. I'll let the check run it's course trough the external drive during the night

EDIT:

Oh, and I did everything else you told me to do, first.




Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
82688 file records processed. File verification completed.
104 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
117412 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
82688 file SDs/SIDs processed. Cleaning up 12 unused index entries from index $SII of file 0x9.
Cleaning up 12 unused index entries from index $SDH of file 0x9.
Cleaning up 12 unused security descriptors.
Security descriptor verification completed.
17363 data files processed. CHKDSK is verifying Usn Journal...
35242744 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

488375968 KB total disk space.
34608984 KB in 65054 files.
44964 KB in 17364 indexes.
0 KB in bad sectors.
198324 KB in use by the system.
65536 KB occupied by the log file.
453523696 KB available on disk.

4096 bytes in each allocation unit.
122093992 total allocation units on disk.
113380924 allocation units available on disk.

 

[CarlTR6]

Very good; it looks like your hard drive is OK. File system is good and no bad sectors. It is the boot drive that I am mainly concerned about. Can you upload the latest BSOD's to us?

 

[strutsi]

Hi!

Good to hear.I hope that I attached right information.

EDIT:
Oh, and my sytem has been running trough the night, something what it never before did.

 

[strutsi]

Okay, BSOD came again with following error message:


Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102610-21262-01.dmp
C:\Users\Lauri\AppData\Local\Temp\WER-31122-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I attached new dumps.

 

[CarlTR6]

I looked at the two most recent dumps. Both point to hardware or hardware related problems.

Error code DE, POOL_CORRUPTION_IN_FILE_AREA. Usual causes: Device driver, ?Memory.

Error code, 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

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`02859000 PsLoadedModuleList = 0xfffff800`02a96e50
Debug session time: Mon Oct 25 14:36:13.766 2010 (GMT-4)
System Uptime: 0 days 0:04:18.608
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DE, {2, fffff8a009bada68, fffff8a009b2da69, 71498c0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d260 )

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

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

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 0000000000000002
Arg2: fffff8a009bada68
Arg3: fffff8a009b2da69
Arg4: 00000000071498c0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDE

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000286e3f3 to fffff800028c9740

STACK_TEXT:  
fffff880`09deed58 fffff800`0286e3f3 : 00000000`000000de 00000000`00000002 fffff8a0`09bada68 fffff8a0`09b2da69 : nt!KeBugCheckEx
fffff880`09deed60 fffff800`028aeb82 : 00000000`00000000 fffffa80`01a5c800 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2d260
fffff880`09deee50 fffff880`012d4447 : fffffa80`01c9f6e8 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`09deeec0 fffff880`012edc0a : fffff880`09def730 fffff8a0`09b57b40 fffff8a0`09b71790 fffff880`09def1bc : Ntfs!NtfsDeleteFile+0x57b
fffff880`09def140 fffff880`0125baa9 : fffffa80`0288b988 fffffa80`0288b988 fffff880`09def690 fffff880`09dde000 : Ntfs!NtfsCommonCleanup+0x15da
fffff880`09def550 fffff800`028d8e5a : fffff880`09def690 fffffa80`028a5f10 fffff8a0`02b79018 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`09def580 fffff880`0125b662 : fffff880`0125ba90 fffff880`09def690 fffff880`09def900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`09def660 fffff880`012fd244 : fffff880`09def730 fffff880`09def730 fffff880`09def730 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`09def6d0 fffff880`0106523f : fffff880`09def730 fffffa80`01a23c10 fffffa80`01a23fb0 fffffa80`01c23c30 : Ntfs!NtfsFsdCleanup+0x144
fffff880`09def940 fffff880`010636df : fffffa80`028348e0 00000000`00000000 fffffa80`026daa00 fffffa80`01a23c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`09def9d0 fffff800`02bdfa0f : fffffa80`01a23c10 fffffa80`0401e060 00000000`00000000 fffffa80`019cb070 : fltmgr!FltpDispatch+0xcf
fffff880`09defa30 fffff800`02bc5a24 : 00000000`00000000 fffffa80`0401e060 fffffa80`047f0100 fffffa80`019cb070 : nt!IopCloseFile+0x11f
fffff880`09defac0 fffff800`02bdf501 : fffffa80`0401e060 fffffa80`00000001 fffff8a0`00ff0010 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`09defb40 fffff800`02bdf414 : 00000000`00001500 fffffa80`0401e060 fffff8a0`00ff0010 00000000`00001500 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`09defbd0 fffff800`028c8993 : fffffa80`01c72b60 fffff880`09defca0 00000000`04d63800 00000000`2cb98d66 : nt!ObpCloseHandle+0x94
fffff880`09defc20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2d260
fffff800`0286e3f3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2d260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260

BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260

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

Kernel base = 0xfffff800`0284e000 PsLoadedModuleList = 0xfffff800`02a8be50
Debug session time: Tue Oct 26 11:40:40.772 2010 (GMT-4)
System Uptime: 0 days 21:02:12.614
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( intelppm!C1Halt+2 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+50d8952f01a7da00
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002ffb8c8 -- (.exr 0xfffff88002ffb8c8)
ExceptionAddress: fffff800028cb4fb (nt!KiSecondaryClockInterrupt+0x000000000000028b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000001
Attempt to write to address 0000000000000001

TRAP_FRAME:  fffff88002ffb970 -- (.trap 0xfffff88002ffb970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fddfc0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000a5af00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028cb4fb rsp=fffff88002ffbb00 rbp=fffff88002ffbb80
 r8=0000000000018d5a  r9=0000000000000000 r10=0000000000012135
r11=fffffa800272ca68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiSecondaryClockInterrupt+0x28b:
fffff800`028cb4fb 000f            add     byte ptr [rdi],cl ds:6300:00000000`00000000=??
Resetting default scope

MISALIGNED_IP: 
nt!KiSecondaryClockInterrupt+28b
fffff800`028cb4fb 000f            add     byte ptr [rdi],cl

LAST_CONTROL_TRANSFER:  from fffff800028b646e to fffff800028be710

STACK_TEXT:  
fffff880`02ffa9b8 fffff800`028b646e : fffffa80`02a23000 00000000`00000000 fffff880`02ffb130 fffff800`028eb668 : nt!KeBugCheck
fffff880`02ffa9c0 fffff800`028e440d : fffff800`02accedc fffff800`02a05dac fffff800`0284e000 fffff880`02ffb8c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa9f0 fffff800`028eba90 : fffff800`02a0db14 fffff880`02ffaa68 fffff880`02ffb8c8 fffff800`0284e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffaa20 fffff800`028f89ef : fffff880`02ffb8c8 fffff880`02ffb130 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`02ffb100 fffff800`028bdd82 : fffff880`02ffb8c8 00000000`00000000 fffff880`02ffb970 fffff880`02fd3180 : nt!KiDispatchException+0x16f
fffff880`02ffb790 fffff800`028bc8fa : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb970 fffff800`028cb4fb : 00000000`00000000 fffff880`02ffbb80 fffff880`02fd3180 00000000`00000001 : nt!KiPageFault+0x23a
fffff880`02ffbb00 fffff880`03eec9c2 : fffff800`028cc24a 00000000`0023d84a fffffa80`03196478 fffff880`02fddfc0 : nt!KiSecondaryClockInterrupt+0x28b
fffff880`02ffbc98 fffff800`028cc24a : 00000000`0023d84a fffffa80`03196478 fffff880`02fddfc0 00000000`00000001 : intelppm!C1Halt+0x2
fffff880`02ffbca0 fffff800`028c6ebc : fffff880`02fd3180 fffff880`00000000 00000000`00000000 fffff880`01865480 : nt!PoIdle+0x53a
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm!C1Halt+2
fffff880`03eec9c2 c3              ret

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  intelppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

I suggest that you test your RAM with Memtest following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Errors, if any, will show on your screen in red. This will take 7-8 hours. Post your results.

If there are no errors in Memtest, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier finds faulty drivers, it will cause BSOD's. Upload any and all Driver Verifier enabled dumps.

 

[strutsi]

Thanks again!

I ran memtest during the night and it went trough 16 passes. There was one error found during pass 11. Error line showed this:

TST 4 PASS 11 Failing adress 000587a75e4 - 1415.6MB Good 18d19e46 Bad 18d18e46 Err-Bits 00001000 Count- Chain 1

I will now start swapping memory to different slots.

 

[CarlTR6]

Pull all of your RAM except for one stick. Test that stack. If it passes pull it, mark it as good and test the next stick and so on. If all sticks test good, test each memory slot with a good stick.

 

[strutsi]

Hi!

I checked every RAM stick individually and memory slots also and memtest found no errors. I must admit that I skipped two memory slots, but there have never been any sticks on them.
I'll do that Driver Verifier next.

EDIT:

Oh, how do I upload Driver Verifier dumps? Same way than those others?

 

[strutsi]

Okay, Driver Verifier caused a BSOD, and I had to use system restore point to get my system working again. Before I uploaded the dumps from the first BSOD, my computer crashed again and showed this error message

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1035

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF800029BBE29
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102710-23306-01.dmp
C:\Users\Lauri\AppData\Local\Temp\WER-46613-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[CarlTR6]

You still got that first error with all of your sticks in. That can mean your RAM is mismatched, not compatible with your mother boards, or there is a problem with the memory controller. If you have not enabled Driver Verifier, I would run Prime 95 following the instructions in this tutorial:

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs).

To answer your question, Driver Verifier enabled dumps are saved the same way as other dumps.