Reproduceable BSOD - .dmp analysis help needed please!

S

slaman

New Member
I just did a fresh format... I am running the following:

Intel Core2 Duo E6400 2.13GHz CPU @ 3.20GHz w/ Scythe MINE Rev. B CPU Cooler, 2 x 1GB Corsair XMS2 6400 TWIN2X1024-6400C4 RAM, Asus P5W-DH Motherboard, Corsair HX620W PSU, Diamond ATI Radeon HD4850 512M PCI-E Video Card, Antec P182 Advanced Super Mid Tower, Pioneer DVR-R100 16XDVDRW, 4 x Western Digital WD5000AAKS 500GB HD (1 External), 2 x Western Digital WD10EADS 1TB HD (RAID1), Logitech diNovo BlueTooth Laser Desktop, Toshiba Regza 42XV540U 42" 1080p 120Hz LCD, Dell 2408W 24" LCD Monitor, Logitech z5500 Digital Surround Sound System

and the following is how my hard drives are setup:

Drive 1 (Boot drive): 640GB WD
Drive 2: 2 x 500GB WD (RAID1 using onboard JMB36X Controller - one is external)
Drive 3: 500GB WD
Drive 4: 500GB WD (Backup drive)
Drive 5: 2 x 1TB WD (RAID1 using onboard Si423 Controller)

I am running Windows Vista SP2 32-bit edition. After my format, I want to run my regularly scheduled backup task using Acronis True Image Home. I ran it four or five times, creating new tasks, and trying to incrementally build my existing backups - it kept freezing.

So I created a new backup file and got the BSOD. I then upgraded my Acronis True Image Home to the latest version of 2009 and ran it again. The same BSOD...

I've tried loading WinDbg and even installed all the symbols, but I still get unknown symbol errors in the dump file analysis.

Any ideas on what could be causing this? I would love some help from the gurus here before I rip out my hair!

The reason I included my system setup is because there is a little bit at the end of the analysis .txt file that indicates hardware error. The only significant change from the last time is the inclusion of the new RAID1 using the JMB36X controller, so could possibly be a driver issue... but I can't confirm!
 

Attachments

Last edited:

My Computer

System One

This is a hardware error that's reported by your CPU (and not by Windows). As such, analyzing the dump file will be very frustrating.

Of note is the error that it finds - it cannot locate symbols for PSHED.dll
I've seen at least 2 other of these errors on the web recently. One remains unsolved, the other is likely to be caused by a component of Avast that the user had installed. I haven't received any information about what Avast product he is using, nor if uninstalling it has solved the BSOD's.

But, these other 2 have had a couple of weeks of troubleshooting so they'll give you a "jump start" on the process.

First, get a start on these things to rule out some of the more common issues: BSOD troubleshooting preliminaries - Vox

Next, set up the system to use Driver Verifier according to these directions. Read the directions carefully BEFORE starting - as it can cause your system to not boot into Windows (from this post: BSOD 0x124. Please Help! - Tech Support Forum ):
To do this, I'd like to try it in several stages:
- Testing only non-Microsoft drivers
- Testing only Microsoft drivers
- Testing all drivers

To do this, follow the instructions here, modifying the BOLDED step to change the drivers that are verified. Please upload the dump files as they occur, if you don't get a dump within 24 hours, switch to the next step:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
Click to expand...
Click to expand...
 

My Computer

System One

Thanks for the insight! I didn't associate my errors with PSHED.dll... but after some searching, I tried a quick fix... I ran SFC /scannow

and it fixed my errors! Must have been a corrupt .dll perhaps?

Thanks for the help though!
 

My Computer

System One

SFC.EXE /SCANNOW worked for you? It hasn't worked for the others with this error.
Different errors give different results - even if the errors seem to be similar.
 

My Computer

System One

The BSOD is back... this time while playing a game or while creating a backup... I have Acronis True Image Home installed, and have read that this might be causing some issues... has anything experienced issues with it?
 

My Computer

System One

