BSOD when installing Warcraft III, when running Windows Update, etc.

[JerryOnion]

Ok guys, I need help. Followed the instructions and uploaded the BSOD dump and system file zip, and I've listed my system specs.

I'm coming from a fresh installation of Windows 7 Ultimate x64 (Full Retail Version).

I encounter random BSODs involving different files whenever I do anything (e.g. opening a web page, opening control panel, opening a flash website in Opera, etc.). The most consistent way I can replicate the BSODs is to either install Warcraft III or run Windows Update - those ALWAYS give me BSODs halfway.

The messages vary from some error with WIN32K.sys to NTFS.sys, to some "System Service Exception" error message.

What I've already tried -
1) Booted up with 1 stick of RAM
2) Swapped between RAM slots
3) Run memtest for 2 hrs (no errors)
4) Reinstalled Windows (multiple times)
5) Changed installation hard drive (installed Win7 on Samsung HDD instead of Supertalent SSD)
6) Used driver files from Biostar Website
7) Used driver files from Biostar OEM disc (Supplied with Motherboard)
8) Removed 9800GT and booted up with Integrated HD 4250 Graphics
9) Removed all external devices sans the Keyboard, Mouse, and Wireless adapter.
10) Run SFC /Scannow on command prompt per someone's suggestion (detected and repaired some files, but didn't solve BSOD problem)
11) Run Chkdsk /r /f (no errors detected)

So . . . I am rather at a loss here. Right now I'm typing this on said problematic PC, but BSOD might come at any moment and I might have to retype this again

Since I have zero ability at deciphering dmp files, I'll need your help guys. HELP !

 

[JMH]

Note your bios64.sys file is dated 2003. That needs to be updated before anything else.

BIOS64.sys    6/8/2003 11:12:00 AM        fffff880`02fae000    fffff880`02fb6000    0x00008000    0x3ee27f50

These all were caused by a memory exception.
Please run these two tests to verify your memory and find which driver is causing the problem.
I know you have run memtest for two hours but that is often not enough.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running forat least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[JerryOnion]

Ok, I ran verifier.exe on each non-Microsoft driver and eliminated one of the culprits (AMD usb driver) that was causing the crashes.

Then I tried installing Warcraft III again. Around the 70% mark I got a IRQL_NOT_LESS_OR_EQUAL BSOD.

Then I restarted and opened Control Panel and the IRQL_NOT_LESS_OR_EQUAL BSOD popped out again.

At least the BSOD is consistent now

I'm running Memtest as we speak.

 

[JerryOnion]

Ok, finished 2nd run of memtest after 10 hours. No errors for either stick.

I tried a fresh installation of Win7 on my other hard disk and still experienced frequent BSODs, only now of the SYSTEM_SERVICE_EXCEPTION nature.

The log files and report are attached, please examine and see if u can figure out anything.

 

[zigzag3143]

Ok, finished 2nd run of memtest after 10 hours. No errors for either stick.

I tried a fresh installation of Win7 on my other hard disk and still experienced frequent BSODs, only now of the SYSTEM_SERVICE_EXCEPTION nature.

The log files and report are attached, please examine and see if u can figure out anything.

The newest (most recent) crashes are still memory exceptions. It is either memory or a driver and the two tests are the only way to diagnose which.

BTW none of these are driver verifier "enabled" so be sure you are following the directions for it

 

[JerryOnion]

Ok, finished 2nd run of memtest after 10 hours. No errors for either stick.

I tried a fresh installation of Win7 on my other hard disk and still experienced frequent BSODs, only now of the SYSTEM_SERVICE_EXCEPTION nature.

The log files and report are attached, please examine and see if u can figure out anything.

The newest (most recent) crashes are still memory exceptions. It is either memory or a driver and the two tests are the only way to diagnose which.

BTW none of these are driver verifier "enabled" so be sure you are following the directions for it

Erm, I forgot to run verifier.exe for the fresh installation, sorry about that. Will try today and repost.

 

[JMH]

Thanks.
Good luck!