Random BSOD's

[usasma]

Check out the "Usual Causes" line at this link: BSOD Index

Next time you restart your system, repeatedly tap the F8 key just before the Windows Splash Screen shows up. This'll get you to a menu for Safe Mode. Further down the list will be an entry to "Disable automaic restart.....". Select that and let the system start. At the next BSOD the system will halt and allow you to read the screen.

You can also, from within Windows, go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
In the window that opens up, select the Advanced tab, then the Startup and Recovery Settings button.
In the next window that opens, in the lower half will be a section called System Failure
Remove the checkmark from the box that says "Automatically restart" and then click OK to exit the dialog.

 

[tomatpasser]

had a blue screen today

It said:

0x1E (0x0, 0x0, 0x0, 0x0)



(Lots of zeros)
There was no other error message or anything..

 

[usasma]

I'd go back and run the diagnostics again:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
Also run the SSD diagnostics again.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)

Beyond that, I'm pretty sure that this is a hardware issue, so I'd have to suggest a hardware stripdown as a last resort to determine the cause: Hardware Troubleshooting Via System Stripdown

 

[tomatpasser]

ok so i did those tests with speedfan and memtest again but they didn't show anything noteable. I also ran the suggested malware scan.

Then today when i turned on my computer and it had been turned on for a few minutes it suddenly restarted with a weird crunchy sound. I'm not sure if i also saw it light up a bit :S

It was booting but i shut it down fast and left it because i didn't have time to look at it a the time.

Then about an hour later i tried to turn it on, but it wouldn't turn on at all. There's no response when i press the power on button.

I'm thinking the power supply is dead? But i have no clue really, could it be the motherboard?

Hoping any of you have a clue here

Thanks in advance

 

[usasma]

Did you also run the Hard Drive diagnostic? If so, what were the results there?

If it doesn't even turn on, the first place to check is the PSU - but don't go out buying new parts just yet as this can happen with other components (such as the mobo). Try testing the PSU with one of these links: psu testing - Google Search

Try this procedure to rule out as many components as possible: Hardware Troubleshooting Via System Stripdown

 

[tomatpasser]

i did the test in speedfan which showed no errors, didn't get to run any other tools before it crashed and burned tho.
I'll check your links.

 

[usasma]

I've seen some computers at work (with bad hard drives) that you can turn on - but you won't see anything on the screen. To check for this:
- unplug the system from the wall
- disconnect both cables that run to the hard drive (data and power)
- plug the system back in and see if it'll power up to get the Gigabyte splash screen (it won't boot anywhere since you don't have a hard drive connected).

