• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Proof: BC Lottery Corp uses a microsoft OS in their machines

GoStumpy

GoStumpy

Golden Member
This happened right beside my table at my local Pub... Needed a hard reboot 😎

Photo002.jpg


Apparently I was the only geek in attendance, nobody else joined in my laughter 😀()🙂
 
A local grocery chain here (Bi-Lo) put in all new 42" display with sff ibm desktops running XP. The day they turned them on about 3 of the 6 in one store had B.S.O.D.'s. I laughed to myself as I took out my phone to snap a picture of one. As I was taking the pic the manager practically sprinted from 50 feet away to come over and confront me about it. He, in a really loud and pissy tone, said "Excuse me sir, MAY I HELP YOU?!", while mean mugging me. I just laughed and said no, then turned back around and finished taking the picture. Not sure why he took it so personal.
 
I see your bluescreen display and raise you one. Apparently a Saab driving simulator at the Javits Center Auto Show 2008 had a problem with an NVidia display driver. 😉

bsod.jpg
 
Last edited:
I see MS prompts and BSODs on all kinds of random kiosks, registers, and terminals, including ATMs. Stopped amusing me back in 1998.
 
I saw BSOD on a candy vending machine display. My girlfriend was thought I was stupid for stopping to take a picture. My geek friends though it was awesome.
 
I see them on MTA electronic billboards at subway stations in the city, the BSOD that is.

And they wonder why people don't feel comfortable with their idea of replacing train conductors with computers. No doubt that as a semi-government agency, they would be using the lowest bidder that would then outsource to the next lowest bidder, that would then outsource to a company in China that would use a pirated copy of Windows ME, complete with the trojans preinstalled in order to save their relatives time in making all trains run express to Chinatown.
 
Even funnier is if a public system like that (billboards especially) had XP Antivirus 2012 running on it. :biggrin:
 
lol it's hilarious to see that on a public display. I've never been lucky enough to catch one. It's one thing to see it on the internet, but it's even funnier when you actually see it yourself. When I was down south I did see a kiosk display at a mall that had a battery warning on it indicating it was a random laptop somewhere that must have been accidentally unplugged, but that's not as funny as a BSOD though.
 
I saw on on of the big digtal boards, someone minimized the program so it was XP desktop lol.

Pumping gas at Shell, BSOD on the TV there lol
 
As usual, the blue screen in the OP is caused by a device driver. If I read correctly, the driver that caused this BSOD is pd1usb.sys, a 3rd party driver supplied by Adata.

Device drivers are almost always the weakest link in the chain, and account for the overwhelming majority of bugchecks. Hardware vendors just don't like to spend the money for quality kernel mode driver developers, it is a "cost" that effects profitability along with testing of the driver.

My point is that especially these days, bugchecks (aka BSOD) are not usually the fault of Microsoft code itself. If a driver has a null pointer or does not free its memory, that is on them. Of course it could be argued that Windows handles these faults better. Microsoft has done a ton of work to alleviate this providing class drivers and user mode driver frameworks.

My question is why isn't the Adata USB device using a proprietary driver and not the class driver? A quick googling of pd1usb.sys shows it is for a usb thumb drive.

The fault in the pic is DRIVER_IRQL_NOT_LESS_OR_EQUAL, which is caused by a bad driver 99% of the time.

Windows stop DRIVER_IRQL_NOT_LESS_OR_EQUAL error.

Cause

This error is generated when a driver or part of Windows attempts to access pageable memory using the IRQL kernel process that is invalid.

Bad hardware drivers.
Bad memory or mismatched memory.
Corrupt or bad Virtual Memory page file.
 
Last edited:
When the Michigan Lottery's Keno displays shut down at 1 AM, you briefly see the Windows 98 shut down screen.
 
davmat787 said:
As usual, the blue screen in the OP is caused by a device driver. If I read correctly, the driver that caused this BSOD is pd1usb.sys, a 3rd party driver supplied by Adata.

Device drivers are almost always the weakest link in the chain, and account for the overwhelming majority of bugchecks. Hardware vendors just don't like to spend the money for quality kernel mode driver developers, it is a "cost" that effects profitability along with testing of the driver.

My point is that especially these days, bugchecks (aka BSOD) are not usually the fault of Microsoft code itself. If a driver has a null pointer or does not free its memory, that is on them. Of course it could be argued that Windows handles these faults better. Microsoft has done a ton of work to alleviate this providing class drivers and user mode driver frameworks.

My question is why isn't the Adata USB device using a proprietary driver and not the class driver? A quick googling of pd1usb.sys shows it is for a usb thumb drive.

The fault in the pic is DRIVER_IRQL_NOT_LESS_OR_EQUAL, which is caused by a bad driver 99% of the time.

Windows stop DRIVER_IRQL_NOT_LESS_OR_EQUAL error.

Cause

This error is generated when a driver or part of Windows attempts to access pageable memory using the IRQL kernel process that is invalid.

Bad hardware drivers.
Bad memory or mismatched memory.
Corrupt or bad Virtual Memory page file.
Click to expand...

I don't even bother explaining this to people these days. They are usually the ones that spell Microsoft, M$.
 
I wonder what the lottery machines use as their source of random numbers:

A pseudorandom algorithm, or the more expensive solution of genuinely random numbers from the proper hardware?

Side note: It's annoying to get stuck behind someone who spends so much time reading off a list of special or "significant" numbers to be played.
Take the machine's numbers, or just use the same numbers every week, it won't affect the outcome anyway.
Though here's a thought: Wait until the machine blue-screens, then use the memory address as your lottery numbers. :hmm:
 
Jeff7 said:
I wonder what the lottery machines use as their source of random numbers:

A pseudorandom algorithm, or the more expensive solution of genuinely random numbers from the proper hardware?

Side note: It's annoying to get stuck behind someone who spends so much time reading off a list of special or "significant" numbers to be played.
Take the machine's numbers, or just use the same numbers every week, it won't affect the outcome anyway.
Though here's a thought: Wait until the machine blue-screens, then use the memory address as your lottery numbers. :hmm:
Click to expand...
i850/Williamette had a true analog RNG as did all Intel platforms in the last decade.
Address ranges will have a lot of the same numbers.
Funny that you would admit to playing a skill-less game with losing odds while insulting other players' intelligence. 😉
 
CZroe said:
i850/Williamette had a true analog RNG as did all Intel platforms in the last decade.

Address ranges will have a lot of the same numbers.
Click to expand...
How good is it? I've seen things out there like this that can command well over $1000.
Is it just the throughput of random bits that makes an expensive generator more desirable?



Funny that you would admit to playing a skill-less game with losing odds while insulting other players' intelligence. 😉
Click to expand...
I don't play - this particular store is a small convenience store. It has only one line to wait in to pay for anything, whether it be a 2L of soda or a lottery ticket.😉
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top