Annoying BSOD

[Moragauth]

Hi,

I recently formatted my laptop (a Fujitsu-Siemens A1667G), and after trying to play some games on it (Baldur's Gate 2, for instance), give or take 5 minutes into the game, it generates a BSOD ("A thread tried to release information it did not own.") The PC used to do this as well, but the problem stopped for some reason after a while. Is there any particular reason it might be causing this? Even after I had new RAM installed, it did not generate any problems, and it is odd that the problem should recur after a format, when in the past it did not do so. It's been suggested to me to use the UBCD diagnostic tool, but I haven't the faintest idea how to use it. I don't want to take my laptop in for repair unless it's really necessary, and I doubt this is being caused by a hardware problem, as before the format it was working fine. I've attached the Dxdiag file and a zip with the minidumps. I'll be running MemTest later to see if I can rule out the memory as the cause of the problem. Please help.

 

[CCT]

When you re-formatted and re-installed, did you install the mobo chipset drivers before the others?

 

[Moragauth]

When you re-formatted and re-installed, did you install the mobo chipset drivers before the others?

No, Fujitsu-Siemens provides a CD that automatically installs all the necessary drivers - I'm not sure in what particular order it installs the drivers.

 

[CCT]

And you then updated ALL the XP security fixes etc?

And you checked the FS site for any updated drivers?

 

[Moragauth]

Yes, to both.

Does the UBCD diagnostic tool pinpoint the particular cause of the problem, BTW?

 

[CCT]

From what I read, the problem is either driver related or hardware interface related. A few of the issues I read about dealt with the cd/dvd player.


I have no knowledge about UBCD tools.

 

[Moragauth]

The two that have come up particularly often are the E3 and the 50 blue screen errors, so it is probably driver related. I thought it might be the memory, but it has never been a problem before, and anyway I'll run MemTest later to see. My particular guess was that it'd be the sound card. Could be the CD/DVD I suppose.

 

[Moragauth]

Well. the CD ROM is definitely what is causing these errors. I had a look at the Event viewer, and what crops up most frequently under "System" are errors related to "disk" and "cdrom"

e.g.
Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 14/04/2008
Time: 12:08:44
User: N/A
Computer: STUDENT
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
Data:
0000: 03 00 68 00 01 00 b8 00 ..h...¸.
0008: 00 00 00 00 07 00 04 c0 .......À
0010: 00 01 00 00 9c 00 00 c0 ....œ..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 e8 62 1e 00 00 00 00 .èb.....
0028: 8b 22 00 00 00 00 00 00 ‹"......
0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
0038: 40 00 00 c4 02 00 00 00 @..Ä....
0040: 00 20 0a 12 48 02 00 40 . ..H..@
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 00 00 00 70 b9 51 86 ....p¹Q†
0058: 00 00 00 00 e0 4b 30 86 ....àK0†
0060: 02 00 00 00 5d cc 03 00 ....]Ì..
0068: 28 00 00 03 cc 5d 00 00 (...Ì]..
0070: 1a 00 00 00 00 00 00 00 ........
0078: f0 00 03 00 03 cc 5d 0a ð....Ì].
0080: 00 00 00 00 11 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........



Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 7
Date: 04/05/2008
Time: 17:46:08
User: N/A
Computer: STUDENT
Description:
The device, \Device\Harddisk0\D, has a bad block.

