Windows 7: jusched.exe application error, then STOP 0x000000F4

My computer has recently had this problem where it cannot continue to run normally for more that 5 minutes or so before it slows down then BSODs.

It seems to start up normally and everything works just fine for a short amount of time until applications stop responding. Sometimes the taskbar disappears and there's an error message with the title of "jusched.exe - Application Error" without the quotes. When I click ok to terminate the program I just see my wallpaper for a few seconds before it BSODs. Other times it just BSODs after applications stop responding.

The part after STOP always seems to be 0x000000F4, but I'm not sure about the rest.

I'd also like to know if I need to wait a certain amount of time before I can shut down my computer during the BSOD. It seems to say something like "initializing the disk for dumping" for quite some time.

Please use this tool to update your profile specs

And then use this tool to post all the files here

Uploaded the zip to the original post.

Well Alp

1. You said you had some BSOD .... but i dont see any dmp files in the uploads... Could you check C:\Windows\minidumps and see if anyfiles are there..... Without these it would be difficult to pinpoint the exact problem..... Also check if you have memory.dmp (this is a big file.....so you would need to upload it to dropbox or skydrive or another third party file hosting service )...even that can help.

2. Even though you have provided the HP model number.... checking the bios version at the site and the one you have installed doesnt show up in their list...... So it would really help if you can also provide the Product Number usaully mentioned in the sticker at the bottom of the laptop....

3. Based on what i can deduce from the logs.... i see you have lots of issues related to GEARAspiWDM.sys which is know to cause issue or BSOD.... This driver is CDROM filter driver... used by products like iTunes, norton etc.. I am not sure which programs uses this....on your system..... so the best bet is either remove or update... Please do remember....Completely removing the GEAR driver set from your system may result in GEAR software applications and any applications using the GEARwrks API not being able to "see" any recorders. Go here to remove or update it... follow the procedure mentioned there


Do these and let me know the product number for your model....

Hmm, well it looks like I updated the gear drivers... but nothing seems to have changed, after a while applications continue to stop responding.

Sorry, I can't seem to locate any model number like the one you're mentioning at the bottom of my laptop. It does have the windows product key information, but that's it.

When it blue screens, how long do I have to wait for dump files to generate? There's no folder in my Windows directory called minidumps...

To check your Product number go here

ok try checking this first before you do anything.....

1. Click start and on the search bar type "View advanced system settings"
   
2. Once there under Startup and Recovery click Settings
   
3. Once there under System Failure uncheck Automatic Restart... then under the dropdown select "Small memory dump"
   
4. then click ok and ok again to come out of it,.....

Again memory dumps will not be produced if the paging file is not the system volume... usually C:\.... to check

1. Click start and on the search bar type "View advanced system settings"
   
2. Once there under Performance click Settings
   
3. Once there under the Advanced tab > Virtual Memory.click on "Change"
   
4. then check automatically manage paging file size for all drives....
   
5. Click ok and then ok again ... to come out of it.... You may need to restart to make this setting stick.

In that case i would suggest you remove GearspiWDM ... Use this

Alright, so I followed the instructions and removed the drivers, unchecked the restart after system failure, and checked to see it already had automatically manage paging file size for all drive checked, which it was. After a restart, it looked like everything was working once again. I was able to use it normally for about an hour. I was away for some 15 minutes and when I came back it had BSOD'd.

I left it at the blue screen for two hours and it never said anything else after "initializing disk for dumping." I had to shut it down because I felt it was getting too hot. The Windows directory still doesn't have any folder called minidumps.

Anyways, I believe this is my laptop's product number:
QA668UA#ABA

ok please use the sf diag and upload the new set of files...

Alright, here they are.