BSOD on Win7 x 64 2 days old

[chetansha]

s Windows 7 . . . -x64 ? - the original installed OS on the system? - full retail version? - What is the age of system (hardware)? 6 months - What is the age of OS installation (have you re-installed the OS?) 2 days

HARDWARE DETAILS:
CPU Type QuadCore AMD Phenom II X4, 3400 MHz (17 x 200)
Motherboard Name Asus Crosshair IV Formula
Motherboard Chipset AMD 890FX,
Memory 8192 MB (DDR3-1333 DDR3 SDRAM)
DIMM1: Corsair Vengeance CMZ8GX3M2A1600C9 4 GB DDR3-1333 DDR3 SDRAM DIMM2: Corsair Vengeance CMZ8GX3M2A1600C9 4 GB DDR3-1333 DDR3 SDRAM BIOS Type AMI (04/01/11)
Display: Video Adapter ATI Radeon HD 5700 Series (1024 MB)
3D Accelerator ATI Radeon HD 5770 (Juniper)
Monitor LG M227WA [22" LCD] (210213571)
Multimedia:
Audio Adapter ATI Radeon HDMI @ ATI Juniper/Broadway - High Definition Audio Controller
Audio Adapter C-Media CMI8738/C3DX Audio Device

 

[zigzag3143]

s Windows 7 . . . -x64 ? - the original installed OS on the system? - full retail version? - What is the age of system (hardware)? 6 months - What is the age of OS installation (have you re-installed the OS?) 2 days

HARDWARE DETAILS:
CPU Type QuadCore AMD Phenom II X4, 3400 MHz (17 x 200) Motherboard Name Asus Crosshair IV Formula (2 PCI, 4 PCI-E x16, 4 DDR3 DIMM, Audio, Gigabit LAN, IEEE-1394) Motherboard Chipset AMD 890FX, AMD K10 System Memory 8192 MB (DDR3-1333 DDR3 SDRAM) DIMM1: Corsair Vengeance CMZ8GX3M2A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz) DIMM2: Corsair Vengeance CMZ8GX3M2A1600C9 4 GB DDR3-1333 DDR3 SDRAM (9-9-9-24 @ 666 MHz) (8-8-8-22 @ 592 MHz) (7-7-7-19 @ 518 MHz) (6-6-6-16 @ 444 MHz) BIOS Type AMI (04/01/11) Display: Video Adapter ATI Radeon HD 5700 Series (1024 MB) 3D Accelerator ATI Radeon HD 5770 (Juniper) Monitor LG M227WA [22" LCD] (210213571) Multimedia: Audio Adapter ATI Radeon HDMI @ ATI Juniper/Broadway - High Definition Audio Controller Audio Adapter C-Media CMI8738/C3DX Audio Device

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[chetansha]

I was editing my post ( i forgot to attach earlier > sorry

 

[zigzag3143]

I was editing my post ( i forgot to attach earlier > sorry

No problem. This crash was probably caused by memory corruption. EIrher RAM or a driver. Please run these two tests to find out which.
.


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 for at 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

 

[chetansha]

Crash after driver verifier

Hi
I was sure about the memories, hence I ran the driver verifier first.
AS soon as i close ASUS Smart Doctor i got BSOD. Attaching the xml file. Hope it helps.

 

[zigzag3143]

Hi
I was sure about the memories, hence I ran the driver verifier first.
AS soon as i close ASUS Smart Doctor i got BSOD. Attaching the xml file. Hope it helps.

We need the DMP files. Are you still having new ones?