Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSOD


  • Please log in to reply
24 replies to this topic

#1 AkaAlias

AkaAlias

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 13 January 2011 - 05:37 AM

Hi,

Since a few days my system is experiencing random crashes. Sometimes within a few minutes after booting, sometimes it takes a few hours.
The last dumpfile had 'verifier' enabled, but i'm not sure if my settings were correct. I followed these instructions: http://www.techsupportforum.com/forums/f217/driver-verifier-windows-7-and-vista-bsod-related-473665.html But my win7 version is in Dutch, so i might have been mistaken while selecting the proper options due to a translation error on my part...

Any help would be very much apreciated, thank you.

System specs:

Quadcore Intel Core 2 Quad Q6600, 2400Mhz (9x267)
Asus Striker Extreme (2PCI, 2 PCI-Ex1, 3 pci-e x16, 4 ddr2 dimmm)
nvidia Ge Force 8800 GTX (768 MB)nVIDIA nforce 680i SLI
4x crucial tech 1GB DDR2 SDRAM (5-5-5-18 @ 400 Mhz)

3x samsung hd501lj scsi disk device 500GB
1x Hitachi HDS722020ALA SCSI Disk Device 1863GB


==================================================
Dump File : 011311-25896-01.dmp
Crash Time : 13-1-2011 10:40:25
Bug Check String : DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug Check Code : 0x000000c9
Parameter 1 : 00000000`00000220
Parameter 2 : fffff880`04402818
Parameter 3 : fffff980`07adedc0
Parameter 4 : fffffa80`039ddbb0
Caused By Driver : HIDCLASS.SYS
Caused By Address : HIDCLASS.SYS+2818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011311-25896-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 266.288
==================================================

==================================================
Dump File : 011311-21606-01.dmp
Crash Time : 13-1-2011 9:18:24
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`000b1989
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`000b791a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011311-21606-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 271.048
==================================================

==================================================
Dump File : 011211-41137-01.dmp
Crash Time : 12-1-2011 13:07:52
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`000b899c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`03b057c1
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011211-41137-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.592
==================================================

==================================================
Dump File : 011111-39608-01.dmp
Crash Time : 11-1-2011 14:11:46
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03a72b6c
Parameter 3 : fffff880`031a7fd8
Parameter 4 : fffff880`031a7840
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1eb6c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011111-39608-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.592
==================================================

==================================================
Dump File : 110410-459875-01.dmp
Crash Time : 4-11-2010 1:30:13
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000006
Parameter 3 : 00000000`0000000a
Parameter 4 : fffffa80`0621bb20
Caused By Driver : nvstor.sys
Caused By Address : nvstor.sys+1950b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\110410-459875-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262.144
==================================================

Edited by AkaAlias, 13 January 2011 - 06:05 AM.

Posted Image

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:47 PM

Posted 13 January 2011 - 08:02 AM

