Seeking Confirmation: BSOD on new PC with Win XP SP2 after program installation

Greetings,

I'm seeking confirmation of my suspicions. Recently a blind friend of mine upgraded his system, and I gave my word that a particular store hadn't sold me dud computers in the past, and had done right by me. He orders the box, it arrives, and I set it up for him, installing a scanner (usb) without any major dramas. Then when we try to install his screen reader software, things turn sour. I really don't want to name the software atm, but it cost him $700. It doesn't install properly and suddenly the system has BSODs. Since he's away on his 'medical grand tour' for a while he gives me the system to fiddle with to fix it. He's due back soon. I've been in contact with the makers of the software, and they are sure that its not the fault of the software and they have not hand any problems with his particular setup beforehand with that particular version.

The main task of his system will be for optical character recognision and for reading material to him.

I think he needs a new motherboard... but this is a brand new computer. Well it was brand new until we took it out of the box. And he can't really afford to spend much more

Here is the error code that I've pulled from the event log each time:
--------------------
0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
--------------------

His system is:
Genuine Intel E6300 Core 2 Duo, Intel 965 m/board, 4 x 1024MB DDR2, 320GB SATA, 256MB NVIDIA GeForce 7300 GT, Creative Sound Blaster Auidocity, 16x DVD Burner, Win XP SP2 Home.