What happens if you re-clock your cpu back to original frequency? If it happened while you were playing a game that indicates you might be pushing the cpu too far.
 

My Computer

System One

  • Manufacturer/Model
    Sony Vaio Z46GDU
    CPU
    [email protected] w/6MB L2 cache 1066MHz FSB
    Memory
    6GB DDR3 1066MHz SDRAM
    Graphics card(s)
    9300M GS 256MB + Intel Integrated 4500MHD
    Monitor(s) Displays
    13.1" WXGA True Colour Tough
    Screen Resolution
    1600x900
    Hard Drives
    320GB SATA 7200RPM
    Internet Speed
    1MB/s
Frostmourne said:
What happens if you re-clock your cpu back to original frequency? If it happened while you were playing a game that indicates you might be pushing the cpu too far.
Click to expand...

I will try this tomorrow for sure... I have run plenty of stress tests without blue screens, but it could be that my CPU has finally given out.

A 2.13GHz running at 3.20GHz for over two years should give out eventually ;)
 

My Computer

System One

By the way, Driver Verifier indicated there was only one unverified driver, asio.sys, which I believe is related to my Asus DH Remote... I was getting BSODs before I installed this driver, so I don't think this is the cause.
 

My Computer

System One

A quick look at the dump files shows a problem with a hardware device, and most likely it's involved with a compatibility issue.

A more indepth analysis doesn't give us much more information.

I'd first suggest stopping any overclocking and return the system to default values. If this stops the BSOD's, then it's the fault of the overclock.

If it doesn't stop them, then it's either (IMO) a Windows corruption or a hardware problem. The Windows issue is easiest to address - it'll require a wipe and reinstall of the operating system - so you'll have to backup all of your stuff first.
 

My Computer

System One

usasma said:
A quick look at the dump files shows a problem with a hardware device, and most likely it's involved with a compatibility issue.

A more indepth analysis doesn't give us much more information.

I'd first suggest stopping any overclocking and return the system to default values. If this stops the BSOD's, then it's the fault of the overclock.

If it doesn't stop them, then it's either (IMO) a Windows corruption or a hardware problem. The Windows issue is easiest to address - it'll require a wipe and reinstall of the operating system - so you'll have to backup all of your stuff first.
Click to expand...

Thanks - I really appreciate your help on this... the more I look at this, the more I think my Vista installation was corrupt. About a month back, when I first started getting these BSODs, I had just format and reinstalled Windows...

Right now, I am running a full back-up using Acronis True Image - I've noticed that I can pretty consistently get a BSOD with this program... this time, I've clocked to default settings. So if I get a BSOD, I can eliminate the overclocking as the issue.

I'll run MemTest and stress out my memory - that may be causing it too somehow - once I eliminate that as a reason, it points more and more towards a Windows corruption.

To be honest, I feel like it's related to one of four RAID controllers I have in my system... but all have Vista-ready drivers install
 

My Computer

System One

Hi -

Be sure to update Marvel Yukon Ethernet and Realtek wifi NIC drivers -

