Bsod 6.1.7601.2.1.0.256.1

[Adam23]

Hey guys, I'm new to this website so I appologise if anything is wrong.

For the last few days i have been experiencing BSOD with error number 6.1.7601.2.1.0.256.1, i build computers and usually just format them (after i check hard ware, connections ect) but i have too much stuff on my pc just to format.

I have included the Zips required, I have also noticed cpu spiking.

Thank's again for You're help.

Windows 7 x64 Ultimate
Full Retail Version
Pc is always being upgraded so age is around 12 months

 

[JMH]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



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-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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






Driver Verifier

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.

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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.
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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Adam23]

I used memtest about a month ago, and it came back with errors (after 20 minutes loads of loops of errors at least 20 thousand) thing is i got told that the memtest dont like anything over 8gb of ram, i use linx memory and cpu tester for 24 hours and its fine, no blue screens nothing, my mate has bought the new gtx 670 and ever since installing the new 301 driver, he too as experienced BSOD, so its making me think, can graphics drivers cause BSOD?? and how would i know if a ram dimm is failing?

 

[JMH]

Submit any new DMP's for analysis.

NB.
It is much easier to find patterns, etc, when there is more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

Please upload them when you have collected 2 or more.

 

[Adam23]

Thanks for the help so far guys, can i ask, whats DMP??

 

[JMH]

A DMP is what is collected after you have experienced a BSOD.
We do need the 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 etc.

 

[Adam23]

Something else i forgot too mention, my CPU usage has been 50% minimum spiking to 100% then back down, but in my task manager i notice a process called "wmiprvse.exe" i have read on google this can cause problems, BSOD, freezing, High cpu usage ect, do you guys know what it is?

 

[Adam23]

Also i had a Bios update available, the last time i installed a bios update on this board it would not post at first, could a bad bios update cause BSOD? and Memtest86 errors?

 

[JMH]

If / when you crash submit the DMP's for analysis.
We will then have a far better idea about what is going on there.

 

[Adam23]

Ok happened again, but i ran memtest86 with no errors, so its making me think what could it be, I'm aiming towards drivers, thanks guys!, ps also including the DMP. file

 

[JMH]

Have you run Driver Verifier yet?
Results?
Refer Post 2.

 

[Adam23]

Below are my results, just followed You're instructions.

 

[zigzag3143]

Below are my results, just followed You're instructions.

Both driver verified and related to your video driver. I would re-install the newest driver available using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver.

In order to do that we recommend using
Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[Adam23]

The other day i ran the Metro 2033 Benchmark and it was really choppy, i went on a uninstall spree last night, an the problem seems to have gone, i ran Prime 95 for another 6 hours and everything came back clean, so did memtest86+ and memtestCL.

Will have a good luck to see if current video drivers are on my Pc

Thank's again for all You're input mate, you are a star

 

[Adam23]

Hey can you lock this Thread now please, or delete it thanks again

 

[Adam23]

Thought i would report back, it turned out to be a fault stick of ram, how great is it best to run 8GB in dual channel or 12GB in single channel?

 

[zigzag3143]

Thought i would report back, it turned out to be a fault stick of ram, how great is it best to run 8GB in dual channel or 12GB in single channel?

Depends on your needs. In dual you will get a bit more speed, with 12 gigs you will have the capacity to do more things.

Either way I doubt you are using any where near 8 gigs.

 

[Adam23]

It was the Corsair Vengeance Kit 16gb, i have ordered a replacement Module, should be here tomorrow, and you are right, playing BF3 i only used 3-4GB Max.

Thanks bud

 

[zigzag3143]

My pleasure in both threads.


Ken