Reboot and the blue screen of death

[weasleman]

Bought a Abit motherboard and a 64 3800 dual core amd. Now turned on the machine installed an OS and the machine worked fine then occasionally the machine rebooted. So thought maybe memory bought some new memory (corsair) still the same problem.
From what i am reading everyone saying change the voltage on the memory. If so does this mean the motherboard its self is faulty because i should not have to change the voltage in the bios for the memory.

Spec

AMD 64 3800 dual core
AN8 Sli
Geforece 6600 PCIE
Corsair Twinx 2x1GB matched XMS3200 TWINX2048-3200PT
Corsair Twinx 2x512MB XMS3200 Pro TWINX1024-3200C2PRO
650watt power supply
SB live soundcard PCI.
SATA 250 gig HD

Ohhh almost forgot there is a code showing in event viewer.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000000, 0x8941e3dc). A dump was saved in: C:\WINDOWS\Minidump\Mini042306-01.dmp

Attached is the Minidump......

 

[weasleman]

Ohhhh i also forgot Windows XP Proffessional service pack 2..

Sorry....


So who out there going to help ?????

 

[weasleman]

Will post my mini dump tonight when i get home sorry did notice till today that it had not been uploaded.

 

[weasleman]

BSOD Need help analysing Minidump file.

Machine reboots intermitantly.


Spec

AMD 64fx 3800 dual core
AN8 Sli
Geforece 6600 PCIE
Corsair Twinx 2x1GB matched XMS3200 TWINX2048-3200PT
Corsair Twinx 2x512MB XMS3200 Pro TWINX1024-3200C2PRO
650watt power supply
SB live soundcard PCI.
SATA 250 gig HD
Windows XP SP2


Event viewer error code.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000000, 0x8941e3dc). A dump was saved in: C:\WINDOWS\Minidump\Mini042306-01.dmp


MiniDump Below...i have also attached the minidump as a zip file.
--------------------------------------------------------------------------

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0036a000
PfnDataBase 81086000
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 100000d1
BugCheckParameter1 00000004
BugCheckParameter2 00000002
BugCheckParameter3 00000000
BugCheckParameter4 8941e3dc
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 000003c8
DriverListOffset 00002fd8
DriverCount 0000007a
StringPoolOffset 00005410
StringPoolSize 000010e8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 80550338
DebuggerDataOffset 00002d48
DebuggerDataSize 00000290
DataBlocksOffset 000064f8
DataBlocksCount 00000005


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Apr 23 21:33:50 2006
System Uptime: 0 days 10:42:24
start end module name
804d7000 806e2000 nt Checksum: 001EE722 Timestamp: Wed Mar 02 00:34:38 2005 (42250A1E)

Unloaded modules:
b1d53000 b1d7d000 kmixer.sys Timestamp: unavailable (00000000)
b1d29000 b1d53000 kmixer.sys Timestamp: unavailable (00000000)
b2555000 b257f000 kmixer.sys Timestamp: unavailable (00000000)
b1527000 b1551000 kmixer.sys Timestamp: unavailable (00000000)
b1d53000 b1d7d000 kmixer.sys Timestamp: unavailable (00000000)
b2555000 b257f000 kmixer.sys Timestamp: unavailable (00000000)
b4371000 b439b000 kmixer.sys Timestamp: unavailable (00000000)
b4e6f000 b4e99000 kmixer.sys Timestamp: unavailable (00000000)
b4e6f000 b4e99000 kmixer.sys Timestamp: unavailable (00000000)
b536a000 b5394000 kmixer.sys Timestamp: unavailable (00000000)
baf08000 baf09000 drmkaud.sys Timestamp: unavailable (00000000)
b554c000 b5559000 DMusic.sys Timestamp: unavailable (00000000)
b5394000 b53b7000 aec.sys Timestamp: unavailable (00000000)
b5634000 b5642000 swmidi.sys Timestamp: unavailable (00000000)
bae64000 bae66000 splitter.sys Timestamp: unavailable (00000000)
b764a000 b765a000 Serial.SYS Timestamp: unavailable (00000000)
b5892000 b58a6000 Parport.SYS Timestamp: unavailable (00000000)
ba958000 ba961000 processr.sys Timestamp: unavailable (00000000)
ba55d000 ba561000 kbdhid.sys Timestamp: unavailable (00000000)
bab08000 bab15000 i8042prt.SYS Timestamp: unavailable (00000000)
bac08000 bac0d000 Cdaudio.SYS Timestamp: unavailable (00000000)
ba561000 ba564000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check


-----------------------------------------------------------------------


Thanks in advance.

 

[howard_hopkinso]

Hello and welcome to Techspot.

It`s difficult to be sure of your problem from just one minidump.

Your minidump crashes at emu10k1m.sys. This is your Creative SB Live! Adapter Driver. It has a bugcheck of D1. Try updating your soundcard drivers.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Go HERE and follow the instructions.

If that doesn`t help. Zip 5 or 6 of your latest minidumps together and attach them here.

P.s I have merged your other thread into this one.

Regards Howard :wave: :wave:

 

[weasleman]

Thank you. If it persists i will post the other Minidumps. But is there any possibility its a hardware issue ?????

 

[howard_hopkinso]

Yes it`s possible that you have a hardware problem.

However, I have no way of telling from just one minidump.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

As you can see from the bugcheck code, ram or a bad pagefile seems to be a possible cause.

Go and follow the instructions and see if it helps.

Regards Howard

 

[shibe]

I am having the exact same problem

has anyone found a solution to this? how did you solve it?