Down8
Ok, I got a super BSOD the other day while copying files, and it happened again when I retried to move the 500MB ISO to one of my SCSI drives. Here it is:
*** STOP: 0x000000D1 (0x0070F74F, 0x00000011, 0x00000000, 0xED418FEB) ***
*** ADDRESS ED418FEB base at ED418000, datestamp 37ed1e6a - aha154x.sys ***
Beggining dump of physical memory to disk: XX <-it counted up to 100, then my computer restarted
Now, I know the aha154x.sys refers to my SCSI card, but I've been using that for almost a year now, in various systems. I recently got some OEM memory from Fry's, and my friend who got the same has experienced some strange lockups [alhtough he recently switched to WinMe, too]. I was wondering: 1) Does anyone know what this is, i.e. is this bad memoery, or is my SCSI cards dying? 2) Does anyone know where I can look up this stop code? My friend said MS site, but I didn't see it [granted, I didn't look that hard].
Hopefully, it's the SCSI card, as my friend got me one for my birthday, and I just need to get down to San Diego to pick it up.
thanks for any help,
-bZj
------------------
Code:
[This message has been edited by Down8 (edited 17 September 2000).]
*** STOP: 0x000000D1 (0x0070F74F, 0x00000011, 0x00000000, 0xED418FEB) ***
*** ADDRESS ED418FEB base at ED418000, datestamp 37ed1e6a - aha154x.sys ***
Beggining dump of physical memory to disk: XX <-it counted up to 100, then my computer restarted
Now, I know the aha154x.sys refers to my SCSI card, but I've been using that for almost a year now, in various systems. I recently got some OEM memory from Fry's, and my friend who got the same has experienced some strange lockups [alhtough he recently switched to WinMe, too]. I was wondering: 1) Does anyone know what this is, i.e. is this bad memoery, or is my SCSI cards dying? 2) Does anyone know where I can look up this stop code? My friend said MS site, but I didn't see it [granted, I didn't look that hard].
Hopefully, it's the SCSI card, as my friend got me one for my birthday, and I just need to get down to San Diego to pick it up.
thanks for any help,
-bZj
------------------
Code:
=====ThugBox===== =====GimpBox=====Home built system: Just for fun:Soyo SY-7VCA Mainboard AST Bravo LC 4/66d[VIA ApolloPro 133A T82C694X] Intel 486/66MHz CPU[onboard sound] 40MB RAM [2x16, 2x4]PIII 500E [flip chip] 500MB Conner HddPNY 128MB PC100 RAM 3 1/2, 5 1/4, 2x CDROMOEM 128MB PC133 RAM 3com Etherlink II [Ext.Transcvr]Stealth III S540 Video Windows 95 [v4.00.1111]LinkSys NC100v2 Ethernet pcAnywhere 9.2Adaptec AHA-1535A SCSI [so I can leave it in the closet]Quantum Fireball 10.3GB Hdd 2 DEC SCSI Hdds [~3.5GB total] NEC 3x SCSI CDROM [Ext.w/Caddy] HP A4331D 20" Monitor Logitec MouseMan [Compaq] ^in about 12 peices on my floor^Win2K Server [v5.00.2195, SP-1] [Will be installing Linux][format => clean install] Norton AntiVirus 2000 Covad 768kbps sDSL w/3com switch & Flowpoint Router [sharedx6]
[This message has been edited by Down8 (edited 17 September 2000).]
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
MoreLight
When did this behaviour occur? Before or after you decided to mix PC100 and PC133 memory?
Down8
OP
It happened after I got the extra memory. Mixing the two has not caused any prolems for my friend who has been running Win2K Server on his PII 300@450MHz for almost a month now. The system just underclocks the PC133.
-bZj
[This message has been edited by Down8 (edited 18 September 2000).]
-bZj
[This message has been edited by Down8 (edited 18 September 2000).]
