Need a Debugging read

[manolz]

Ran my PC under Prime95 to see if it was stable. After I stopped my test the PC crashed BSOD. I had no errors from Prime95, just wondering if I can get a read on why it crashed.

I've run memtest for hours and my memory passed.
Thanks

 

[zigzag3143]

Ran my PC under Prime95 to see if it was stable. After I stopped my test the PC crashed BSOD. I had no errors from Prime95, just wondering if I can get a read on why it crashed.

I've run memtest for hours and my memory passed.
Thanks

Memory corruption and since you say it passed memtest it is probably caused by a driver.

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/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

 

[manolz]

Ok I've attached my minidump, All my details are inside. I had to system restore in Safe-Mode.

Thanks

 

[manolz]

http://www.sevenforums.com/crashes-debugging/117980-bsod-desperate-please-help.html

I've followed some of the suggestions in this post as the Elby title showed during my BSOD. Going to be uninstalling programs by Elaborate Bytes, updating Realtek driver and installing MSE.

I'll run driververifier once again to see if my pc crashes.

 

[writhziden]

Do you currently have an antivirus on your computer (before MSE)?

 

[manolz]

Do you currently have an antivirus on your computer (before MSE)?

Nope

 

[manolz]

Do you currently have an antivirus on your computer (before MSE)?

Have removed Elaborate Bytes material and run a quick scan - MSE.
Going to system restore and Driver Verifier to see if I make it into Windows.

 

[manolz]

Ok I made it back into Windows 7 no problems.
Thanks once again

manolz

note
I'll be switching Verifier off

 

[writhziden]

Do you currently have an antivirus on your computer (before MSE)?

Nope

Alright, just wanted to make sure you weren't installing a second antivirus. Let us know how things go and post any dump files if you get another BSOD.

 

[manolz]

Do you currently have an antivirus on your computer (before MSE)?

Nope

Alright, just wanted to make sure you weren't installing a second antivirus. Let us know how things go and post any dump files if you get another BSOD.

Thanks,

I'm assuming Driver Verifier turns itself off after a reboot? I made my way back into verifier and can't see an option to stop the service. I'll leave things how they are and post back if I come across another BSOD. Thanks again

 

[writhziden]

Thanks,

I'm assuming Driver Verifier turns itself off after a reboot? I made my way back into verifier and can't see an option to stop the service. I'll leave things how they are and post back if I come across another BSOD. Thanks again

You said you used system restore to go back, right? That probably restored it back to before you turned verifier on. It also would have removed any driver updates you have done between when you made the restore point and when you restored.

 

[manolz]

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

 

[writhziden]

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

Ah, guess I misunderstood. Odd that it was turned off when you came back, though. I haven't used Verifier much myself, and never got it to BSOD when I did, so I turned it off after 36 hours manually.

 

[zigzag3143]

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

 

[manolz]

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

Okay good to know.

Thanks again !

 

[zigzag3143]

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

Okay good to know.

Thanks again !

My pleasure and let us know if you need help.

If it doesnt crash in that time period we can make it crash.

 

[manolz]

New minidump.

 

[writhziden]

New minidump.

Your bsod was caused by trixx.sys; please remove all trixx software for further testing.

 

[zigzag3143]

New minidump.

Your bsod was caused by trixx.sys; please remove all trixx software for further testing.

Might want to mention that they were driver verified.

 

[writhziden]

Might want to mention that they were driver verified.

Aye... I suppose it is up to the OP to continue testing with driver verifier running after uninstalling the offending driver. I think it might be safe at this point to disable verifier and run normally and not remove trixx software.

Thanks zigzag3143. I assumed the verifier was intentional, but after reading over the previous posts again, now I see your point.