Author Topic: A Christmas Day Blue Screen. (and hello)  (Read 2012 times)

0 Members and 1 Guest are viewing this topic.

A Christmas Day Blue Screen. (and hello)
Hi.

Welll now. It's certainly been an eventful year, high-school drama and 10-year old emotional demons aside.
I've decided to come back home to HLP. Freespace just refuses to die on me, if my asking of TrackIR 5 for Christmas is any testament.

I am now the proud owner of a Razer Nostromo, Razer Onza TE, and Track IR 5 with proclip. Oh, and a computer with (seemingly) corrupt USB drivers that BSOD's me whenever I try to boot-up with the Razer Onza plugged in.
This is after trying to get the gamepad to work with Devil May Cry 4 and Team Fortress 2, both of which it is completely unresponsive to.

I'm taking this time to hopefully solve some other PC issues that have been plaguing me all year and I've simply been too lazy to fix, since they seem to be rather minor. However, inevitably, it seems that my laziness has unironically bitten me in the ass. I really want this gamepad to work, and I want my logintimes to at least go a bit lower than about 2 minutes.

I'm truly sorry that the first thing I post on HLP is an asking for tech help, especially on Christmas of all times, but I really just want to get this **** working so I can enjoy my break before the diplomas kill me. I intent to lurk around HLP once again and be a part of this amazing community. I don't expect to get much help soon, it being Christmas, but I'm hoping later in the week I can get some problems solved. I'm truly grateful for any help I'm given.

I've honestly missed you guys. Even Snail. Whether this problem is helped or not, I intend to be part of Hard-Light once again, and play Freespace just like I did back when my days were happier. I hope things have been well for y'all.

Here's the situation on my PC.
Like I said I blue-screen when I try to boot-up with the Onza, and I can't get it to work with any games. The problem seems to be with my drivers, as the asmthub3.sys file is pointed out as the problem during hte BSOD message. I've downloaded the proper drivers from ASUS (which are at least a year old) and attempted to install, but the two install programs (asussetup.exe and setup.exe) are both unresponsive. Therefore I simply tried copy-pasting the driver files from the install folder (in which they are convieniently sorted into the proper windows directories) to the windows drivers directory, replacing my old files. That didn't help anything. I don't really know where to go to tech support, so I went here. I've been debating whether or not to return to HLP again for at least two months now, and I guess I have further incentive to come back. I'd love to have some help, if that's even possible. and again, I'm happy to be back.
« Last Edit: December 25, 2011, 01:11:48 pm by haloboy100 »
Fun while it lasted.

Then bitter.

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: A Christmas Day Blue Screen. (and hello)
See if you can manually extract (like with 7-zip) the drivers, and tell Device manager to update the drivers, then that you will specify which drivers to install, then point it at the extracted driver file.

 
Re: A Christmas Day Blue Screen. (and hello)
Doesn't look like it works. Keep in mind the driver folder is simply contain the two setup executables, a bunch of two-line .inis for languages, and a folder called "INF_files" that contains the actual drivers, which are a few .cat and .inf files, and folders "amd64", "i386", "ia64", that contain the .sys files.

The drivers came in a .zip file to begin with.
Fun while it lasted.

Then bitter.

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: A Christmas Day Blue Screen. (and hello)
point device manager at "INF_files" and try again

 
Re: A Christmas Day Blue Screen. (and hello)
Says it can't find the drivers.

I'm doing this from the (in windows 7, sorry if I didn't mention the OS) devices and printers menu, where it says "unknown device" which I know is my Onza, and clicking it and going to the properties menu.
Fun while it lasted.

Then bitter.

 
Re: A Christmas Day Blue Screen. (and hello)
Hold it. I've solved the problem.

Looks like I had to install the Xbox 360 controller for windows driver...even though the box says I don't need to install the drivers. Lying bastards.

Well, that's fixed. But there is other problems I wish to have help with, if it's all the same.

Is there a way to streamline my login time? IT takes about 1-3 minutes to log in to windows; 5-10 seconds on the welcome screen, a few minutes after for the system to become responsive enough to be usable. On startup, I also get an error message about "BChelper.exe", and that it can't start because "sqlite.dll" is missing or corrupt.
Fun while it lasted.

Then bitter.

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: A Christmas Day Blue Screen. (and hello)
http://www.sqlite.org/download.html  find and replace

If you suspect data corruption of Windows files, after running a check disk from an elevated command prompt

(start > type
Code: [Select]
cmd and then right-click the result and choose "Run as Administrator")

type the following:

Code: [Select]
chkdsk c: /f
replace the c with your drive letter if it is different.

Then, after restarting to scan the disk, open another elevated command prompt and run this:

Code: [Select]
sfc /scannow and let it complete.

EDIT: In case it's not clear, chkdsk is Windows' CHecK DiSK utility, and sfc is the System File Checker

 

Offline Davros

  • 29
Re: A Christmas Day Blue Screen. (and hello)
I could be wrong here but do a search for bchelper.exe
its a program by this company
http://www.blabbers.com/app/portal/about.jsp

do you really want this ?

 
Re: A Christmas Day Blue Screen. (and hello)
Chkdsk checks for data errors related to problems with the physical drive. Sfc fixes windows files. You will need your windows install cd handy for it to work, though. After that, run msconfig to see what all is booting up when windows starts. My policy is to turn off/disable any programs that seem unnecessary or are unknown, and if it is missed, re-enable it later. The OBVIOUS exception being anything that has to do with boot.ini or autoexec.bat (if they are even still used in Win7). Those are both important, as are almost anything in them.
Could we with ink the ocean fill, and were the skies of parchment made
Were every stalk on earth a quill, and every man a scribe by trade
To write the love of God above, would drain the ocean dry
Nor could the scroll contain the whole, though stretched from sky to sky!

  

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: A Christmas Day Blue Screen. (and hello)
Autoexec was nixed with NT (including XP and 2000), which also introduced boot.ini as the file that points to your windows install on startup.
Boot.ini was nixed with Vista, with the introduction of IIRC bootmgr. But if you dual boot with an old OS then ofc keep them.

EDIT you don't need windows CD unless cache is incomplete or broken
« Last Edit: December 31, 2011, 11:34:40 pm by jr2 »