Multiple and varied blue screen errors can often be caused by a bad motherboard. Rule out ram first by running memtest (http://www.memtest.org/), but I'm guessing the problem goes deeper than ram.

#3 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:47 PM

Posted 13 January 2011 - 11:35 PM

I would upgrade your drivers for your nVidia based motherboard.

#4 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 14 January 2011 - 02:24 AM

Hi, thank you for your advice.

I ran the Memory Diagnostic Test in Win 7 and memtest86, the last one ran for 7 passes. Both showed no errors.
When installing the latest MoBo drivers, should/can I uninstall the old ones first? Also Asus aparently doesn't have win7 64 bit drivers, should i use the Vista drivers?
Posted Image

#5 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:47 PM

Posted 14 January 2011 - 02:32 AM

If you know your chipset go here http://www.nvidia.com

#6 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:47 PM

Posted 14 January 2011 - 08:05 AM

What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

#7 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 14 January 2011 - 10:52 AM

Hi, i updated the chipset drivers. I also ran chckdsk for all internal HDD's, no errors. I'm not sure if it found any errors on the C: drive, as this one ran when i was asleep.

The last program installed before BSOD problems was Silverlight last januari the 3th. The BSOD started showing up since the 11th. The computer appeared to be working fine last week.

I also read somewhere that it could be a power issue, disabling all power save options was adviced. I did this yesterday. I haven't had a BSOD since. I'll post if and when it happens again. Thanks for the help everyone.
Posted Image

#8 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:47 PM

Posted 14 January 2011 - 11:00 AM

May I ask how you ran checkdisk (method and switch)?

#9 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 14 January 2011 - 11:39 AM

I ran chckdsk by right-clicking on the drive icon. All drives accept c: were checked while in Windows, c: was checked the same way but required a reboot to start checking.
Posted Image

#10 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:47 PM

Posted 14 January 2011 - 11:42 AM

Okay. Please open an elevated command prompt (right-click on a command window and "open as administrator"). Type chkdsk /r and press ENTER. You'll be told the drive is locked and asked if you want to run it at the next boot. Say yes, exit the command window, reboot.

#11 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 21 February 2011 - 05:43 AM

Hi,

Since last chckdsk all problems appeared te be gone. Then suddenly last thursday morning i had a major crash.
After the crash, I couldn't boot to windows, couldn't load win7 CD.

After removing all but one memory bank, and a broken HDD that had a damaged boot sector and damaged Master File Table. I was able to boot from CD and reinstall windows on a new HDD. After finally getting it to boot i checked my memor one by one.

I have 4 sticks of 1Gb crucial ballistix ddr2 pc6400 800mhz memory.
2 stickes appeared to work fine on all slots,
1 stick only worked in memory slot 1
the last stick worked in all slots except for memory slot 2.

I now have only 2 sticks plugged in to the Mobo.
I ran the windows memory diagnostic tool and memtest86 for a few passes, no errors.
I ran prime95 torture test for about 15 hours, without errors or crashes and was convinced the problems were solved.

Then today, with only two firefox screens open, and winamp idling in the background it crashed again to BSOD, a memory dump was made:
Before being able to do anything on the next boot, it crashed again after 5 sec. in windows.

In eventvwr it gives a critical error "Kernel-Power" event-id "41"
The error usually preceding the Kernel-Power error is: event-id 6008 and event-id 1101

I haven't got any idea's left on what to do.

*edit*
I attached a .zip of the last minidump file.

Attached Files


Edited by AkaAlias, 21 February 2011 - 06:47 AM.

Posted Image

#12 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:47 PM

Posted 21 February 2011 - 09:19 AM

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Compliments of Broni

#13 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 21 February 2011 - 11:05 AM

Here are the BSOD dumps.

==================================================
Dump File : 022111-39624-01.dmp
Crash Time : 21-2-2011 11:20:59
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa7f`ffffffe0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02af5b7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\022111-39624-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 287.472
==================================================

==================================================
Dump File : 022111-63227-01.dmp
Crash Time : 21-2-2011 11:16:23
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa7f`ffffffe0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02aebb7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\022111-63227-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.576
==================================================

==================================================
Dump File : 021911-22729-01.dmp
Crash Time : 19-2-2011 19:43:14
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00008886
Parameter 2 : fffffa80`01182f00
Parameter 3 : fffffa80`01643ac0
Parameter 4 : 00000000`00000704
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-22729-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 286.160
==================================================

==================================================
Dump File : 021911-28563-01.dmp
Crash Time : 19-2-2011 19:26:18
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+2cefea
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-28563-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 289.776
==================================================

==================================================
Dump File : 021911-27986-01.dmp
Crash Time : 19-2-2011 17:21:48
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000010
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02afab7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-27986-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 284.832
==================================================

==================================================
Dump File : 021911-32994-01.dmp
Crash Time : 19-2-2011 16:55:45
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000010
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02af0b7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-32994-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 288.752
==================================================

==================================================
Dump File : 021911-35069-01.dmp
Crash Time : 19-2-2011 16:17:41
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0005dbc4
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`000178d2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-35069-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 285.632
==================================================

==================================================
Dump File : 021911-40919-01.dmp
Crash Time : 19-2-2011 15:47:21
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0000c9d2
Parameter 3 : 00000000`00000003
Parameter 4 : 00000000`0004cba0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-40919-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 288.672
==================================================

==================================================
Dump File : 021911-15397-01.dmp
Crash Time : 19-2-2011 2:32:21
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff6bf`ffffffe0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02afa77e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-15397-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 282.304
==================================================

==================================================
Dump File : 021911-16660-01.dmp
Crash Time : 19-2-2011 2:09:28
Bug Check String : INTERRUPT_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000003d
Parameter 1 : fffff880`071735d0
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`06d0d4c6
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+84c6
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021911-16660-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.584
==================================================

==================================================
Dump File : 021811-14492-01.dmp
Crash Time : 18-2-2011 23:39:51
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`029f590d
Parameter 3 : fffff880`0338b160
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\021811-14492-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 284.936
==================================================
Posted Image

#14 AkaAlias

AkaAlias
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Location:Roermond, The Netherlands
  • Local time:04:47 PM

Posted 21 February 2011 - 01:30 PM

And the latest one:

==================================================
Dump File : 022111-39795-01.dmp
Crash Time : 21-2-2011 19:26:51
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa7f`ffffffe0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02a98b7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\022111-39795-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.584
==================================================
Posted Image

#15 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:47 PM

Posted 21 February 2011 - 02:15 PM

How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    Posted Image
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    Posted Image

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    Posted Image
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :)

Compliments of Billy O'Neal.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users