For more information, see Help and Support Center at
Data:
0000: 03 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 07 00 04 c0 .......À
0010: 00 01 00 00 9c 00 00 c0 ....œ..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 38 71 60 12 00 00 00 .8q`....
0028: 01 b3 08 00 00 00 00 00 .³......
0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ....
0038: 40 00 00 84 02 00 00 00 @..„....
0040: 00 20 0a 12 40 03 20 00 . ..@. .
0048: 00 00 00 00 0a 00 00 00 ........
0050: f8 59 56 04 20 03 0c 85 øYV. ..…
0058: 00 00 00 00 00 be df 84 .....¾ß„
0060: 02 00 00 00 9c 38 30 09 ....œ80.
0068: 28 00 09 30 38 9c 00 00 (..08œ..
0070: 01 00 00 00 00 00 00 00 ........
0078: f0 00 03 00 00 00 00 0b ð.......
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........


And one of the system error messages:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 13/04/2008
Time: 17:52:43
User: N/A
Computer: STUDENT
Description:
Error code 000000e3, parameter1 8644d744, parameter2 85017798, parameter3 00000000, parameter4 00000002.


Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 65 000000e
0020: 33 20 20 50 61 72 61 6d 3 Param
0028: 65 74 65 72 73 20 38 36 eters 86
0030: 34 34 64 37 34 34 2c 20 44d744,
0038: 38 35 30 31 37 37 39 38 85017798
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 32 0002

I'm not sure if anything under "Applications" would be of relevance.



So now what should I do? MS' troubleshooting guide is not exactly too helpful with all this.

 

[Moragauth]

Anyone else got any suggestions?

 

[peterdiva]

Uninstall Norton AV. Not all are caused by Norton though (maybe the E3s). Post some new minidumps if it continues to crash.

BugCheck E3, {85da0264, 84f80020, 0, 2}
Probably caused by : SRTSP.SYS ( SRTSP+14600 )
PROCESS_NAME: BGMain.exe

 

[CCT]

This site: http://phorums.com.au/archive/index.php/t-83837.html has a smartie who says, in part:

"Most systems today do not have a separate drive controller card and instead
use a controller chip that's built onto the motherboard. It is very, very
possible that the electronics is going bad on one of your drives, most
likely a CD drive, and electrically interfering with the controller chip.
You can verify this by unplugging the AC power cord from the computer and
then, at the motherboard (preferred) or at the drive itself, removing the
flat ribbon cable/s that go to the CD drive/s. Note the red stripe on one
side of the ribbon cable, just in case the connectors are not keyed --
plugging a cable in backwards can severely damage things. Clear your Event
Logs and use the computer, watch those logs carefully for more error
messages to occur about a bad block (do a check for bad sectors, then look
at the Event Viewer). If you get more such messages, also disconnect the
ribbon cable/s for anything else you have except for C. Assuming that you
have a Drive A, you might have to tell BIOS that you don't have a Drive A
for the system to boot properly (depends on the BIOS) if you remove its
cable. Simply removing the power connectors is NOT sufficient (a drive with
bad electronics can still load or partly load the controller via the ribbon
cable, even with power to it disconencted).

The bad block messages are a serious error report of current device failures and impending total device failure. They get reported in Event Viewer if a feature, built into drives, called S.M.A.R.T. is enabled in BIOS (and if the BIOS and the drive itself supports the feature). If it were me, I'd immediately put the HDD's into a different computer (one at a time), as slave drives, and do a full and complete check on them for bad sectors and let errors be automatically fixed, and then check again for bad block messages in Event Viewer in the different computer. If they show up there too, after usage following the repair of any bad sectors, then there's little doubt that the HDD is just about to fully fail and attempts to back it up (make a disk image copy or at least save your user files) should immediately be made and not to use it any more than is absolutely necessary.
This procedure can rule out a bad HDD and instead determine that it's being electrically interfered with by another drive, a bad ribbon cable (they flex in the fan generated airflow and over time the wires can break, just like if you repeatably bent a wire by hand until it breaks), or the motherboard controller chip itself going bad. You can usually determine which is at
fault simply by removing drives and cables and, ultimately, trying a different drive all by itself to rule out the controller chip, and then watching the Event Viewer"

 

[Moragauth]

Thanks. I'm thinking of taking the laptop to the repairs shop since I can't really do any of that myself. Even after uninstalling Norton AV, the blue screens persist. Here's the minidump it stored.

 

[Bobbye]

Event Type: Error
Event Source: Cdrom
Event ID: 7
The device, \Device\CdRom0, has a bad block.

Event Type: Error
Event Source: Disk
Event ID: 7 (wrong number)
The device, \Device\Harddisk0\D, has a bad block.

Device-any device attached to the mobo that has it’s own controller
Harddisk-obvious
0-denotes any hard disk in any master position.
D- denotes the drive letter assigned to the drive according to the standard drive naming order. (D is usually your cd/dvd.)

Your CD drive has either gone bad, is dirty or is corrupt. Clean or replace.

Event Type: Error
Event Source: System Error
Event ID: 1003
Description: Error code 000000e3,

You receive a "STOP: 0x000000E3" error message when you safely remove an encrypted USB storage device from a computer that is running Windows XP Service Pack 2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;900808

Using EventID.net.