Steps I've taken so far (in rough order)
- Repartition Hard Disk
- Reinstall Windows from shrink wrap cd
- Installed Motherboard driver + software
- Installed Soundcard drivers + software + update downloaded onto thumbdrive from net
- Installed Video Card drivers + software + update downloaded onto thumbdrive from net
- Installed DVD Burner drivers
(computer hasn't missed a beat yet)
- Installed *The Program* which wants to reboot
BSOD
- Use "Last good settings" *The Program* trys to continue to install
BSOD
- "Last good settings" - cancel installation
- <insert various miscellaneous steps as per instructions from programs help desk which don't fix problem>
- Intel Desktop Utilities show all monitored values within nominal ranges.
- Test system with BurnIn Test which shows maths errors whenever maths and sound or maths and video tasks are preformed at the same time.

I've also run some SiSoftware Sandra(Lite XI.SP1) tests on the machine as well if it helps.

Should I post the memory dumps here, small or kernal memory dump? I think I've only one full kernal dump due to forgeting to fix the settings. But I do have about 10 or so mini-dumps. Anything other details required like the results of dxdiag? Or tests to run? Any possible fixes?

I've been trying to chase down the problem for 2 weeks now.

Many thanks.

Definitely post your memory dumps found in C:\Windows\minidump

If the computer doesn't blue screen without this software, there's no reason to believe the computer itself is at fault... it really is most likely the software. It may be some combination of hardware, software or configuration settings that are making this software act up, but certainly don't rule out the application itself.

This sounds troubling, but you have to take these software 'burn in tests' with a grain of salt. Seek a second opinion using a different burn in utility... preferably one that is done OUTSIDE of Windows.

As requested, here are some of the memory dumps from C:\windows\minidump

In particular, the first 2 memory dumps and the last 3 memory dumps.

This maybe more of a red-herring then an assistance, but the program at its current state of installation, is complaining about being unable to install its video intercept drivers.

There is another reason why I'm leaning more towards the hardware, apart from the fact that for $700 you expect a piece of software to run without too many problems. Included in the Intel Desktop Utilities was 'StressTest' by PassMark Software. Every time I've run the 2 minutes test, I've produced errors... the latest set of 3 being 33 errors (26 CPU, 7 MMX), 35 errors (30 CPU, 5 MMX), and 30 errors (26 CPU, 4 MMX). These errors are mathematical errors and consist of a random selection of all four main types of operations (addition, subtraction, multiplication, division)

With regards the burn in test, I've been using the software call BurnInTest by PassMark Software. I'll have a look at the link you provided. Thanks. BurnInTest, when just doing maths, has no problems, but when doing certain other tasks, then the errors start to appear like in the 2 minute 'StressTest'.

I'll be wiping the computer before I give it back to him, as I'll need to repartition the hard disk back to how he wants it, and will be re-installing Windows and all the various drivers, software, etc, but that's unrelated to the underlying fault.

Stack overflow

This is stack overflow issue. Usually it occurs if Norton AV is installed. From the stack trace, I find a lot of footprint of dcmc0d0 and jawsvid.

ba94583c bfa4caa7 bfa4c9c8 ba945ec4 e185acf0 dcmc0d0+0x932c
ba945ca8 bfa4c819 ba945cbc 00000208 00000000 dcmc0d0+0x7aa7
ba945edc bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x7819
ba945f10 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba946148 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba94617c bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba9463b4 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba9463e8 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba946620 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba946654 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba94688c bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba9468c0 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba946af8 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba946b2c bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba946d64 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba946d98 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba946fd0 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba947004 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba94723c bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba947270 bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba9474a8 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba9474dc bfa4c86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba947714 bfa1d0e6 00030101 0000000c ba9479a0 dcmc0d0+0x786f
ba947748 bf9da86f 00030101 0000000c ba9479a0 jawsvid+0x90e6
ba947980 bf8ba311 00030101 0000000c ba9479a0 atkdisp+0x786f

Expand the size of stack trace may resolve the blue screen problem. Refer the following webpage to extend the size of windows stack.
http://service1.symantec.com/SUPPOR...10eaa5fc1148e6f888256bf40056e227?OpenDocument

Hmmm...

The names you mention are names of some of the .dll that get removed from the c:\windows\system32 directory during the <steps for help desk> stage, and are then restored from 'good' verisions. Therefore they are probably what's causing the the stack to overflow. I'll try to increase the stack size - I'm hunting through the knowledge base at Microsoft in another window at the moment.

The computer in question does not have Nortons AV installed on it, nor does it have any Symantec software on it. It's completely standalone - has never been connected to another computer and never intended to be. So all the software and upgrades for drivers and alike are downloaded onto this computer, scanned, transfered onto a thumbdrive, and then transfered onto his computer as needed.

I've also gone back into the event log and must extend my appologies, for I failed to mention something that might have helped. For the first two times the system had a BSOD, (and the first two times only) the event log has the following entry very close to the save dump entry:

Code:

Event Type:	Error
Event Source:	System Error
Event Category:	(102)
Event ID:	1003
Date:		13/02/2007
Time:		9:38:17 AM
User:		N/A
Computer:	WARRENS
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000, 
parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.
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 31 30 30 30 30 30 37    1000007
0020: 66 20 20 50 61 72 61 6d   f  Param
0028: 65 74 65 72 73 20 30 30   eters 00
0030: 30 30 30 30 30 38 2c 20   000008, 
0038: 38 30 30 34 32 30 30 30   80042000
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 30               0000    

Code:

Event Type:	Error
Event Source:	System Error
Event Category:	(102)
Event ID:	1003
Date:		13/02/2007
Time:		9:39:09 AM
User:		N/A
Computer:	WARRENS
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000, 
parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
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 31 30 30 30 30 30 37    1000007
0020: 66 20 20 50 61 72 61 6d   f  Param
0028: 65 74 65 72 73 20 30 30   eters 00
0030: 30 30 30 30 30 38 2c 20   000008, 
0038: 38 30 30 34 32 30 30 30   80042000
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 30               0000    

I'm still a little concerned though about the errors that the two different benchmarkers that I've run so far as outlined above.

I don't mean your friend's windows has Norton AV. Stack overflow means that all the stacks are used. Norton AV uses a lot of stack trace hence it has the procedure to extend the size of stack. Anyway it is no harm to extend the size of stack trace. Maybe it can resolve the problem.

From the stack trace I find the following entries repeated several times. After you extend the stack , you had better re-install jaws.

Repeating entries
dcmc0d0+0x786f
jawsvid+0x90e6

The saga continues...

I'm still having trouble with my friend's system. And hats off to cpc2004 for identifying The Program as Jaws.

In order to save space the in the following there are a few abreviations, some of which I hope are standard, in particular, LKGC - Last Known Good Configuration.

Following the suggestions presented here, I have tried to extend the size of the kernel stack space. I tried looking at the page suggested here, it didn't really help, and tried going through the Knowledge base at Microsoft. However, this has been without success.

Generally speaking the following cycle was followed:

• Modify Boot.ini
• Reboot
• Install Program from CD
• Before reboot update Video intercept drivers
• Reboot
• BSOD
• Start Normally
• BSOD
• LKCG
• Run Program
• Video Intercept error - install driver
• Reboot
• BSOD
• LKGC
• Uninstall Program
• Reboot

Original boot.ini

Code:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect

Here is the modifications for the boot.ini for each cycle. (snipped for space)

Code:

<snip>tion" /3G /noex<snip>

Code:

<snip>tion" /3G /noguiboot /sos /noex<snip>

Code:

<snip>/3G /userva=2900 /noguiboot /sos <snip>

Code:

<snip>/userva=2560<snip>

Code:

<snip>/userva=2220<snip>

As beforehand, the following was the record in the event log:

Code:

Event Type:	Information
Event Source:	Save Dump
Event Category:	None
Event ID:	1001
Date:		7/03/2007
Time:		12:09:35 PM
User:		N/A
Computer:	WARRENS
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000007f 
(0x00000008, 0x80042000, 0x00000000, 0x00000000). 
A dump was saved in: C:\WINDOWS\Minidump\Mini030707-04.dmp.
For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.

The only difference between events were the actual minidump name and the datestamp.

Please find attached the assoicated minidumps for each cycle. Is it still a Kernal Stack Overflow? Are the drivers faulty somehow? Am I trying to change the kernal size correctly? The answer is probably staring me in the face, I just can't see it at the moment.

Oddly enough, during the final cycle, event though The Program caused the BSOD, I couldn't find a minidump for it and only noticed this when I went to post this message.

Regards,

MicroShader

Is the video card made by ASUS? You don't have an nv_disp.dll file (nvidia driver), instead the file is atkdisp.dll, which I think is an ASUS enhanced video driver. It's known to cause problems.

I just pulled the side of the case off the computer yet again and carefully looked at the video card... with no really visible logos, etc on it. Hunting around, along one edge it says PCB Made In China. On the other face of the card, no details can really be seen as its hidden behind a large heatsink, by shining a torch on it shows ASUS embossed in the heatsink, so they probably made the card. I'll try to hunt down a copy of nv_disp.dll and see if it helps.

What you should do is uninstall the current video drivers and then install the Nvidia supplied drivers. Hopefully this will remove everything ASUS related.

Uninstall instructions.

Nvidia drivers.

Sorry for the delay in responding - had some medical tests of my own to complete.

The problem is fixed.

Followed your suggestions peterdiva and then tried to reinstall the program and got the BSOD. Just before I tried to reinstall the program I checked the system directory and noted that atkdisp.dll was still present, but still continued anyway

So I took a step back and looked over the directions again. No were did they mention atkdisp.dll... so I went to Add/remove programs and saw that the ASUS Enhanced Drivers were still 'installed' so I clicked remove. Checked the system directory, and atkdisp.dll had vanished. I then uninstalled Jaws, and manually removed the various entries in the registry that it left behind, and the files it left in the system directory, as per directions sent to me by tech support.

Reboot.
Install the program.
Success!

No BSOD!

I've since wiped the system again to clean up all the various tweaks and other programs, files, and other stuff I've put on it trying to find the problem, and reinstalled everything that my friend wants, and have activated Windows and alike for him.

He very happy to have his computer back and running. Thanks for all the help.