BSOD error message Event ID 1001

Status
Not open for further replies.
Hello,

I am getting a bsod every day this is what is showing up in system log.

Event ID 1003
Category (102)
Error code 1000008e, parameter1 c0000005, parameter2 f5575ee9, parameter3 f5fd6788, parameter4 00000000.

Event ID 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf5575ee9, 0xf5f96788, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini071409-07.dmp.

Here is the DMP file log. Any help with this will be greatly appreciated.

Thank you.



C:\>dumpchk Mini071409-07.dmp
Loading dump file Mini071409-15.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 797c0080
PfnDataBase 81926000
PsLoadedModuleList 8055d720
PsActiveProcessHead 805638b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 f565dee9
BugCheckParameter3 ed066788
BugCheckParameter4 00000000
PaeEnabled 00000001
KdDebuggerDataBlock 8054d2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00001868
DriverListOffset 00004478
DriverCount 000000a2
StringPoolOffset 00007490
StringPoolSize 00001678
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ed066798
DebuggerDataOffset 000041e8
DebuggerDataSize 00000290
DataBlocksOffset 00008b08
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 c

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 14 18:16:09 2009
System Uptime: 0 days 0:11:32
start end module name
804d7000 806e4000 nt Checksum: 001F9D43 Timestamp: Fri F
32:51 2009 (498C11D3)

Unloaded modules:
f38fe000 f3903000 Cdaudio.SYS Timestamp: unavailable (00000000)
9fd48000 9fd4b000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check
 
0x8E errors are almost always caused by hardware (though sometimes by drivers) and are particularly strong indicators of corrupted memory. I am not saying this is your cause but it would be a good move to run Memtest on your RAM.

Check out this link and follow directions: https://www.techspot.com/vb/topic62524.html

Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better.. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


* Get back to us with the results.
 
As Route44 said... this Bugcheck points strongly to your RAM. So...
Are you overclocking?
Are your RAM voltages set to manufacturer specs?
Is your RAM on the Hardware compatibility list for your MB?
(Asus boards are known to be especially picky)
 
Status
Not open for further replies.
Back