Update Silicon Image Serial ATA Raid driver . . .
[COLOR=#000ff]SiWinAcc.sys Mon Nov 01 12:21:31 2004 (41868CBB)[/COLOR]

This Asus utility driver is especially BSOD-capable
AsIO.sys Wed Dec 21 00:55:21 2005 (43A91879)

PC Log-me-in driver -
vncmirror.sys Fri Mar 14 10:42:46 2008 (47DAB916)

Regards. . .

jcgriff2

.

EDIT: DID THIS INSTALL COME FROM AN ACRONIS TRUE IMAGE ? If so, re-install again with the Vista DVD itself.

.
 

My Computer

System One

  • Manufacturer/Model
    HP dv7-1020us
    CPU
    Intel P7350 Core2 Duo @2GHz
    Memory
    4096mb DDR2 SDRAM
    Graphics card(s)
    NVIDIA GeForce 9600M GT
    Sound Card
    IDT
    Hard Drives
    Fujitsu 320gb SATA HDD 5400RPM
    Mouse
    Logitech USB
    Internet Speed
    Intel 5100
The BSOD occurs because of a fault condition related to a particular execution of a driver. So you can (for example) use your video drivers for hours in a game and then get a BSOD when exiting (because of the change in things that the driver is doing).

Overclocking may/may not affect this.
 

My Computer

System One

jcgriff2 said:
Hi -

Be sure to update Marvel Yukon Ethernet and Realtek wifi NIC drivers -

Update Silicon Image Serial ATA Raid driver . . .
SiWinAcc.sys Mon Nov 01 12:21:31 2004 (41868CBB)

This Asus utility driver is especially BSOD-capable
AsIO.sys Wed Dec 21 00:55:21 2005 (43A91879)

PC Log-me-in driver -
vncmirror.sys Fri Mar 14 10:42:46 2008 (47DAB916)

Regards. . .

jcgriff2

.

EDIT: DID THIS INSTALL COME FROM AN ACRONIS TRUE IMAGE ? If so, re-install again with the Vista DVD itself.

.
Click to expand...

Step by step, this is what I did... I uninstalled VNC and the associated driver. I got a BSOD after doing this... I then uninstalled ASUS DH Remote... I got a BSOD after doing this... I then updated the Marvell drivers - had a few BSODs while doing this, but eventually got it working... My final update will be the Realtek driver...

and yes the Vista install was done from the Vista DVD - not from a backed-up image.
 

My Computer

System One

usasma said:
The BSOD occurs because of a fault condition related to a particular execution of a driver. So you can (for example) use your video drivers for hours in a game and then get a BSOD when exiting (because of the change in things that the driver is doing).

Overclocking may/may not affect this.
Click to expand...

Right - given that I've been running stable for almost 2 yrs on an overclocked system, I don't think this is what's causing the BSODs. It's got to be a driver incomptability, but now I'm running out of options as to what could be causing it!
 

My Computer

System One

slaman said:
usasma said:
The BSOD occurs because of a fault condition related to a particular execution of a driver. So you can (for example) use your video drivers for hours in a game and then get a BSOD when exiting (because of the change in things that the driver is doing).

Overclocking may/may not affect this.
Click to expand...

Right - given that I've been running stable for almost 2 yrs on an overclocked system, I don't think this is what's causing the BSODs. It's got to be a driver incomptability, but now I'm running out of options as to what could be causing it!
Click to expand...

Well, you know best - so have fun fixing it yourself.
 

My Computer

System One

usasma said:
slaman said:
usasma said:
The BSOD occurs because of a fault condition related to a particular execution of a driver. So you can (for example) use your video drivers for hours in a game and then get a BSOD when exiting (because of the change in things that the driver is doing).

Overclocking may/may not affect this.
Click to expand...

Right - given that I've been running stable for almost 2 yrs on an overclocked system, I don't think this is what's causing the BSODs. It's got to be a driver incomptability, but now I'm running out of options as to what could be causing it!
Click to expand...

Well, you know best - so have fun fixing it yourself.
Click to expand...

Your help has really been appreciated! To be honest, I've never had such great responses when I've posted on forums before. Thanks a lot!

I think I'm going to just re-format my master partition and reinstall Vista. I just got another BSOD and I've uninstalled most drivers and am on a regular clock.
 

My Computer

System One

If it matters to anyone following this thread, I found out that the issue was caused by Acronis True Image. I uninstalled it completely and used the Acronis Clean Up tool... seems a few other people are facing BSODs with this installed on their system.

Needless to say, I'll never be using an Acronis product again!
 

My Computer

System One

slaman said:
If it matters to anyone following this thread, I found out that the issue was caused by Acronis True Image. I uninstalled it completely and used the Acronis Clean Up tool... seems a few other people are facing BSODs with this installed on their system.

Needless to say, I'll never be using an Acronis product again!
Click to expand...

Just an update - since uninstalling, I have never seen this BSOD again. Looks like I found the culprit! Thanks for everyone's help!
 

My Computer

System One

You must log in or register to reply here.
Back
Top