If you see the splash screen, then it's usually a safe bet that the hard drive is toast. But you'll have to purchase a new hard drive to verify this (and don't buy one just on my say so - since it can be other components causing this).

 

[tomatpasser]

Disconnecting the hard disks didn't change anything. I tested the 24-pin motherboard power connector with a multimeter and but shorting out two of the pins (used this guide) and it didn't work at all.

 

[usasma]

Do you mean that the PSU isn't putting any power out on those leads?
If not, try purchasing a PSU from a place that you can return it (if it's not needed) and see if that fixes the problem.

Beyond that, the hardware stripdown is the way to go.

 

[tomatpasser]

I bought a new PSU and it's working now No bsods yet but we'll see..

 

[tomatpasser]

Ok so i still get bsods.
I guess it's the motherboard then? As i have had bsods with each of my harddisks disconnected.. before when i only had one hdd i got bsods, then i bought the ssd and installed win 7 on that one, and then i tried to disconnect my old hdd, still crashed randomly.

I've done several tests on my ram including memtest.. errors would show if they were faulty, right? I've run memtest over night 2 times with no errors.

Please tell me if there's anything i have overlooked, thanks in advance

EDIT: Or can it be CPU/GPU? Might want to test those again..

 

[usasma]

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

It can be almost anything - but it's been 3 months since the last reported BSOD
Please provide this info again: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[tomatpasser]

okey. I'm sorry about your eye problems! Hope it will all sort out


It's not 3 months since i've had a blue screen, i've just been super busy and using my laptop instead, so haven't had time to look at it :/

anyways here are the files:

 

[usasma]

The perfmon report states that your Cisco VPN is disabled - if not needed, please uninstall it. If needed, please enable it and update it - then disable it again.

Only one memory dump in the uploaded files. If you're using a disk cleanup program, please don't use it until this problem is solved.

Daemon Tools (and the Alcohol % software also) is known to cause BSOD's on Win7 systems through it's sptd.sys driver. Please uninstall the program and use this free tool to ensure that the troublesome sptd.sys driver is uninstalled: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Please update these drivers, paying particular attention to those highlighted in RED:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
sptd.sys        Sun Oct 11 16:55:14 2009 (4AD24632)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
lvrs64.sys      Tue Jul 27 04:00:02 2010 (4C4E9202)
[Color=Red]adfs.SYS        Thu Jun 26 16:52:37 2008 (48640195)[/Color]
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
truecrypt.sys   Sun Sep 05 10:23:16 2010 (4C83A7D4)
Rt64win7.sys    Thu Feb 26 04:04:13 2009 (49A65B0D)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
lvsels64.sys    Tue Jul 27 03:59:23 2010 (4C4E91DB) - Logitech Webcam
[Color=Red]bbcap.sys       Fri Nov 02 03:30:12 2007 (472AD204)[/Color] - BB Flash Recorder Mirror Miniport Driver
[Color=Red]ManyCam_x64.sys Thu Mar 13 03:46:01 2008 (47D8DBB9)[/Color]
LGBusEnum.sys   Mon Nov 23 20:36:48 2009 (4B0B38B0)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
lvbflt64.sys    Tue Jul 27 03:59:08 2010 (4C4E91CC) - Logitech Webcam
lvuvc64.sys     Tue Jul 27 04:00:43 2010 (4C4E922B)
LHidFilt.Sys    Thu Mar 18 04:51:17 2010 (4BA1E985)
LMouFilt.Sys    Thu Mar 18 04:51:24 2010 (4BA1E98C)
LVPr2M64.sys    Fri May 07 21:38:16 2010 (4BE4C088)
LGVirHid.sys    Mon Nov 23 20:36:48 2009 (4B0B38B0)
[/font]

http://www.carrona.org/dvrref.html#sptd.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#lvrs64.sys
http://www.carrona.org/dvrref.html#adfs.SYS
http://www.carrona.org/dvrref.html#cpuz135_x64.sys
http://www.carrona.org/dvrref.html#MpFilter.sys
http://www.carrona.org/dvrref.html#truecrypt.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#ManyCam_x64.sys
http://www.carrona.org/dvrref.html#LGBusEnum.sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#AtihdW76.sys
http://www.carrona.org/dvrref.html#lvuvc64.sys
http://www.carrona.org/dvrref.html#LHidFilt.Sys
http://www.carrona.org/dvrref.html#LMouFilt.Sys
http://www.carrona.org/dvrref.html#LVPr2M64.sys
http://www.carrona.org/dvrref.html#LGVirHid.sys

If the BSOD's continue after this, please run Driver Verifier according to these instructions:

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.

So, 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).

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 "Special Pool" and "Low Resource Simulation" 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.

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

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\093011-85722-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep 30 15:18:41.033 2011 (UTC - 4:00)
System Uptime: 0 days 3:22:53.172
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02e99a9b fffff880`08348fc0 00000000`00000000
BiosVersion = F5
BiosReleaseDate = 11/18/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[tomatpasser]

Ok. I updated many of the drivers (the ones i could find) and deleted and used the tool to remove Daemon Tools.

Then I installed Pro Tools, need it for some of my music recording, and it seemed like it just made everything worse, so I removed it again, to solve my computer problem first.
Many of the crashes seem to be caused by the anti-piracy software in Pro Tools.

So i removed it, and still get blue screens. I have been running with driver verifier running.

I also find a weird huge file that appeared on my secondary hdd: "DUMP1d20.tmp" modified two days ago.. do you have any idea what it is, can i use it to debug or something?

One of the minidumps said something about some memory failure, so i tried to run memtest again. After two passes it showed some errors, but i tried running 5 more passes the next day, to see if i could reproduce the errors, but it showed no errors this time.

I'm uploading a big bunch of dumps and a new perfmon report in case you need it

 

[tomatpasser]

ok i tried to run prime95 as suggested in another post you wrote earlier, where i told you it found something but we never really looked into it.

I get the same error as then, after like 5 minutes there's errors on all the "workers"

Log:

 

[usasma]

What size is the "DUMP1d20.tmp" file?

You've got memory errors - both using MemTest and using Primer 95. While bad RAM is the most likely cause, please run all 3 tests of Prime95 (Blend, Small FFT's, Large FFT's) and time how long it takes for each to generate errors. That'll give us a clue as to what's causing this.

FYI - I can't see well enough to read the memory dump files. If my suggestions don't fix it, please PM another staff member for assistance.

 

[tomatpasser]

The "DUMP1d20.tmp" file is 4.44 GB


The blend test takes as little as 20 seconds to 7 minutes to fail.

The Small FFT's test didn't show any errors after 3 hours (had to shut my pc down, it's so noiseful!) Do i have to have it running for a longer time?

The Large FFT's test showed errors in less than a minute to 5 minutes for 3 of the workers, but it took 41 minutes before the 4th worker got an error.. how can this be?

Thanks again for all the help so far, I'm really sorry about your eye problems.

 

[usasma]

I suspect that the .tmp file is a remnant of a crash that wasn't completely captured.
How much RAM do you have?
Check the date stamp on the file and see if you can recall any crashes that weren't completed that day.
Rename the file to .dmp and see if you can open it in WinDbg - that may give you more info (if it opens)

FWIW - MemTest doesn't stress the RAM when testing - Prime95 does stress it.

Blend test tests a lot of RAM, Large FFT's also tests RAM. I'd suspect that the RAM is bad (although it's possible that it's something else). Try testing each stick and each slot individually - to see if it's just one stick or not. Most brand name RAM has a lifetime warranty - so you may be able to get yours replaced. If not, purchase RAM from a place that you can return it for your money back.

 

[tomatpasser]

I have 8 gB ram (4 times 2 gB)

I tried renaming the file to .dmp and could actually open it in WinDbg. It was an 0x10D error and it points to MDPMGRNT.SYS which is one of the drivers that came with Pro Tools.. i don't remember any crashes that didn't complete but well.. might just have forgotten. There's not much help from that file, i guess.

Suspecting the RAM too. But could be the ram slots or something.
In the weekend I'll try testing each ram stick and slot like you suggested.