Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Frequent BSODs - No Entry in Event Viewer


  • Please log in to reply

#61
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go 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.

Thanks to Broni for the instructions and program
  • 0

Advertisements


#62
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
would you happen to have a secondary link for that app? Firewall here has it blocked as "Hacking".. websense..
  • 0

#63
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
Waaait a minute...

Take a look at post#7.. I already have BlueScreenViewer downloaded and have been trying to use it. For some reason windows is not writing the mini dump. I navigated to %system root%\minidump and there is nothing there... (all hidden and system files are viewable). the folder is just empty and remains that way.

Any ideas what may be up there?
  • 0

#64
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Try this one HERE and if still no joy then Open firewall settings and allow the site.
Every site I found with it points back to the original site.
  • 0

#65
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
nah i get a server connection was reset error every time i try that link.. But, again, I already have the program downloaded from when this thread was started. It shows absolutely nothing. Either the OS is not writing the minidump or it is being deleted.

thoughts?
  • 0

#66
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK I just seen that you had a Malware topic HERE that was never completed.
I would suggest pm'ing the Tech who was helping you and continue with them. It seems you may have a issue with a infection that may be hindering us fixing this. Please add a link to this topic so that Tech can see what we have attempted.
  • 0

#67
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
ha.. that was actually my next thoughts..

will do... I'll post back here as soon as we finish that topic.

Thanks for the help!
  • 0

#68
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You are very welcome. I hope they find the problem and can resolve it for you. If not then return here and we will continue.
  • 0

#69
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
oh me too.. perhaps whatever is preventing the minidumps is what is causing the bluescreens and freezes too... wouldnt that be nice!

but knowing computers, it is probably answer c: all of the above plus something extra :)

almost makes you want to :)

...almost... (but not quite ready to yet!)
  • 0

#70
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

almost makes you want to surrender.gif

...almost... (but not quite ready to yet!)

:) I can understand your frustration
  • 0

Advertisements


#71
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
here is a question for you...

now that my computer is starting to write and keep the minidumps i have been looking at them in BSODViewer and I am starting to see a pattern.

In everyone of them ntoskrnl.exe is in there. In everyone of the crashes i see this line in the bottom half of BSDOViewer's GUI(I will break the line down into respective columns:

File Name: ntoskrnl.exe
Address in Stack: ntoskrnl.exe+119e13
From address: 0x804d7000
To Address: 0x806e4000
Size: 0x0020d000
Time Stamp: 0x4a784394
Time String: 8/4/2009 8:20:04 AM
Product Name: Microsoft® Windows® Operating System
File Description: NT Kernel & System
File Version: 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Company: Microsoft Corporation
Full Path: C:\WINDOWS\system32\ntoskrnl.exe

I assume this line since it is in red is the program/application that is in fault. In most of the recent BSODs that line is accompanied by another [varied] line(s) and only in the first 2 is that line by itself. In other minidump entries we have programs such as Epfw.sys, hal.dll, and NTFS.sys. Is there any chance there is a correlation between ntoskrnl.exe and one (if not all) of those programs? I was thinking perhaps they are conflicting and it is indeed the OS that is in fault. Though I will still need to replace the PSU as mentioned in the Malware thread I went to here

Just incase it is needed/wanted, here are the BSOD minidump reports from BSODViewer:

==================================================
Dump File : Mini111109-01.dmp
Crash Time : 11/11/2009 5:03:35 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805f0e13
Parameter 3 : 0xa0e009e8
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+119e13
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini111009-02.dmp
Crash Time : 11/10/2009 8:23:22 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00000cd4
Parameter 3 : 0x04760807
Parameter 4 : 0xe3651850
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini111009-01.dmp
Crash Time : 11/10/2009 1:10:30 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x00000008
Parameter 2 : 0xb8340d70
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+65535
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini110809-01.dmp
Crash Time : 11/8/2009 2:01:54 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x80521c60
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4ac60
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini110709-01.dmp
Crash Time : 11/7/2009 12:20:26 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xb523c4f4
Parameter 3 : 0xb523c1f0
Parameter 4 : 0xb7e2e1f3
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+2a1f3
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini110609-01.dmp
Crash Time : 11/6/2009 1:51:34 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x80521c60
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4ac60
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
==================================================

==================================================
Dump File : Mini110309-01.dmp
Crash Time : 11/3/2009 12:36:37 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000010
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x805229bf
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b9bf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
==================================================



Thoughts?
  • 0

#72
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
That is caused by a corrupted OS and with a repair installation hopefully should take care of that.
  • 0

#73
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
oook. Lets say you tried a repair install and had several files that could not be extracted, maybe 45 of them (that sounds like a good number). They were all .sys and .dll file, most .sys, though there was one single .exe towards the end.

what would be your first reaction?
  • 0

#74
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Either the drive is bad or the cd is bad.
  • 0

#75
SomeCrazyStuff

SomeCrazyStuff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 401 posts
hmm.. well i tried from 2 different CDs.. stupid computer.. lol
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP