BleepingComputer.com: bleeping computer

Jump to content

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

bleeping computer

#16 User is offline   LucheLibre 

  • Senior Member
  • PipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 592
  • Joined: 02-February 11
  • Gender:Male
  • Location:Tennessee

Posted 09 February 2012 - 06:12 PM

After looking at some other posts, I suggest try unplugging everything from the back of the PC except the monitor and power and turn it on. Any change?
If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~

#17 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 10 February 2012 - 02:13 AM

View PostLucheLibre, on 09 February 2012 - 06:12 PM, said:

After looking at some other posts, I suggest try unplugging everything from the back of the PC except the monitor and power and turn it on. Any change?

i will give it a go this morning.

#18 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 10 February 2012 - 07:22 AM

View PostLucheLibre, on 09 February 2012 - 06:12 PM, said:

After looking at some other posts, I suggest try unplugging everything from the back of the PC except the monitor and power and turn it on. Any change?

no change

#19 User is offline   LucheLibre 

  • Senior Member
  • PipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 592
  • Joined: 02-February 11
  • Gender:Male
  • Location:Tennessee

Posted 10 February 2012 - 08:27 AM

We can check the BSODs to see if anything needs to be done about it.

But if your hard drive checks out, and the computer otherwise runs well, then I wouldn't worry about the clicks until necessary.

Use BlueScreenView to provide details about your errors.

  • Download the .zip file and extract to a folder on your desktop. Open that folder and run BlueScreenView.exe.
  • After BSV completes its scan, click Edit > Select All. Then click File > Save Selected Items and save the report to your desktop as BSOD.txt
  • Open BSOD.txt in Notepad and copy/paste all of its content to your next reply.


===========================================
If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~

#20 User is offline   rotor123 

  • Forum Addict
  • PipPipPipPipPipPip
  • Find Topics
  • Group: BC Advisor
  • Posts: 1,754
  • Joined: 12-March 10
  • Gender:Male
  • Location:New Jersey

Posted 10 February 2012 - 10:20 AM

One stray thought.
I have heard sounds that are similar to clicking come from the Optical drive on some computers when they are powered on for a few seconds. More so when the computer is set to check the drive ahead of the hard drive in the boot options.

This post has been edited by rotor123: 10 February 2012 - 10:22 AM

My first Computer had a Whopping 16K of memory @ 0.89MHz
My first hard drive held 20 Megabytes and never got filled up.

#21 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 10 February 2012 - 11:52 AM

View PostLucheLibre, on 10 February 2012 - 08:27 AM, said:

We can check the BSODs to see if anything needs to be done about it.

But if your hard drive checks out, and the computer otherwise runs well, then I wouldn't worry about the clicks until necessary.

Use BlueScreenView to provide details about your errors.

  • Download the .zip file and extract to a folder on your desktop. Open that folder and run BlueScreenView.exe.
  • After BSV completes its scan, click Edit > Select All. Then click File > Save Selected Items and save the report to your desktop as BSOD.txt
  • Open BSOD.txt in Notepad and copy/paste all of its content to your next reply.


===========================================

==================================================
Dump File : 120111-20092-01.dmp
Crash Time : 01/12/2011 12:53:10
Bug Check String : ATTEMPTED_SWITCH_FROM_DPC
Bug Check Code : 0x100000b8
Parameter 1 : fffffa80`06e19680
Parameter 2 : fffff880`0316ef80
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : NETIO.SYS
Caused By Address : NETIO.SYS+2892
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f4da
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\120111-20092-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 102611-20202-01.dmp
Crash Time : 26/10/2011 19:02:45
Bug Check String : ATTEMPTED_SWITCH_FROM_DPC
Bug Check Code : 0x100000b8
Parameter 1 : fffffa80`06e19680
Parameter 2 : fffff880`0316ef80
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2524
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f4da
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102611-20202-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 101211-20155-01.dmp
Crash Time : 12/10/2011 14:03:03
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2593
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101211-20155-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 092811-17862-01.dmp
Crash Time : 28/09/2011 19:02:27
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : vsmraid.sys
Caused By Address : vsmraid.sys+20d4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092811-17862-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 092711-23056-01.dmp
Crash Time : 27/09/2011 01:19:24
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : vsmraid.sys
Caused By Address : vsmraid.sys+20d4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092711-23056-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 092111-19624-01.dmp
Crash Time : 21/09/2011 08:50:40
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : vsmraid.sys
Caused By Address : vsmraid.sys+20d4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092111-19624-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7601
Dump File Size : 275,496
==================================================

==================================================
Dump File : 090611-17409-01.dmp
Crash Time : 06/09/2011 12:34:39
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : vsmraid.sys
Caused By Address : vsmraid.sys+20d4c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090611-17409-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 275,440
==================================================

#22 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 11 February 2012 - 12:05 PM

View PostLucheLibre, on 10 February 2012 - 08:27 AM, said:

We can check the BSODs to see if anything needs to be done about it.

But if your hard drive checks out, and the computer otherwise runs well, then I wouldn't worry about the clicks until necessary.

Use BlueScreenView to provide details about your errors.

  • Download the .zip file and extract to a folder on your desktop. Open that folder and run BlueScreenView.exe.
  • After BSV completes its scan, click Edit > Select All. Then click File > Save Selected Items and save the report to your desktop as BSOD.txt
  • Open BSOD.txt in Notepad and copy/paste all of its content to your next reply.


===========================================

if i knew why it has been getting bsod i might not need a new m/b

#23 User is offline   LucheLibre 

  • Senior Member
  • PipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 592
  • Joined: 02-February 11
  • Gender:Male
  • Location:Tennessee

Posted 11 February 2012 - 04:28 PM

My first guess as to the BSODs is that you need to update your drivers starting with the chipset driver. NETIO.sys is a MS networking driver and vsmraid is a SATA RAID driver. Both these deal with devices on the motherboard.

This post has been edited by LucheLibre: 11 February 2012 - 10:06 PM

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~

#24 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 11 February 2012 - 04:48 PM

View PostLucheLibre, on 11 February 2012 - 04:28 PM, said:

My first guess as to the BSODs is that you need to update your drivers starting with the chipset driver. NETIO.sys is a MS networking driver and vsmraid is a HDD controller driver. Both these deal with devices on the motherboard.

do you mean motherboard update?

#25 User is offline   LucheLibre 

  • Senior Member
  • PipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 592
  • Joined: 02-February 11
  • Gender:Male
  • Location:Tennessee

Posted 11 February 2012 - 05:42 PM

The motherboard chipset driver, yes.
If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~

#26 User is offline   carpman1 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 24
  • Joined: 08-February 12

Posted 11 February 2012 - 06:10 PM

View PostLucheLibre, on 11 February 2012 - 05:42 PM, said:

The motherboard chipset driver, yes.

i updated them about 4 months ago when i fitted the m/b, i have never heard of that causing bsod.

#27 User is offline   LucheLibre 

  • Senior Member
  • PipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 592
  • Joined: 02-February 11
  • Gender:Male
  • Location:Tennessee

Posted 11 February 2012 - 10:09 PM

Presuming no bad hardware, it may be that your chipset driver may have been giving you BSODs ever since. Very infrequent, though.
If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~

Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users