BSOD while idle, surfing the net or gaming: just randomly

[PedroPortnoy]

Hi guys.

I'm new to this forum and I'm new to BSOD's solving, but my system started to randomly crash once in a while, and I noticed that the BCCode was always the same, D1 I think. It would be great if you could help me solving this issue.

I have Windows 7 Ultimate x64

Thanks

I'm sorry for my terrible English

edit: I forgot to say that I reinstalled windows 7 just 2 days ago and i had BSOD before. But since I reinstalled it, I had 2 BSOD already, both when I was away from my computer. Hope this helps you helping me

 

[zigzag3143]

Hi guys.

I'm new to this forum and I'm new to BSOD's solving, but my system started to randomly crash once in a while, and I noticed that the BCCode was always the same, D1 I think. It would be great if you could help me solving this issue.

I have Windows 7 Ultimate x64

Thanks

I'm sorry for my terrible English

edit: I forgot to say that I reinstalled windows 7 just 2 days ago and i had BSOD before. But since I reinstalled it, I had 2 BSOD already, both when I was away from my computer. Hope this helps you helping me

You uploaded the app instead of the data try this method




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.



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.

 

[PedroPortnoy]

Sorry, it was a dumb mistake. This are the correct files.

 

[PedroPortnoy]

Anyone? Please? I really have no idea why I had those BlueScreens, if anyone could help me it'd be great!

Thanks

 

[PedroPortnoy]

I just had another BSOD. Here are the files.

Please help me. Thanks

 

[zigzag3143]

memory exception caused by an as yet un-named driver. These need updating

Alpham264.sys    3/20/2007 5:51:03 AM        fffff880`09f9f000    0051f8d4`09fa4500    0x0052005400005500    0x45ffae87                        
Alpham164.sys    7/23/2007 3:57:03 AM        fffff880`09f62000    002ff8d4`09f6ef00    0x003000540000cf00    0x46a45f4f                        
AsInsHelp64.sys    1/4/2008 1:36:10 AM        fffff880`0b600000    0053f8ce`0b605000    0x0054004e00005000    0x477dc5ca                        
ALSysIO64.sys    4/19/2009 3:41:04 PM        fffff880`0be7d000    002ff8d4`0be85000    0x0030005400008000    0x49eb7e50                        
BULKUSB.sys    4/20/2009 1:32:53 AM        fffff880`0a1f1000    425540d5`0a1fd000    0x425548550000c000    0x49ec0905                        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        fffff880`05fd7000    fffff881`05fe4000    0x000000010000d000    0x4a1151c0                        
Tosrfhid.sys    5/19/2009 9:23:51 PM        fffff880`09e84000    fffff880`09e99b00    0x00015b00    0x4a135ba7                        
dump_iaStor.sys    6/4/2009 9:53:40 PM        fffff880`04cb3000    fffff880`04dcf000    0x0011c000    0x4a287aa4                        
iaStor.sys    6/4/2009 9:53:40 PM        fffff880`010cc000    fffff880`011e8000    0x0011c000    0x4a287aa4                        
tosporte.sys    6/16/2009 6:48:47 AM        fffff880`0964a000    d6e7cf67`0965b000    0xd6e7d6e700011000    0x4a37788f

also

Please run driver verifier to find which driver is the offender.

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.

 

[PedroPortnoy]

I forgot to say that my system is overclocked from factory. Do you think it is possible that an unstable OC is causing this? Or the information I uploaded tells you it is definitly driver-related?

If you think the OC may be causing this, I can run some stress tests on my system just to be sure it is not the OC.

What do you think?

 

[Anthony]

Yes!! Remove the overclock then test again!!